Executive summary
shayanhabibi/Partas.Solid falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies, and it has uses of packages that aren't listed. It scores 50 out of 100 and is rated Adequate, and none of its seven critical findings concern security.
Production Readiness, at 34, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Tidying the declared packages would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 64.
The six uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 15,640 lines, about €38,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 34 to 70, the lowest score rated Strong, the score would rise from 50 to about 64.
New since the last survey: 1 finding
- Knowledge Freshness · Orphaned knowledge src/Partas.Solid/Style.fs
Fixed since the last survey: 1 finding
- God Classes · FileTooLong: Workbench/Workbench.fs tools/Workbench/Workbench.fs
Rebuild cost: about €38,000 · Estimate
| Cost to rebuild | €13,000 to €64,000, for 211 to 670 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.7 at a score of 50. 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: 15,640 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Fable.AST.Fable.Expr | 2 Nacara.Plugins | 3 Partas.Solid.Attr | 4 Partas.Solid.Builder | 5 Partas.Solid.Experimental.U | 6 Partas.Solid.JsxGen.Surface | 7 Nacara.Plugins.Internal | 8 Partas.Solid.Aria | 9 Partas.Solid.AttributeExtensions | 10 Partas.Solid.Bindings.For | 11 Partas.Solid.HtmlAttributeAliases | 12 Partas.Solid.HtmlAttributes | 13 Partas.Solid.HtmlEvents | 14 Partas.Solid.JsxGen.Emit | 15 Partas.Solid.Router.Bindings | 16 Partas.Solid.Web | 17 Nacara.Plugins.Internal.SolidCompile | 18 Nacara.Plugins.Internal.SolidScanModule | 19 Nacara.Plugins.Internal.SolidWorkspace | 20 Nacara.Plugins.SolidExamples | 21 Partas.Solid.Bindings | 22 Partas.Solid.JsxGen.ProfilesEmit | 23 Partas.Solid.JsxGen.TagsEmit | 24 Partas.Solid.Tags | 25 Partas.Solid | 26 Partas.Solid.Bindings.Match | 27 Partas.Solid.Meta.Bindings | 28 Partas.Solid.AST | 29 Partas.Solid.AST.AttributesAndProperties | 30 Partas.Solid.AST.SpecialAttributeTransformation | 31 Partas.Solid.AST.TagValue | 32 Partas.Solid.Baked | 33 Partas.Solid.Experimental | 34 Partas.Solid.Expr | 35 Partas.Solid.PluginContextModule | 36 Partas.Solid.ReactiveMatch | 37 Partas.Solid.StorybookAST | 38 Partas.Solid.StorybookCases | 39 Partas.Solid.StorybookDecorator | 40 Partas.Solid.StorybookRender |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Fable.AST.Fable.Expr | ||||||||||||||||||||||||||||||||||||||||
| 2 Nacara.Plugins | ||||||||||||||||||||||||||||||||||||||||
| 3 Partas.Solid.Attr | ||||||||||||||||||||||||||||||||||||||||
| 4 Partas.Solid.Builder | ||||||||||||||||||||||||||||||||||||||||
| 5 Partas.Solid.Experimental.U | ||||||||||||||||||||||||||||||||||||||||
| 6 Partas.Solid.JsxGen.Surface | ||||||||||||||||||||||||||||||||||||||||
| 7 Nacara.Plugins.Internal | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Partas.Solid.Aria | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Partas.Solid.AttributeExtensions | 74 | 54 | ||||||||||||||||||||||||||||||||||||||
| 10 Partas.Solid.Bindings.For | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Partas.Solid.HtmlAttributeAliases | 13 | 5 | ||||||||||||||||||||||||||||||||||||||
| 12 Partas.Solid.HtmlAttributes | 61 | 6 | ||||||||||||||||||||||||||||||||||||||
| 13 Partas.Solid.HtmlEvents | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Partas.Solid.JsxGen.Emit | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Partas.Solid.Router.Bindings | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Partas.Solid.Web | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Nacara.Plugins.Internal.SolidCompile | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 Nacara.Plugins.Internal.SolidScanModule | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Nacara.Plugins.Internal.SolidWorkspace | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Nacara.Plugins.SolidExamples | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Partas.Solid.Bindings | 7 | 1 | 10 | |||||||||||||||||||||||||||||||||||||
| 22 Partas.Solid.JsxGen.ProfilesEmit | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 Partas.Solid.JsxGen.TagsEmit | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Partas.Solid.Tags | 120 | 57 | ||||||||||||||||||||||||||||||||||||||
| 25 Partas.Solid | 5 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Partas.Solid.Bindings.Match | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Partas.Solid.Meta.Bindings | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 28 Partas.Solid.AST | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 Partas.Solid.AST.AttributesAndProperties | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Partas.Solid.AST.SpecialAttributeTransformation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Partas.Solid.AST.TagValue | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Partas.Solid.Baked | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Partas.Solid.Experimental | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Partas.Solid.Expr | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Partas.Solid.PluginContextModule | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 Partas.Solid.ReactiveMatch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Partas.Solid.StorybookAST | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 Partas.Solid.StorybookCases | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Partas.Solid.StorybookDecorator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Partas.Solid.StorybookRender | 1 | 1 |
7→2 Nacara.Plugins.Internal uses Nacara.Plugins✕
- Connections
- 2 pairs of types, where a type in Nacara.Plugins.Internal uses a type in Nacara.Plugins.
- The types involved
Nacara.Plugins.Internal.SolidMessage→Nacara.Plugins.SolidPageUnitNacara.Plugins.Internal.SolidScan→Nacara.Plugins.SolidCell
- Direction
- Nacara.Plugins.Internal uses Nacara.Plugins, so a change to Nacara.Plugins can break Nacara.Plugins.Internal, while a change to Nacara.Plugins.Internal can't break Nacara.Plugins.
- Position
- Below the diagonal: Nacara.Plugins.Internal uses a module listed above it, which is the healthy direction.
8→3 Partas.Solid.Aria uses Partas.Solid.Attr✕
- Connections
- 7 pairs of types, where a type in Partas.Solid.Aria uses a type in Partas.Solid.Attr.
- The types involved
Partas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaAutocompletePartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaDropeffectPartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaLivePartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaOrientationPartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaRelevantPartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaRolePartas.Solid.Aria.HtmlTag→Partas.Solid.Attr.AriaSort
- Direction
- Partas.Solid.Aria uses Partas.Solid.Attr, so a change to Partas.Solid.Attr can break Partas.Solid.Aria, while a change to Partas.Solid.Aria can't break Partas.Solid.Attr.
- Position
- Below the diagonal: Partas.Solid.Aria uses a module listed above it, which is the healthy direction.
8→5 Partas.Solid.Aria uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Aria uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.Aria.HtmlTag→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.Aria uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.Aria, while a change to Partas.Solid.Aria can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.Aria uses a module listed above it, which is the healthy direction.
9→3 Partas.Solid.AttributeExtensions uses Partas.Solid.Attr✕
- Connections
- 74 pairs of types, where a type in Partas.Solid.AttributeExtensions uses a type in Partas.Solid.Attr. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Partas.Solid.AttributeExtensions.AnimateMotionSVGAttributes→Partas.Solid.Attr.SvgOriginPartas.Solid.AttributeExtensions.AnimationAdditionSVGAttributes→Partas.Solid.Attr.SvgAccumulatePartas.Solid.AttributeExtensions.AnimationAdditionSVGAttributes→Partas.Solid.Attr.SvgAdditivePartas.Solid.AttributeExtensions.AnimationAttributeTargetSVGAttributes→Partas.Solid.Attr.SvgAttributeTypePartas.Solid.AttributeExtensions.AnimationTimingSVGAttributes→Partas.Solid.Attr.SvgRestartPartas.Solid.AttributeExtensions.AnimationValueSVGAttributes→Partas.Solid.Attr.SvgCalcModePartas.Solid.AttributeExtensions.ClipPathSVGAttributes→Partas.Solid.Attr.SvgClipPathUnitsPartas.Solid.AttributeExtensions.ExternalResourceSVGAttributes→Partas.Solid.Attr.SvgExternalResourcesRequiredPartas.Solid.AttributeExtensions.FeBlendSVGAttributes→Partas.Solid.Attr.SvgModePartas.Solid.AttributeExtensions.FeConvolveMatrixSVGAttributes→Partas.Solid.Attr.SvgEdgeModePartas.Solid.AttributeExtensions.FeConvolveMatrixSVGAttributes→Partas.Solid.Attr.SvgPreserveAlphaPartas.Solid.AttributeExtensions.FeDisplacementMapSVGAttributes→Partas.Solid.Attr.SvgXChannelSelectorPartas.Solid.AttributeExtensions.FeDisplacementMapSVGAttributes→Partas.Solid.Attr.SvgYChannelSelectorPartas.Solid.AttributeExtensions.FeTurbulanceSVGAttributes→Partas.Solid.Attr.SvgStitchTilesPartas.Solid.AttributeExtensions.FilterSVGAttributes→Partas.Solid.Attr.SvgFilterUnitsPartas.Solid.AttributeExtensions.FilterSVGAttributes→Partas.Solid.Attr.SvgPrimitiveUnitsPartas.Solid.AttributeExtensions.GradientElementSVGAttributes→Partas.Solid.Attr.SvgGradientUnitsPartas.Solid.AttributeExtensions.GradientElementSVGAttributes→Partas.Solid.Attr.SvgSpreadMethodPartas.Solid.AttributeExtensions.MarkerSVGAttributes→Partas.Solid.Attr.SvgMarkerUnitsPartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaAtomicPartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaAutocompletePartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaBusyPartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaCheckedPartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaCurrentPartas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Attr.SvgAriaDisabled
- Direction
- Partas.Solid.AttributeExtensions uses Partas.Solid.Attr, so a change to Partas.Solid.Attr can break Partas.Solid.AttributeExtensions, while a change to Partas.Solid.AttributeExtensions can't break Partas.Solid.Attr.
- Position
- Below the diagonal: Partas.Solid.AttributeExtensions uses a module listed above it, which is the healthy direction.
9→5 Partas.Solid.AttributeExtensions uses Partas.Solid.Experimental.U✕
- Connections
- 54 pairs of types, where a type in Partas.Solid.AttributeExtensions uses a type in Partas.Solid.Experimental.U. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Partas.Solid.AttributeExtensions.AnimationValueSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeCompositeSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeConvolveMatrixSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeDiffuseLightingSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeDisplacementMapSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeDistantLightSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeFuncSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeMorphologySVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeSpotLightSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FeTurbulanceSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.FilterSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.MarkerSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.MaskSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.RadialGradientSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.TextPathSVGAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.baselineshiftAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.cxAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.cyAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.dxAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.dyAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.fillopacityAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.floodopacityAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.fontsizeadjustAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.fontweightAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2Partas.Solid.AttributeExtensions.heightAttributeInterfaceProvider→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.AttributeExtensions uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.AttributeExtensions, while a change to Partas.Solid.AttributeExtensions can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.AttributeExtensions uses a module listed above it, which is the healthy direction.
10→4 Partas.Solid.Bindings.For uses Partas.Solid.Builder✕
- Connections
- 8 pairs of types, where a type in Partas.Solid.Bindings.For uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Bindings.For.For→Partas.Solid.Builder.ChildLambdaProvider2Partas.Solid.Bindings.For.For→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.For.Keyed→Partas.Solid.Builder.ChildLambdaProvider2Partas.Solid.Bindings.For.Keyed→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.For.KeyedFn→Partas.Solid.Builder.ChildLambdaProvider2Partas.Solid.Bindings.For.KeyedFn→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.For.NonKeyed→Partas.Solid.Builder.ChildLambdaProvider2Partas.Solid.Bindings.For.NonKeyed→Partas.Solid.Builder.HtmlElement
- Direction
- Partas.Solid.Bindings.For uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Bindings.For, while a change to Partas.Solid.Bindings.For can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Bindings.For uses a module listed above it, which is the healthy direction.
10→5 Partas.Solid.Bindings.For uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Bindings.For uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.Bindings.For.For→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.Bindings.For uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.Bindings.For, while a change to Partas.Solid.Bindings.For can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.Bindings.For uses a module listed above it, which is the healthy direction.
11→3 Partas.Solid.HtmlAttributeAliases uses Partas.Solid.Attr✕
- Connections
- 13 pairs of types, where a type in Partas.Solid.HtmlAttributeAliases uses a type in Partas.Solid.Attr.
- The types involved
Partas.Solid.HtmlAttributeAliases.AnchorHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributeAliases.AreaHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributeAliases.ButtonHTMLAttributes→Partas.Solid.Attr.FormenctypePartas.Solid.HtmlAttributeAliases.ButtonHTMLAttributes→Partas.Solid.Attr.FormmethodPartas.Solid.HtmlAttributeAliases.ButtonHTMLAttributes→Partas.Solid.Attr.PopovertargetactionPartas.Solid.HtmlAttributeAliases.HTMLAttributes→Partas.Solid.Attr.AutocapitalizePartas.Solid.HtmlAttributeAliases.HTMLAttributes→Partas.Solid.Attr.InputmodePartas.Solid.HtmlAttributeAliases.IframeHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributeAliases.ImgHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributeAliases.InputHTMLAttributes→Partas.Solid.Attr.FormenctypePartas.Solid.HtmlAttributeAliases.InputHTMLAttributes→Partas.Solid.Attr.FormmethodPartas.Solid.HtmlAttributeAliases.LinkHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributeAliases.ScriptHTMLAttributes→Partas.Solid.Attr.Referrerpolicy
- Direction
- Partas.Solid.HtmlAttributeAliases uses Partas.Solid.Attr, so a change to Partas.Solid.Attr can break Partas.Solid.HtmlAttributeAliases, while a change to Partas.Solid.HtmlAttributeAliases can't break Partas.Solid.Attr.
- Position
- Below the diagonal: Partas.Solid.HtmlAttributeAliases uses a module listed above it, which is the healthy direction.
11→5 Partas.Solid.HtmlAttributeAliases uses Partas.Solid.Experimental.U✕
- Connections
- 5 pairs of types, where a type in Partas.Solid.HtmlAttributeAliases uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.HtmlAttributeAliases.HTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributeAliases.ImgHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributeAliases.LinkHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributeAliases.MediaHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributeAliases.ScriptHTMLAttributes→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.HtmlAttributeAliases uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.HtmlAttributeAliases, while a change to Partas.Solid.HtmlAttributeAliases can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.HtmlAttributeAliases uses a module listed above it, which is the healthy direction.
12→3 Partas.Solid.HtmlAttributes uses Partas.Solid.Attr✕
- Connections
- 61 pairs of types, where a type in Partas.Solid.HtmlAttributes uses a type in Partas.Solid.Attr. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Partas.Solid.HtmlAttributes.AnchorHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributes.AnchorHTMLAttributes→Partas.Solid.Attr.ShapePartas.Solid.HtmlAttributes.AreaHTMLAttributes→Partas.Solid.Attr.ReferrerpolicyPartas.Solid.HtmlAttributes.AreaHTMLAttributes→Partas.Solid.Attr.ShapePartas.Solid.HtmlAttributes.ButtonHTMLAttributes→Partas.Solid.Attr.ButtonTypePartas.Solid.HtmlAttributes.ButtonHTMLAttributes→Partas.Solid.Attr.FormenctypePartas.Solid.HtmlAttributes.ButtonHTMLAttributes→Partas.Solid.Attr.FormmethodPartas.Solid.HtmlAttributes.ButtonHTMLAttributes→Partas.Solid.Attr.PopovertargetactionPartas.Solid.HtmlAttributes.CaptionHTMLAttributes→Partas.Solid.Attr.CaptionAlignPartas.Solid.HtmlAttributes.ColHTMLAttributes→Partas.Solid.Attr.ColAlignPartas.Solid.HtmlAttributes.ColHTMLAttributes→Partas.Solid.Attr.ValignPartas.Solid.HtmlAttributes.ColgroupHTMLAttributes→Partas.Solid.Attr.ColAlignPartas.Solid.HtmlAttributes.ColgroupHTMLAttributes→Partas.Solid.Attr.ValignPartas.Solid.HtmlAttributes.DialogHtmlAttributes→Partas.Solid.Attr.ClosedbyPartas.Solid.HtmlAttributes.EmbedHTMLAttributes→Partas.Solid.Attr.EmbedAlignPartas.Solid.HtmlAttributes.FormHTMLAttributes→Partas.Solid.Attr.AutocompletePartas.Solid.HtmlAttributes.FormHTMLAttributes→Partas.Solid.Attr.EncodingPartas.Solid.HtmlAttributes.FormHTMLAttributes→Partas.Solid.Attr.EnctypePartas.Solid.HtmlAttributes.FormHTMLAttributes→Partas.Solid.Attr.MethodPartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.AutocapitalizePartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.AutocorrectPartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.DirPartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.DraggablePartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.EnterkeyhintPartas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Attr.Inputmode
- Direction
- Partas.Solid.HtmlAttributes uses Partas.Solid.Attr, so a change to Partas.Solid.Attr can break Partas.Solid.HtmlAttributes, while a change to Partas.Solid.HtmlAttributes can't break Partas.Solid.Attr.
- Position
- Below the diagonal: Partas.Solid.HtmlAttributes uses a module listed above it, which is the healthy direction.
12→5 Partas.Solid.HtmlAttributes uses Partas.Solid.Experimental.U✕
- Connections
- 6 pairs of types, where a type in Partas.Solid.HtmlAttributes uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.HtmlAttributes.HTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributes.ImgHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributes.InputHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributes.LinkHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributes.MediaHTMLAttributes→Partas.Solid.Experimental.U.U2Partas.Solid.HtmlAttributes.ScriptHTMLAttributes→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.HtmlAttributes uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.HtmlAttributes, while a change to Partas.Solid.HtmlAttributes can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.HtmlAttributes uses a module listed above it, which is the healthy direction.
13→4 Partas.Solid.HtmlEvents uses Partas.Solid.Builder✕
- Connections
- 1 pair of types, where a type in Partas.Solid.HtmlEvents uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.HtmlEvents.HtmlContainer→Partas.Solid.Builder.HtmlElement
- Direction
- Partas.Solid.HtmlEvents uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.HtmlEvents, while a change to Partas.Solid.HtmlEvents can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.HtmlEvents uses a module listed above it, which is the healthy direction.
14→6 Partas.Solid.JsxGen.Emit uses Partas.Solid.JsxGen.Surface✕
- Connections
- 1 pair of types, where a type in Partas.Solid.JsxGen.Emit uses a type in Partas.Solid.JsxGen.Surface.
- The types involved
Partas.Solid.JsxGen.Emit.Emit→Partas.Solid.JsxGen.Surface.Surface
- Direction
- Partas.Solid.JsxGen.Emit uses Partas.Solid.JsxGen.Surface, so a change to Partas.Solid.JsxGen.Surface can break Partas.Solid.JsxGen.Emit, while a change to Partas.Solid.JsxGen.Emit can't break Partas.Solid.JsxGen.Surface.
- Position
- Below the diagonal: Partas.Solid.JsxGen.Emit uses a module listed above it, which is the healthy direction.
15→4 Partas.Solid.Router.Bindings uses Partas.Solid.Builder✕
- Connections
- 3 pairs of types, where a type in Partas.Solid.Router.Bindings uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Router.Bindings.RouteSectionProps→Partas.Solid.Builder.HtmlElementPartas.Solid.Router.Bindings.RouterInstance→Partas.Solid.Builder.TagValuePartas.Solid.Router.Bindings.RouterRoot→Partas.Solid.Builder.ChildLambdaProvider
- Direction
- Partas.Solid.Router.Bindings uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Router.Bindings, while a change to Partas.Solid.Router.Bindings can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Router.Bindings uses a module listed above it, which is the healthy direction.
15→5 Partas.Solid.Router.Bindings uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Router.Bindings uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.Router.Bindings.BeforeLeaveEventArgs→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.Router.Bindings uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.Router.Bindings, while a change to Partas.Solid.Router.Bindings can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.Router.Bindings uses a module listed above it, which is the healthy direction.
16→4 Partas.Solid.Web uses Partas.Solid.Builder✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Web uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Web.Bindings→Partas.Solid.Builder.TagValue
- Direction
- Partas.Solid.Web uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Web, while a change to Partas.Solid.Web can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Web uses a module listed above it, which is the healthy direction.
16→5 Partas.Solid.Web uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Web uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.Web.HeadTag→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.Web uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.Web, while a change to Partas.Solid.Web can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.Web uses a module listed above it, which is the healthy direction.
17→2 Nacara.Plugins.Internal.SolidCompile uses Nacara.Plugins✕
- Connections
- 2 pairs of types, where a type in Nacara.Plugins.Internal.SolidCompile uses a type in Nacara.Plugins.
- The types involved
Nacara.Plugins.Internal.SolidCompile.SolidCompile→Nacara.Plugins.SolidExamplesOptionsNacara.Plugins.Internal.SolidCompile.SolidCompile→Nacara.Plugins.SolidPageUnit
- Direction
- Nacara.Plugins.Internal.SolidCompile uses Nacara.Plugins, so a change to Nacara.Plugins can break Nacara.Plugins.Internal.SolidCompile, while a change to Nacara.Plugins.Internal.SolidCompile can't break Nacara.Plugins.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidCompile uses a module listed above it, which is the healthy direction.
17→7 Nacara.Plugins.Internal.SolidCompile uses Nacara.Plugins.Internal✕
- Connections
- 3 pairs of types, where a type in Nacara.Plugins.Internal.SolidCompile uses a type in Nacara.Plugins.Internal.
- The types involved
Nacara.Plugins.Internal.SolidCompile.SolidCompile→Nacara.Plugins.Internal.SolidCompiledNacara.Plugins.Internal.SolidCompile.SolidCompile→Nacara.Plugins.Internal.SolidMessageNacara.Plugins.Internal.SolidCompile.Watching→Nacara.Plugins.Internal.SolidFableWatcher
- Direction
- Nacara.Plugins.Internal.SolidCompile uses Nacara.Plugins.Internal, so a change to Nacara.Plugins.Internal can break Nacara.Plugins.Internal.SolidCompile, while a change to Nacara.Plugins.Internal.SolidCompile can't break Nacara.Plugins.Internal.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidCompile uses a module listed above it, which is the healthy direction.
18→2 Nacara.Plugins.Internal.SolidScanModule uses Nacara.Plugins✕
- Connections
- 2 pairs of types, where a type in Nacara.Plugins.Internal.SolidScanModule uses a type in Nacara.Plugins.
- The types involved
Nacara.Plugins.Internal.SolidScanModule.SolidScanModule→Nacara.Plugins.SolidCellNacara.Plugins.Internal.SolidScanModule.Tokens→Nacara.Plugins.SolidShow
- Direction
- Nacara.Plugins.Internal.SolidScanModule uses Nacara.Plugins, so a change to Nacara.Plugins can break Nacara.Plugins.Internal.SolidScanModule, while a change to Nacara.Plugins.Internal.SolidScanModule can't break Nacara.Plugins.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidScanModule uses a module listed above it, which is the healthy direction.
18→7 Nacara.Plugins.Internal.SolidScanModule uses Nacara.Plugins.Internal✕
- Connections
- 1 pair of types, where a type in Nacara.Plugins.Internal.SolidScanModule uses a type in Nacara.Plugins.Internal.
- The types involved
Nacara.Plugins.Internal.SolidScanModule.SolidScanModule→Nacara.Plugins.Internal.SolidScan
- Direction
- Nacara.Plugins.Internal.SolidScanModule uses Nacara.Plugins.Internal, so a change to Nacara.Plugins.Internal can break Nacara.Plugins.Internal.SolidScanModule, while a change to Nacara.Plugins.Internal.SolidScanModule can't break Nacara.Plugins.Internal.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidScanModule uses a module listed above it, which is the healthy direction.
19→2 Nacara.Plugins.Internal.SolidWorkspace uses Nacara.Plugins✕
- Connections
- 1 pair of types, where a type in Nacara.Plugins.Internal.SolidWorkspace uses a type in Nacara.Plugins.
- The types involved
Nacara.Plugins.Internal.SolidWorkspace.SolidWorkspace→Nacara.Plugins.SolidExamplesOptions
- Direction
- Nacara.Plugins.Internal.SolidWorkspace uses Nacara.Plugins, so a change to Nacara.Plugins can break Nacara.Plugins.Internal.SolidWorkspace, while a change to Nacara.Plugins.Internal.SolidWorkspace can't break Nacara.Plugins.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidWorkspace uses a module listed above it, which is the healthy direction.
19→7 Nacara.Plugins.Internal.SolidWorkspace uses Nacara.Plugins.Internal✕
- Connections
- 1 pair of types, where a type in Nacara.Plugins.Internal.SolidWorkspace uses a type in Nacara.Plugins.Internal.
- The types involved
Nacara.Plugins.Internal.SolidWorkspace.SolidWorkspace→Nacara.Plugins.Internal.SolidRun
- Direction
- Nacara.Plugins.Internal.SolidWorkspace uses Nacara.Plugins.Internal, so a change to Nacara.Plugins.Internal can break Nacara.Plugins.Internal.SolidWorkspace, while a change to Nacara.Plugins.Internal.SolidWorkspace can't break Nacara.Plugins.Internal.
- Position
- Below the diagonal: Nacara.Plugins.Internal.SolidWorkspace uses a module listed above it, which is the healthy direction.
20→2 Nacara.Plugins.SolidExamples uses Nacara.Plugins✕
- Connections
- 2 pairs of types, where a type in Nacara.Plugins.SolidExamples uses a type in Nacara.Plugins.
- The types involved
Nacara.Plugins.SolidExamples.SolidExamples→Nacara.Plugins.SolidExamplesOptionsNacara.Plugins.SolidExamples.SolidExamplesPlugin→Nacara.Plugins.SolidExamplesOptions
- Direction
- Nacara.Plugins.SolidExamples uses Nacara.Plugins, so a change to Nacara.Plugins can break Nacara.Plugins.SolidExamples, while a change to Nacara.Plugins.SolidExamples can't break Nacara.Plugins.
- Position
- Below the diagonal: Nacara.Plugins.SolidExamples uses a module listed above it, which is the healthy direction.
20→7 Nacara.Plugins.SolidExamples uses Nacara.Plugins.Internal✕
- Connections
- 1 pair of types, where a type in Nacara.Plugins.SolidExamples uses a type in Nacara.Plugins.Internal.
- The types involved
Nacara.Plugins.SolidExamples.SolidExamples→Nacara.Plugins.Internal.SolidMessage
- Direction
- Nacara.Plugins.SolidExamples uses Nacara.Plugins.Internal, so a change to Nacara.Plugins.Internal can break Nacara.Plugins.SolidExamples, while a change to Nacara.Plugins.SolidExamples can't break Nacara.Plugins.Internal.
- Position
- Below the diagonal: Nacara.Plugins.SolidExamples uses a module listed above it, which is the healthy direction.
21→4 Partas.Solid.Bindings uses Partas.Solid.Builder✕
- Connections
- 7 pairs of types, where a type in Partas.Solid.Bindings uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Bindings.IMatch→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.LazyComponent→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.Loading→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.Repeat→Partas.Solid.Builder.ChildLambdaProviderStrictPartas.Solid.Bindings.Repeat→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.Show→Partas.Solid.Builder.HtmlElementPartas.Solid.Bindings.Switch→Partas.Solid.Builder.HtmlElement
- Direction
- Partas.Solid.Bindings uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Bindings, while a change to Partas.Solid.Bindings can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Bindings uses a module listed above it, which is the healthy direction.
21→5 Partas.Solid.Bindings uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Bindings uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.Bindings.Errored→Partas.Solid.Experimental.U.U2
- Direction
- Partas.Solid.Bindings uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid.Bindings, while a change to Partas.Solid.Bindings can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid.Bindings uses a module listed above it, which is the healthy direction.
21→13 Partas.Solid.Bindings uses Partas.Solid.HtmlEvents✕
- Connections
- 10 pairs of types, where a type in Partas.Solid.Bindings uses a type in Partas.Solid.HtmlEvents.
- The types involved
Partas.Solid.Bindings.ContextProvider→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Errored→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Hydration→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Loading→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Match→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.NoHydration→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Repeat→Partas.Solid.HtmlEvents.FlowContainerPartas.Solid.Bindings.Reveal→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Show→Partas.Solid.HtmlEvents.HtmlContainerPartas.Solid.Bindings.Switch→Partas.Solid.HtmlEvents.FlowContainer
- Direction
- Partas.Solid.Bindings uses Partas.Solid.HtmlEvents, so a change to Partas.Solid.HtmlEvents can break Partas.Solid.Bindings, while a change to Partas.Solid.Bindings can't break Partas.Solid.HtmlEvents.
- Position
- Below the diagonal: Partas.Solid.Bindings uses a module listed above it, which is the healthy direction.
22→6 Partas.Solid.JsxGen.ProfilesEmit uses Partas.Solid.JsxGen.Surface✕
- Connections
- 1 pair of types, where a type in Partas.Solid.JsxGen.ProfilesEmit uses a type in Partas.Solid.JsxGen.Surface.
- The types involved
Partas.Solid.JsxGen.ProfilesEmit.ProfilesEmit→Partas.Solid.JsxGen.Surface.Surface
- Direction
- Partas.Solid.JsxGen.ProfilesEmit uses Partas.Solid.JsxGen.Surface, so a change to Partas.Solid.JsxGen.Surface can break Partas.Solid.JsxGen.ProfilesEmit, while a change to Partas.Solid.JsxGen.ProfilesEmit can't break Partas.Solid.JsxGen.Surface.
- Position
- Below the diagonal: Partas.Solid.JsxGen.ProfilesEmit uses a module listed above it, which is the healthy direction.
22→14 Partas.Solid.JsxGen.ProfilesEmit uses Partas.Solid.JsxGen.Emit✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.JsxGen.ProfilesEmit uses a type in Partas.Solid.JsxGen.Emit.
- The types involved
Partas.Solid.JsxGen.ProfilesEmit.ProfilesEmit→Partas.Solid.JsxGen.Emit.EmissionPartas.Solid.JsxGen.ProfilesEmit.ProfilesEmit→Partas.Solid.JsxGen.Emit.EmittedMember
- Direction
- Partas.Solid.JsxGen.ProfilesEmit uses Partas.Solid.JsxGen.Emit, so a change to Partas.Solid.JsxGen.Emit can break Partas.Solid.JsxGen.ProfilesEmit, while a change to Partas.Solid.JsxGen.ProfilesEmit can't break Partas.Solid.JsxGen.Emit.
- Position
- Below the diagonal: Partas.Solid.JsxGen.ProfilesEmit uses a module listed above it, which is the healthy direction.
23→6 Partas.Solid.JsxGen.TagsEmit uses Partas.Solid.JsxGen.Surface✕
- Connections
- 1 pair of types, where a type in Partas.Solid.JsxGen.TagsEmit uses a type in Partas.Solid.JsxGen.Surface.
- The types involved
Partas.Solid.JsxGen.TagsEmit.TagsEmit→Partas.Solid.JsxGen.Surface.Surface
- Direction
- Partas.Solid.JsxGen.TagsEmit uses Partas.Solid.JsxGen.Surface, so a change to Partas.Solid.JsxGen.Surface can break Partas.Solid.JsxGen.TagsEmit, while a change to Partas.Solid.JsxGen.TagsEmit can't break Partas.Solid.JsxGen.Surface.
- Position
- Below the diagonal: Partas.Solid.JsxGen.TagsEmit uses a module listed above it, which is the healthy direction.
23→14 Partas.Solid.JsxGen.TagsEmit uses Partas.Solid.JsxGen.Emit✕
- Connections
- 1 pair of types, where a type in Partas.Solid.JsxGen.TagsEmit uses a type in Partas.Solid.JsxGen.Emit.
- The types involved
Partas.Solid.JsxGen.TagsEmit.TagsEmit→Partas.Solid.JsxGen.Emit.Overrides
- Direction
- Partas.Solid.JsxGen.TagsEmit uses Partas.Solid.JsxGen.Emit, so a change to Partas.Solid.JsxGen.Emit can break Partas.Solid.JsxGen.TagsEmit, while a change to Partas.Solid.JsxGen.TagsEmit can't break Partas.Solid.JsxGen.Emit.
- Position
- Below the diagonal: Partas.Solid.JsxGen.TagsEmit uses a module listed above it, which is the healthy direction.
24→4 Partas.Solid.Tags uses Partas.Solid.Builder✕
- Connections
- 120 pairs of types, where a type in Partas.Solid.Tags uses a type in Partas.Solid.Builder. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Partas.Solid.Tags.Fragment→Partas.Solid.Builder.FragmentNodePartas.Solid.Tags.a→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.abbr→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.address→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.area→Partas.Solid.Builder.IntrinsicVoidNodePartas.Solid.Tags.article→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.aside→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.audio→Partas.Solid.Builder.AudioHTMLAttributesPartas.Solid.Tags.audio→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.b→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.base'→Partas.Solid.Builder.IntrinsicVoidNodePartas.Solid.Tags.bdi→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.bdo→Partas.Solid.Builder.BdoHTMLAttributesPartas.Solid.Tags.bdo→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.big→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.blockquote→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.body→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.br→Partas.Solid.Builder.IntrinsicVoidNodePartas.Solid.Tags.button→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.canvas→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.caption→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.cite→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.code→Partas.Solid.Builder.IntrinsicParentNodePartas.Solid.Tags.col→Partas.Solid.Builder.IntrinsicVoidNodePartas.Solid.Tags.colgroup→Partas.Solid.Builder.IntrinsicParentNode
- Direction
- Partas.Solid.Tags uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Tags, while a change to Partas.Solid.Tags can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Tags uses a module listed above it, which is the healthy direction.
24→12 Partas.Solid.Tags uses Partas.Solid.HtmlAttributes✕
- Connections
- 57 pairs of types, where a type in Partas.Solid.Tags uses a type in Partas.Solid.HtmlAttributes. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Partas.Solid.Tags.a→Partas.Solid.HtmlAttributes.AmbiguousNamespaceAttributesPartas.Solid.Tags.a→Partas.Solid.HtmlAttributes.AnchorHTMLAttributesPartas.Solid.Tags.area→Partas.Solid.HtmlAttributes.AreaHTMLAttributesPartas.Solid.Tags.audio→Partas.Solid.HtmlAttributes.MediaHTMLAttributesPartas.Solid.Tags.base'→Partas.Solid.HtmlAttributes.BaseHTMLAttributesPartas.Solid.Tags.blockquote→Partas.Solid.HtmlAttributes.BlockquoteHTMLAttributesPartas.Solid.Tags.body→Partas.Solid.HtmlAttributes.BodyHTMLAttributesPartas.Solid.Tags.body→Partas.Solid.HtmlAttributes.EventHandlersWindowPartas.Solid.Tags.button→Partas.Solid.HtmlAttributes.ButtonHTMLAttributesPartas.Solid.Tags.canvas→Partas.Solid.HtmlAttributes.CanvasHTMLAttributesPartas.Solid.Tags.caption→Partas.Solid.HtmlAttributes.CaptionHTMLAttributesPartas.Solid.Tags.col→Partas.Solid.HtmlAttributes.ColHTMLAttributesPartas.Solid.Tags.colgroup→Partas.Solid.HtmlAttributes.ColgroupHTMLAttributesPartas.Solid.Tags.data→Partas.Solid.HtmlAttributes.DataHTMLAttributesPartas.Solid.Tags.del→Partas.Solid.HtmlAttributes.InsHTMLAttributesPartas.Solid.Tags.details→Partas.Solid.HtmlAttributes.DetailsHtmlAttributesPartas.Solid.Tags.dialog→Partas.Solid.HtmlAttributes.DialogHtmlAttributesPartas.Solid.Tags.embed→Partas.Solid.HtmlAttributes.EmbedHTMLAttributesPartas.Solid.Tags.fieldset→Partas.Solid.HtmlAttributes.FieldsetHTMLAttributesPartas.Solid.Tags.form→Partas.Solid.HtmlAttributes.FormHTMLAttributesPartas.Solid.Tags.iframe→Partas.Solid.HtmlAttributes.IframeHTMLAttributesPartas.Solid.Tags.img→Partas.Solid.HtmlAttributes.ImgHTMLAttributesPartas.Solid.Tags.input→Partas.Solid.HtmlAttributes.InputHTMLAttributesPartas.Solid.Tags.ins→Partas.Solid.HtmlAttributes.InsHTMLAttributesPartas.Solid.Tags.keygen→Partas.Solid.HtmlAttributes.KeygenHTMLAttributes
- Direction
- Partas.Solid.Tags uses Partas.Solid.HtmlAttributes, so a change to Partas.Solid.HtmlAttributes can break Partas.Solid.Tags, while a change to Partas.Solid.Tags can't break Partas.Solid.HtmlAttributes.
- Position
- Below the diagonal: Partas.Solid.Tags uses a module listed above it, which is the healthy direction.
25→1 Partas.Solid uses Fable.AST.Fable.Expr✕
- Connections
- 5 pairs of types, where a type in Partas.Solid uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.ElementBuilder→Fable.AST.Fable.Expr.ExprPartas.Solid.PartasStorybookAttribute→Fable.AST.Fable.Expr.ExprPartas.Solid.SolidComponentAttribute→Fable.AST.Fable.Expr.ExprPartas.Solid.SolidTypeComponentAttribute→Fable.AST.Fable.Expr.ExprPartas.Solid.TagSource→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid, while a change to Partas.Solid can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid uses a module listed above it, which is the healthy direction.
25→5 Partas.Solid uses Partas.Solid.Experimental.U✕
- Connections
- 1 pair of types, where a type in Partas.Solid uses a type in Partas.Solid.Experimental.U.
- The types involved
Partas.Solid.ProjectionOptions→Partas.Solid.Experimental.U.U3
- Direction
- Partas.Solid uses Partas.Solid.Experimental.U, so a change to Partas.Solid.Experimental.U can break Partas.Solid, while a change to Partas.Solid can't break Partas.Solid.Experimental.U.
- Position
- Below the diagonal: Partas.Solid uses a module listed above it, which is the healthy direction.
25→21 Partas.Solid uses Partas.Solid.Bindings✕
- Connections
- 6 pairs of types, where a type in Partas.Solid uses a type in Partas.Solid.Bindings.
- The types involved
Partas.Solid.Bindings→Partas.Solid.Bindings.LazyComponentPartas.Solid.Bindings→Partas.Solid.Bindings.OwnerPartas.Solid.Bindings→Partas.Solid.Bindings.RefreshablePartas.Solid.Bindings→Partas.Solid.Bindings.RefreshableStorePartas.Solid.Bindings→Partas.Solid.Bindings.RootPartas.Solid.Bindings→Partas.Solid.Bindings.Store
- Direction
- Partas.Solid uses Partas.Solid.Bindings, so a change to Partas.Solid.Bindings can break Partas.Solid, while a change to Partas.Solid can't break Partas.Solid.Bindings.
- Position
- Below the diagonal: Partas.Solid uses a module listed above it, which is the healthy direction.
25→24 Partas.Solid uses Partas.Solid.Tags✕
- Connections
- 1 pair of types, where a type in Partas.Solid uses a type in Partas.Solid.Tags.
- The types involved
Partas.Solid.Bindings→Partas.Solid.Tags.Ref
- Direction
- Partas.Solid uses Partas.Solid.Tags, so a change to Partas.Solid.Tags can break Partas.Solid, while a change to Partas.Solid can't break Partas.Solid.Tags.
- Position
- Below the diagonal: Partas.Solid uses a module listed above it, which is the healthy direction.
26→4 Partas.Solid.Bindings.Match uses Partas.Solid.Builder✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.Bindings.Match uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Bindings.Match.Keyed→Partas.Solid.Builder.ChildLambdaProviderPartas.Solid.Bindings.Match.NonKeyed→Partas.Solid.Builder.ChildLambdaProvider
- Direction
- Partas.Solid.Bindings.Match uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Bindings.Match, while a change to Partas.Solid.Bindings.Match can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Bindings.Match uses a module listed above it, which is the healthy direction.
26→21 Partas.Solid.Bindings.Match uses Partas.Solid.Bindings✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.Bindings.Match uses a type in Partas.Solid.Bindings.
- The types involved
Partas.Solid.Bindings.Match.Keyed→Partas.Solid.Bindings.IMatchPartas.Solid.Bindings.Match.NonKeyed→Partas.Solid.Bindings.IMatch
- Direction
- Partas.Solid.Bindings.Match uses Partas.Solid.Bindings, so a change to Partas.Solid.Bindings can break Partas.Solid.Bindings.Match, while a change to Partas.Solid.Bindings.Match can't break Partas.Solid.Bindings.
- Position
- Below the diagonal: Partas.Solid.Bindings.Match uses a module listed above it, which is the healthy direction.
27→4 Partas.Solid.Meta.Bindings uses Partas.Solid.Builder✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Meta.Bindings uses a type in Partas.Solid.Builder.
- The types involved
Partas.Solid.Meta.Bindings.Head→Partas.Solid.Builder.FragmentNode
- Direction
- Partas.Solid.Meta.Bindings uses Partas.Solid.Builder, so a change to Partas.Solid.Builder can break Partas.Solid.Meta.Bindings, while a change to Partas.Solid.Meta.Bindings can't break Partas.Solid.Builder.
- Position
- Below the diagonal: Partas.Solid.Meta.Bindings uses a module listed above it, which is the healthy direction.
27→24 Partas.Solid.Meta.Bindings uses Partas.Solid.Tags✕
- Connections
- 7 pairs of types, where a type in Partas.Solid.Meta.Bindings uses a type in Partas.Solid.Tags.
- The types involved
Partas.Solid.Meta.Bindings.Base→Partas.Solid.Tags.base'Partas.Solid.Meta.Bindings.Link→Partas.Solid.Tags.linkPartas.Solid.Meta.Bindings.Meta→Partas.Solid.Tags.metaPartas.Solid.Meta.Bindings.Script→Partas.Solid.Tags.scriptPartas.Solid.Meta.Bindings.Style→Partas.Solid.Tags.stylePartas.Solid.Meta.Bindings.Stylesheet→Partas.Solid.Tags.linkPartas.Solid.Meta.Bindings.Title→Partas.Solid.Tags.title
- Direction
- Partas.Solid.Meta.Bindings uses Partas.Solid.Tags, so a change to Partas.Solid.Tags can break Partas.Solid.Meta.Bindings, while a change to Partas.Solid.Meta.Bindings can't break Partas.Solid.Tags.
- Position
- Below the diagonal: Partas.Solid.Meta.Bindings uses a module listed above it, which is the healthy direction.
28→1 Partas.Solid.AST uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.AST.AST→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.AST uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.AST, while a change to Partas.Solid.AST can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.AST uses a module listed above it, which is the healthy direction.
28→25 Partas.Solid.AST uses Partas.Solid✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.AST uses a type in Partas.Solid.
- The types involved
Partas.Solid.AST.AST→Partas.Solid.ElementBuilderPartas.Solid.AST.AST→Partas.Solid.PluginContext
- Direction
- Partas.Solid.AST uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.AST, while a change to Partas.Solid.AST can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.AST uses a module listed above it, which is the healthy direction.
29→1 Partas.Solid.AST.AttributesAndProperties uses Fable.AST.Fable.Expr✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.AST.AttributesAndProperties uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.AST.AttributesAndProperties.AttributesAndProperties→Fable.AST.Fable.Expr.ExprPartas.Solid.AST.AttributesAndProperties.CollectionItem→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.AST.AttributesAndProperties uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.AST.AttributesAndProperties, while a change to Partas.Solid.AST.AttributesAndProperties can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.AST.AttributesAndProperties uses a module listed above it, which is the healthy direction.
29→25 Partas.Solid.AST.AttributesAndProperties uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST.AttributesAndProperties uses a type in Partas.Solid.
- The types involved
Partas.Solid.AST.AttributesAndProperties.AttributesAndProperties→Partas.Solid.PluginContext
- Direction
- Partas.Solid.AST.AttributesAndProperties uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.AST.AttributesAndProperties, while a change to Partas.Solid.AST.AttributesAndProperties can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.AST.AttributesAndProperties uses a module listed above it, which is the healthy direction.
30→1 Partas.Solid.AST.SpecialAttributeTransformation uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST.SpecialAttributeTransformation uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.AST.SpecialAttributeTransformation.SpecialAttributeTransformation→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.AST.SpecialAttributeTransformation uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.AST.SpecialAttributeTransformation, while a change to Partas.Solid.AST.SpecialAttributeTransformation can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.AST.SpecialAttributeTransformation uses a module listed above it, which is the healthy direction.
30→25 Partas.Solid.AST.SpecialAttributeTransformation uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST.SpecialAttributeTransformation uses a type in Partas.Solid.
- The types involved
Partas.Solid.AST.SpecialAttributeTransformation.SpecialAttributeTransformation→Partas.Solid.PluginContext
- Direction
- Partas.Solid.AST.SpecialAttributeTransformation uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.AST.SpecialAttributeTransformation, while a change to Partas.Solid.AST.SpecialAttributeTransformation can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.AST.SpecialAttributeTransformation uses a module listed above it, which is the healthy direction.
31→1 Partas.Solid.AST.TagValue uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST.TagValue uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.AST.TagValue.TagValue→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.AST.TagValue uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.AST.TagValue, while a change to Partas.Solid.AST.TagValue can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.AST.TagValue uses a module listed above it, which is the healthy direction.
31→25 Partas.Solid.AST.TagValue uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.AST.TagValue uses a type in Partas.Solid.
- The types involved
Partas.Solid.AST.TagValue.TagValue→Partas.Solid.PluginContext
- Direction
- Partas.Solid.AST.TagValue uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.AST.TagValue, while a change to Partas.Solid.AST.TagValue can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.AST.TagValue uses a module listed above it, which is the healthy direction.
32→1 Partas.Solid.Baked uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Baked uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.Baked.Baked→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.Baked uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.Baked, while a change to Partas.Solid.Baked can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.Baked uses a module listed above it, which is the healthy direction.
32→25 Partas.Solid.Baked uses Partas.Solid✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.Baked uses a type in Partas.Solid.
- The types involved
Partas.Solid.Baked.Baked→Partas.Solid.ElementBuilderPartas.Solid.Baked.Baked→Partas.Solid.PluginContext
- Direction
- Partas.Solid.Baked uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.Baked, while a change to Partas.Solid.Baked can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.Baked uses a module listed above it, which is the healthy direction.
33→21 Partas.Solid.Experimental uses Partas.Solid.Bindings✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Experimental uses a type in Partas.Solid.Bindings.
- The types involved
Partas.Solid.Experimental.LazyBuilder→Partas.Solid.Bindings.LazyComponent
- Direction
- Partas.Solid.Experimental uses Partas.Solid.Bindings, so a change to Partas.Solid.Bindings can break Partas.Solid.Experimental, while a change to Partas.Solid.Experimental can't break Partas.Solid.Bindings.
- Position
- Below the diagonal: Partas.Solid.Experimental uses a module listed above it, which is the healthy direction.
33→25 Partas.Solid.Experimental uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Experimental uses a type in Partas.Solid.
- The types involved
Partas.Solid.Experimental.ChildrenBuilder→Partas.Solid.ChildrenReturn
- Direction
- Partas.Solid.Experimental uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.Experimental, while a change to Partas.Solid.Experimental can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.Experimental uses a module listed above it, which is the healthy direction.
34→1 Partas.Solid.Expr uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Expr uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.Expr.Expr→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.Expr uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.Expr, while a change to Partas.Solid.Expr can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.Expr uses a module listed above it, which is the healthy direction.
34→25 Partas.Solid.Expr uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.Expr uses a type in Partas.Solid.
- The types involved
Partas.Solid.Expr.Expr→Partas.Solid.PluginContext
- Direction
- Partas.Solid.Expr uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.Expr, while a change to Partas.Solid.Expr can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.Expr uses a module listed above it, which is the healthy direction.
35→1 Partas.Solid.PluginContextModule uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.PluginContextModule uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.PluginContextModule.PluginContextModule→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.PluginContextModule uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.PluginContextModule, while a change to Partas.Solid.PluginContextModule can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.PluginContextModule uses a module listed above it, which is the healthy direction.
35→25 Partas.Solid.PluginContextModule uses Partas.Solid✕
- Connections
- 3 pairs of types, where a type in Partas.Solid.PluginContextModule uses a type in Partas.Solid.
- The types involved
Partas.Solid.PluginContextModule.PluginContextModule→Partas.Solid.ComponentFlagPartas.Solid.PluginContextModule.PluginContextModule→Partas.Solid.PluginContextPartas.Solid.PluginContextModule.PluginContextModule→Partas.Solid.TransformationKind
- Direction
- Partas.Solid.PluginContextModule uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.PluginContextModule, while a change to Partas.Solid.PluginContextModule can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.PluginContextModule uses a module listed above it, which is the healthy direction.
36→1 Partas.Solid.ReactiveMatch uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.ReactiveMatch uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.ReactiveMatch.ReactiveMatch→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.ReactiveMatch uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.ReactiveMatch, while a change to Partas.Solid.ReactiveMatch can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.ReactiveMatch uses a module listed above it, which is the healthy direction.
36→25 Partas.Solid.ReactiveMatch uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.ReactiveMatch uses a type in Partas.Solid.
- The types involved
Partas.Solid.ReactiveMatch.ReactiveMatch→Partas.Solid.PluginContext
- Direction
- Partas.Solid.ReactiveMatch uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.ReactiveMatch, while a change to Partas.Solid.ReactiveMatch can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.ReactiveMatch uses a module listed above it, which is the healthy direction.
37→1 Partas.Solid.StorybookAST uses Fable.AST.Fable.Expr✕
- Connections
- 3 pairs of types, where a type in Partas.Solid.StorybookAST uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.StorybookAST.FieldData→Fable.AST.Fable.Expr.ExprPartas.Solid.StorybookAST.MetaExpr→Fable.AST.Fable.Expr.ExprPartas.Solid.StorybookAST.StorybookAST→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.StorybookAST uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.StorybookAST, while a change to Partas.Solid.StorybookAST can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.StorybookAST uses a module listed above it, which is the healthy direction.
37→25 Partas.Solid.StorybookAST uses Partas.Solid✕
- Connections
- 2 pairs of types, where a type in Partas.Solid.StorybookAST uses a type in Partas.Solid.
- The types involved
Partas.Solid.StorybookAST.StorybookAST→Partas.Solid.FieldTypePartas.Solid.StorybookAST.StorybookAST→Partas.Solid.PluginContext
- Direction
- Partas.Solid.StorybookAST uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.StorybookAST, while a change to Partas.Solid.StorybookAST can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.StorybookAST uses a module listed above it, which is the healthy direction.
38→1 Partas.Solid.StorybookCases uses Fable.AST.Fable.Expr✕
- Connections
- 3 pairs of types, where a type in Partas.Solid.StorybookCases uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.StorybookCases.CasesExpr→Fable.AST.Fable.Expr.ExprPartas.Solid.StorybookCases.CasesInfo→Fable.AST.Fable.Expr.ExprPartas.Solid.StorybookCases.StorybookCases→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.StorybookCases uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.StorybookCases, while a change to Partas.Solid.StorybookCases can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.StorybookCases uses a module listed above it, which is the healthy direction.
38→25 Partas.Solid.StorybookCases uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.StorybookCases uses a type in Partas.Solid.
- The types involved
Partas.Solid.StorybookCases.StorybookCases→Partas.Solid.PluginContext
- Direction
- Partas.Solid.StorybookCases uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.StorybookCases, while a change to Partas.Solid.StorybookCases can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.StorybookCases uses a module listed above it, which is the healthy direction.
39→1 Partas.Solid.StorybookDecorator uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.StorybookDecorator uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.StorybookDecorator.StorybookDecorator→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.StorybookDecorator uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.StorybookDecorator, while a change to Partas.Solid.StorybookDecorator can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.StorybookDecorator uses a module listed above it, which is the healthy direction.
39→25 Partas.Solid.StorybookDecorator uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.StorybookDecorator uses a type in Partas.Solid.
- The types involved
Partas.Solid.StorybookDecorator.StorybookDecorator→Partas.Solid.PluginContext
- Direction
- Partas.Solid.StorybookDecorator uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.StorybookDecorator, while a change to Partas.Solid.StorybookDecorator can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.StorybookDecorator uses a module listed above it, which is the healthy direction.
40→1 Partas.Solid.StorybookRender uses Fable.AST.Fable.Expr✕
- Connections
- 1 pair of types, where a type in Partas.Solid.StorybookRender uses a type in Fable.AST.Fable.Expr.
- The types involved
Partas.Solid.StorybookRender.StorybookRender→Fable.AST.Fable.Expr.Expr
- Direction
- Partas.Solid.StorybookRender uses Fable.AST.Fable.Expr, so a change to Fable.AST.Fable.Expr can break Partas.Solid.StorybookRender, while a change to Partas.Solid.StorybookRender can't break Fable.AST.Fable.Expr.
- Position
- Below the diagonal: Partas.Solid.StorybookRender uses a module listed above it, which is the healthy direction.
40→25 Partas.Solid.StorybookRender uses Partas.Solid✕
- Connections
- 1 pair of types, where a type in Partas.Solid.StorybookRender uses a type in Partas.Solid.
- The types involved
Partas.Solid.StorybookRender.StorybookRender→Partas.Solid.PluginContext
- Direction
- Partas.Solid.StorybookRender uses Partas.Solid, so a change to Partas.Solid can break Partas.Solid.StorybookRender, while a change to Partas.Solid.StorybookRender can't break Partas.Solid.
- Position
- Below the diagonal: Partas.Solid.StorybookRender uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj. | +4.8 pts | Low | ADR Quality |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Style.fs. | +3.7 pts | Low | Knowledge Freshness |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +6.3 pts | Medium | Dependency Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.7 pts | Medium | Architecture documentation |
| Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI. | +3.1 pts | Medium | Tooling |
| Expand the README with getting-started, architecture overview and a project map. | +2.9 pts | Medium | Documentation (README) |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.6 pts | Medium | Type Safety |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.0 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Partas.Solid.FablePlugin/Storybook.fs | 7.2 | Mixed | God Classes: FileTooLong: Partas.Solid.FablePlugin/Storybook.fs |
| src/Partas.Solid/Tags.fs | 7.2 | Mixed | God Classes: FileTooLong: Partas.Solid/Tags.fs |
| src/Partas.Solid/Style.fs | 7.4 | Mixed | God Classes: TooManyMethods: Style |
| src/Partas.Solid/SolidBindings.fs | 7.4 | Mixed | God Classes: TooManyMethods: Bindings |
| tests/Partas.Solid.Tests.Runtime/Integration/Router/Router.test.js | 7.4 | Mixed | Test Quality: No assertions: streams a live query's values through a memo |
| src/Partas.Solid.FablePlugin/Plugin.fs | 7.8 | Mixed | God Classes: FileTooLong: Partas.Solid.FablePlugin/Plugin.fs |
| src/Partas.Solid/AttributesAliasesExtensions.fs | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/Partas.Solid.FablePlugin/Partas.Solid.FablePlugin.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/Partas.Solid.FablePlugin/Utils.fs | 8.5 | Near-clean | God Classes: FileTooLong: Partas.Solid.FablePlugin/Utils.fs |
| tools/Partas.Nacara.Plugins.Solid/Scan.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (7–8 lines × 2) |
| tools/JsxGen/ProfilesEmit.fs | 9.3 | Near-clean | Naming Consistency: `renderSvg` spells `Svg` where 111 names in the project spell it `SVG` |
| docs/site/docs.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
| src/Partas.Solid/Builder.fs | 9.5 | Near-clean | Naming Consistency: `IntrinsicDOMElement` spells `DOM` where 118 names in the project spell it `Dom` |
| tests/Partas.Solid.Tests.Runtime/Dom/Portals/B-Dynamic.fs | 9.5 | Near-clean | Naming Consistency: `DynamicSvg` spells `Svg` where 111 names in the project spell it `SVG` |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 44 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, 43 of 57 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D6 Cohesion (LCOM4) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 23 of 32 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 933 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 156 test source file(s) (.fs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: NU1301: Unable to load the service index for source https://nuget.cloudsmith.io/shayanhabibi/xantham/v3/index.json. [Partas.Solid.slnx] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [Partas.Solid.slnx]. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to nuget.cloudsmith.io, and a re-run with it reachable measures this repository.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (67200 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 266 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Nuget.cloudsmith.io could not be reached (NU1301: Unable to load the service index for source https://nuget.cloudsmith.io/shayanhabibi/xantham/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a UI framework dependency ('solid-js'). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit 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 audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention 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 retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights 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 data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for docs/site/docs.fsproj, src/Partas.Solid/Partas.Solid.fsproj, tests/Partas.Solid.Tests.Plugin/Compiled/Partas.Solid.Tests.Plugin.Compiled.fsproj, tests/Partas.Solid.Tests.Plugin/Partas.Solid.Tests.Plugin.fsproj, tests/Partas.Solid.Tests.Runtime/Dom/Partas.Solid.Tests.Runtime.Dom.fsproj and 4 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 6 FileTooLong finding(s) in God Classes — start with Style.fs, Storybook.fs, Plugin.fs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with Style.fs (2), SolidBindings.fs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 2.1 % of the production lines (323 of 15,640) are in a reported copy. 1 of the 11 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Duplicated block (40 lines × 2) finding(s) in Code Duplication — start with Storybook.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18 lines × 3) finding(s) in Code Duplication — start with Tags.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 5) finding(s) in Code Duplication — start with Tags.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D10 · Test Quality
2 skipped (2 with a documented reason), 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 933 tests. Measured on the JavaScript/TypeScript suite only — at least 156 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 3 No assertions finding(s) in Test Quality — start with Router.test.js (3). — One of this dimension's main actionable groups (3 warning-level).
D11 · Test Reliability
0 flaky across 3 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky); JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in tests/Partas.Solid.Tests.Runtime/ (0 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 132 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 26 direct `PackageReference`(s), and 103 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
4 naming inconsistencies among 233 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `IntrinsicDOMElement` spells `DOM` where 118 names in the project spell… finding(s) in Naming Consistency — start with Builder.fs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `DynamicSvg` spells `Svg` where 111 names in the project spell it `SVG` finding(s) in Naming Consistency — start with B-Dynamic.fs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `renderSvg` spells `Svg` where 111 names in the project spell it `SVG` finding(s) in Naming Consistency — start with ProfilesEmit.fs. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 157 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 6 build units (MSBuild, npm) 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).
D27 · Navigability
86 % of calls cross a namespace and 3 % go through an interface, but 74 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: nuget.cloudsmith.io could not be reached (NU1301: Unable to load the service index for source https://nuget.cloudsmith.io/shayanhabibi/xantham/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.)), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
1 of 29 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Partas.Solid/Style.fs. Counted over 29 of the 32 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Style.fs. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Partas.Solid.FablePlugin.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
- The root README is 84 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/site/content/guide/installation.md names FSharp.Core 10, but the manifest declares `FSharp.Core` 11.0.101-rc1.26425.128. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/site/content/guide/installation.md:25
What to do
- Reconcile the README with reality: docs/site/content/guide/installation.md names FSharp.Core 10, but the manifest declares `FSharp.Core` 11.0.101-rc1.26425.128.
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/site`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 3 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. — .github/workflows/dotnet.yml:6
- `docs/site/docs.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — docs/site/docs.fsproj:13
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
R1 · Type Safety
- 0 typed · 88 plain JS — the untyped files are tests/Partas.Solid.Tests.Runtime/Dom/Elements/A-Structure.test.js, tests/Partas.Solid.Tests.Runtime/Dom/Elements/B-Attributes.test.js, tests/Partas.Solid.Tests.Runtime/Dom/Elements/C-Events.test.js, tests/Partas.Solid.Tests.Runtime/Dom/Elements/D-Refs.test.js, tests/Partas.Solid.Tests.Runtime/Dom/Elements/E-Svg.test.js, tests/Partas.Solid.Tests.Runtime/Dom/Elements/F-Spread.test.js (+82 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- 9 file(s) (~478 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: tools/JsxStress/runtime.test.jsx imports '../../.research/jsx-stress/Partas/IfTwoElements.fs.jsx', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×6) — tools/JsxStress/check.mjs:10, tools/JsxStress/check.mjs:132, tools/Partas.Nacara.Plugins.Solid/assets/bundle.mjs:8, …
- Declared in tests/Partas.Solid.Tests.Runtime/package.json but never imported anywhere in that package or its workspace members — while tools/Partas.Nacara.Plugins.Solid/assets/bundle.mjs DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
- Declared in tests/Partas.Solid.Tests.Runtime/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Checked 7 of 16 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 34% | Weak — gated by R6, R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's F# 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 F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D12 Dependency Hygiene — Dependency hygiene not measured — nuget.cloudsmith.io could not be reached
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- 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.
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — the coverage run wrote reports, but they instrument no source line — nothing was measured; the JavaScript/TypeScript half could not be measured — tests/Partas.Solid.Tests.Runtime/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 158 value object(s); 10 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — no production JavaScript/TypeScript files to cover (83 test file(s) present) — nothing to measure
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 7 finding(s)
- Orphaned knowledge src/Partas.Solid/Style.fs:1
- Unlisted import '@babel/core' tools/JsxStress/check.mjs:10
- Unlisted import '@babel/parser' tools/JsxStress/check.mjs:132
- Unlisted import '@solidjs/compiler' tools/Partas.Nacara.Plugins.Solid/assets/bundle.mjs:8
- Unlisted import '@solidjs/vite-plugin' tools/JsxStress/vitest.config.mjs:6
- Unlisted import '@solidjs/web' tools/JsxStress/runtime.test.jsx:2
- Unlisted import 'rolldown' tools/Partas.Nacara.Plugins.Solid/assets/bundle.mjs:7
Serious — 32 finding(s)
- FileTooLong: Partas.Solid/Style.fs src/Partas.Solid/Style.fs
- FileTooLong: Partas.Solid.FablePlugin/Storybook.fs src/Partas.Solid.FablePlugin/Storybook.fs
- FileTooLong: Partas.Solid.FablePlugin/Plugin.fs src/Partas.Solid.FablePlugin/Plugin.fs
- FileTooLong: Partas.Solid/SolidBindings.fs src/Partas.Solid/SolidBindings.fs
- FileTooLong: Partas.Solid/Tags.fs src/Partas.Solid/Tags.fs
- FileTooLong: Partas.Solid.FablePlugin/Utils.fs src/Partas.Solid.FablePlugin/Utils.fs
- No assertions: streams a live query's values through a memo tests/Partas.Solid.Tests.Runtime/Integration/Router/Router.test.js:124
- No assertions: calls an action through useAction and lists its settled submissions tests/Partas.Solid.Tests.Runtime/Integration/Router/Router.test.js:140
- No assertions: posts a form to an action with a bound argument tests/Partas.Solid.Tests.Runtime/Integration/Router/Router.test.js:147
- TooManyMethods: Style src/Partas.Solid/Style.fs:12
- TooManyMethods: Bindings src/Partas.Solid/SolidBindings.fs:622
- TooManyMethods: SvgStyle src/Partas.Solid/Style.fs:3875
- REDACTED
- Duplicated block (40 lines × 2) src/Partas.Solid.FablePlugin/Storybook.fs:684
- Duplicated block (18 lines × 3) src/Partas.Solid/Tags.fs:321
- Duplicated block (13 lines × 5) src/Partas.Solid/Tags.fs:153
- Duplicated block (13 lines × 3) src/Partas.Solid/Tags.fs:137
- Duplicated block (8 lines × 2) src/Partas.Solid/AttributesAliasesExtensions.fs:192
- Duplicated block (7 lines × 2) src/Partas.Solid.FablePlugin/Plugin.fs:478
- Duplicated block (9 lines × 2) src/Partas.Solid/SolidBindings.fs:441
- Duplicated block (15 lines × 2) src/Partas.Solid.FablePlugin/Storybook.fs:633
- Duplicated block (11 lines × 2) src/Partas.Solid.FablePlugin/Storybook.fs:620
- Duplicated block (5 lines × 5) src/Partas.Solid/AttributesAliasesExtensions.fs:126
- Duplicated block (7–8 lines × 2) tools/Partas.Nacara.Plugins.Solid/Scan.fs:284
- End-of-life runtime: .NET net6.0 src/Partas.Solid.FablePlugin/Partas.Solid.FablePlugin.fsproj:3
- Coverage not measured — .NET and JavaScript/TypeScript suite
- Type Safety
- No lint or typecheck script
- Unused dependency '@solidjs/compiler'
- Unused dependency '@solidjs/meta'
- Unused dependency '@solidjs/router'
- NuGet dependencies are not locked
Minor — 16 finding(s)
- No ADRs found docs/site/docs.fsproj:3
- `IntrinsicDOMElement` spells `DOM` where 118 names in the project spell it `Dom` src/Partas.Solid/Builder.fs:25
- `DynamicSvg` spells `Svg` where 111 names in the project spell it `SVG` tests/Partas.Solid.Tests.Runtime/Dom/Portals/B-Dynamic.fs:97
- `renderSvg` spells `Svg` where 111 names in the project spell it `SVG` tools/JsxGen/ProfilesEmit.fs:90
- `existingSvg` spells `Svg` where 111 names in the project spell it `SVG` tools/JsxGen/ProfilesEmit.fs:90
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- README/code drift docs/site/content/guide/installation.md:25
- Logging is not universal
- No SAST .github/workflows/dotnet.yml:6
- No dependency-update automation docs/site/docs.fsproj:13
Minor — 2 finding(s)
- Skipped (documented): Oxpecker preserves a statement and following child tools/JsxStress/runtime.test.jsx:48
- Skipped (documented): a reactive mount moves the content between nodes tests/Partas.Solid.Tests.Runtime/Dom/Portals/Portal.test.js:155
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8d7227a000fe4b52ad4c3804647dd228/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8d7227a000fe4b52ad4c3804647dd228/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Partas.Solid.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |