Executive summary
nfdi4plants/Swate falls short of our standard for production because seven passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 46 out of 100 and is rated Weak, and 77 of its 146 critical findings are security problems.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step is replacing the seven exposed passwords or keys and switching the old ones off, worth about 13 points. Adding automated security scanning comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 58.
Twenty-nine known security holes in the packages the code depends on can be used by attackers. Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-five form fields can't be read by a screen reader. Updating the vulnerable packages, pinning each tool to an exact version and labelling the form fields would close these risks. The seven passwords or keys in the code and the six passwords or keys in the code's history need replacing, with the old ones switched off. The five unsafe settings in infrastructure or container files need changing to safe values. The 19 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 114,170 lines, about €160,000 to rebuild.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 46 to about 58.
New since the last survey: 70 findings
- God Classes · FileTooLong: ArcVault/ArcVaultFileWatcher.fs src/Electron/src/Main/ArcVault/ArcVaultFileWatcher.fs
- God Classes · FileTooLong: Shared/PathHelpers.fs src/Shared/PathHelpers.fs
- God Classes · FileTooLong: ProvenanceGraph/ProvenanceGraph.fs src/Components/src/Page/ProvenanceGraph/ProvenanceGraph.fs
- God Classes · FileTooLong: FileExplorer/FileExplorer.fs src/Components/src/Page/FileExplorer/FileExplorer.fs
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- Churn × Complexity Hotspots · Hotspot: src/Components/src/Page/FileExplorer/FileExplorer.fs src/Components/src/Page/FileExplorer/FileExplorer.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Renderer/Components/MainContent/ArcFilePreviewTarget.fs src/Electron/src/Renderer/Components/MainContent/ArcFilePreviewTarget.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Swate.Electron.Shared/FileIOHelper.fs src/Electron/src/Swate.Electron.Shared/FileIOHelper.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Renderer/Components/Helper/FileExplorerStateReconciliation.fs src/Electron/src/Renderer/Components/Helper/FileExplorerStateReconciliation.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Renderer/Context/FileTreeExpansionContext.fs src/Electron/src/Renderer/Context/FileTreeExpansionContext.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Renderer/Context/FileTreeStore.fs src/Electron/src/Renderer/Context/FileTreeStore.fs
- Churn × Complexity Hotspots · Hotspot: src/Components/src/Page/ProvenanceGraph/OverviewNav.fs src/Components/src/Page/ProvenanceGraph/OverviewNav.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Main/IndexedFileTree.fs src/Electron/src/Main/IndexedFileTree.fs
- Churn × Complexity Hotspots · Hotspot: src/Components/src/Page/FileExplorer/Types.fs src/Components/src/Page/FileExplorer/Types.fs
- Churn × Complexity Hotspots · Hotspot: src/Electron/src/Main/ArcVault/ArcVaultFileWatcher.fs src/Electron/src/Main/ArcVault/ArcVaultFileWatcher.fs
- Churn × Complexity Hotspots · Hotspot: src/Components/src/Page/Metadata/FormComponents/PersonsInput/PersonImportDialog.fs src/Components/src/Page/Metadata/FormComponents/PersonsInput/PersonImportDialog.fs
- Churn × Complexity Hotspots · Repeated repair: src/Components/src/Composite/TemplateBrowser/Helper.fs src/Components/src/Composite/TemplateBrowser/Helper.fs
- Secrets (history) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: FileTreeCreator.fs ↔ FileExplorerLfs.fs src/Electron/src/Main/FileTreeCreator.fs
- Change Coupling · Change coupling: FileExplorer.stories.tsx ↔ FileExplorerItem.fs src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Large Files · REDACTED: 2449 lines of code REDACTED
- Large Files · src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx: 945 lines of code src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx
- Large Files · src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx: 800 lines of code src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx
- Large Files · src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx: 647 lines of code src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Electron/src/Renderer/tailwind.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/tailwind.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Client/tailwind.css
Fixed since the last survey: 328 findings
- Cyclomatic Complexity · GitWorkflow.updateCore (cyclomatic 227) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ProvenanceGrouping.Main (cyclomatic 180) src/Components/src/Page/ProvenanceGrouping/ProvenanceGrouping.fs
- Cyclomatic Complexity · GitPagedDiffViewer.Grid (cyclomatic 166) src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs
- Cyclomatic Complexity · ArcVaultsApi.api (cyclomatic 145) src/Electron/src/Main/IPC/IArcVaultsApi.fs
- Cyclomatic Complexity · Interface.update (cyclomatic 77) src/Client/Update/InterfaceUpdate.fs
- Cyclomatic Complexity · TextInputWithMarkdown.TextInputWithMarkdown (cyclomatic 76) src/Components/src/Composite/MarkdownText/TextInputWithMarkdown.fs
- Cyclomatic Complexity · GraphCanvas.GraphCanvas (cyclomatic 70) src/Components/src/Composite/GraphCanvas/GraphCanvas.fs
- Cyclomatic Complexity · FileTree.FileTree (cyclomatic 66) src/Electron/src/Renderer/Components/LeftSidebar/FileExplorer/FileTree.fs
- Cyclomatic Complexity · GitDiffPageLoader.updatePage (cyclomatic 65) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · TutorialOverlay.Main (cyclomatic 63) src/Components/src/Composite/TutorialOverlay/TutorialOverlay.fs
- Cyclomatic Complexity · Controls.PropertyRailItem (cyclomatic 60) src/Components/src/Page/ProvenanceGrouping/Controls.fs
- Cyclomatic Complexity · TermSearch.TermSearch (cyclomatic 55) src/Components/src/Composite/TermSearch/TermSearch.fs
- Cyclomatic Complexity · IVersionControlApi.api (cyclomatic 54) src/Electron/src/Main/IPC/IVersionControlApi.fs
- Cyclomatic Complexity · Spreadsheet.update (cyclomatic 52) src/Client/Update/SpreadsheetUpdate.fs
- Cyclomatic Complexity · GroupCard.Main (cyclomatic 50) src/Components/src/Page/ProvenanceGrouping/GroupCard.fs
- Cyclomatic Complexity · DropOverlay.DropOverlay (cyclomatic 47) src/Components/src/Composite/Workspace/DropOverlay.fs
- Cyclomatic Complexity · GitSidebar.Main (cyclomatic 46) src/Components/src/Page/GitSidebar/GitSidebar.fs
- Cyclomatic Complexity · ConnectorOverlay.Main (cyclomatic 41) src/Components/src/Page/ProvenanceGrouping/ConnectorOverlay.fs
- Cyclomatic Complexity · Build.main (cyclomatic 39) build/Build.fs
- Cyclomatic Complexity · GitMergeConflictViewer.Viewer (cyclomatic 38) src/Components/src/Page/GitComparison/GitMergeConflictViewer.fs
- Cyclomatic Complexity · PersonSearchDialog.PersonSearchDialog (cyclomatic 38) src/Components/src/Page/Metadata/FormComponents/PersonsInput/PersonSearchDialog.fs
- Cyclomatic Complexity · Table.Table (cyclomatic 38) src/Components/src/Composite/Table/Table.fs
- Cyclomatic Complexity · GitPagedDiffViewer.RowView (cyclomatic 36) src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs
- Cyclomatic Complexity · GitWorkflow.runPublishAsync (cyclomatic 36) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ARCitect.update (cyclomatic 34) src/Client/Update/ARCitectUpdate.fs
- Cyclomatic Complexity · DataHubBrowser.ExplorePanel (cyclomatic 34) src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs
- Cyclomatic Complexity · GitPagedDiffViewer.Viewer (cyclomatic 33) src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs
- Cyclomatic Complexity · PublicationSearchDialog.PublicationSearchDialog (cyclomatic 33) src/Components/src/Page/Metadata/FormComponents/PublicationsInput/PublicationSearchDialog.fs
- Cyclomatic Complexity · GitWorkflow.runPrimarySaveAttemptAsync (cyclomatic 33) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ArcVaultExtensions.ArcVault._FileEventController (cyclomatic 31) src/Electron/src/Main/ArcVault/ArcVault.fs
- Cyclomatic Complexity · DataAnnotator.Table (cyclomatic 29) src/Components/src/Composite/Widgets/DataAnnotator/DataAnnotator.fs
- Cyclomatic Complexity · FolderedDraggableList.FolderedDraggableList (cyclomatic 29) src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.fs
- Cyclomatic Complexity · BuildIndex.readRow (cyclomatic 29) src/Shared/ProvenanceGraph/BuildIndex.fs
- Cyclomatic Complexity · Controls.ValueChip (cyclomatic 27) src/Components/src/Page/ProvenanceGrouping/Controls.fs
- Cyclomatic Complexity · GitWorkflow.confirmMergeResolutionAsync (cyclomatic 27) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ProvenanceGraph.Header (cyclomatic 26) src/Components/src/Page/ProvenanceGraph/ProvenanceGraph.fs
- Cyclomatic Complexity · Controls.PropertyRail (cyclomatic 26) src/Components/src/Page/ProvenanceGrouping/Controls.fs
- Cyclomatic Complexity · GitDiffTarget.Main (cyclomatic 26) src/Electron/src/Renderer/Components/MainContent/GitDiffTarget.fs
- Cyclomatic Complexity · ArcFileFooterTabs.Main (cyclomatic 25) src/Components/src/Page/ArcFileEditor/ArcFileFooterTabs.fs
- Cyclomatic Complexity · DataHubBrowser.Entry (cyclomatic 25) src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs
- Cyclomatic Complexity · Layout.Sidebars (cyclomatic 25) src/Components/src/Composite/Layout/Layout.fs
- Cyclomatic Complexity · V2.ontologyApi (cyclomatic 25) src/Server/Api/IOntologyAPI.fs
- Cyclomatic Complexity · DataHubBrowserModel.update (cyclomatic 24) src/Components/src/Page/DataHubBrowser/Model.fs
- Cyclomatic Complexity · Main.tryParseToArcFile (cyclomatic 23) src/Client/OfficeInterop/OfficeInterop.fs
- Cyclomatic Complexity · V1.ontologyApi (cyclomatic 23) src/Server/Api/IOntologyAPI.fs
- Cyclomatic Complexity · GitDiffPageLoader.updateWithReopen (cyclomatic 23) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ArcVaults.OnCloseWindow (cyclomatic 23) src/Electron/src/Main/ArcVault/ArcVault.fs
- Cyclomatic Complexity · FormComponents.TextInput (cyclomatic 22) src/Client/SharedComponents/Metadata/Forms.fs
- Cyclomatic Complexity · FileExplorerItem.LFSStatusPill (cyclomatic 22) src/Components/src/Page/FileExplorer/FileExplorerItem.fs
- Cyclomatic Complexity · GitPagedDiffViewer.LineContent (cyclomatic 22) src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs
- Cyclomatic Complexity · GraphCanvas.PillMenu (cyclomatic 22) src/Components/src/Composite/GraphCanvas/GraphCanvas.fs
- Cyclomatic Complexity · DataAnnotator.Main (cyclomatic 22) src/Components/src/Composite/Widgets/DataAnnotator/DataAnnotator.fs
- Cyclomatic Complexity · ComboBox.ComboBox (cyclomatic 22) src/Components/src/Primitive/ComboBox/ComboBox.fs
- Cyclomatic Complexity · ArcEntityPathRules.classifyDeleteTarget (cyclomatic 22) src/Shared/PathHelpers.fs
- Cyclomatic Complexity · GitDiffPageLoader.evict (cyclomatic 22) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · ArcVaultHelper.updateARCByFileContentDTO (cyclomatic 22) src/Electron/src/Main/ArcVault/ArcVaultHelper.fs
- Cyclomatic Complexity · FormComponents.ValueInput (cyclomatic 21) src/Client/SharedComponents/Metadata/Forms.fs
- Cyclomatic Complexity · DataHubBrowser.Filter (cyclomatic 21) src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs
- Cyclomatic Complexity · FileExplorer.FileExplorer (cyclomatic 21) src/Components/src/Page/FileExplorer/FileExplorer.fs
- Cyclomatic Complexity · GitSidebar.OperationStatusNotice (cyclomatic 21) src/Components/src/Page/GitSidebar/GitSidebar.fs
- Cyclomatic Complexity · GitSidebar.PublishRenameDialog (cyclomatic 21) src/Components/src/Page/GitSidebar/GitSidebar.fs
- Cyclomatic Complexity · TextInput.TextInput (cyclomatic 21) src/Components/src/Page/Metadata/FormComponents/TextInput.fs
- Cyclomatic Complexity · AnnotationTableContextMenuUtil.getFittedCells (cyclomatic 21) src/Components/src/Composite/AnnotationTable/ContextMenu.fs
- Cyclomatic Complexity · ContextMenu.ContextMenu (cyclomatic 21) src/Components/src/Primitive/ContextMenu/ContextMenu.fs
- Cyclomatic Complexity · MessageInteropHelper.buildInProxyInner (cyclomatic 20) src/Client/Util/MessageInterop.fs
- Cyclomatic Complexity · Notes.Wizard (cyclomatic 20) src/Components/src/Composite/Notes/Editor/Notes.fs
- Cyclomatic Complexity · SortableList.SortableList (cyclomatic 20) src/Components/src/Composite/SortableList/SortableList.fs
- Cyclomatic Complexity · Queries.processDetail (cyclomatic 19) src/Shared/ProvenanceGraph/Queries.fs
- Cyclomatic Complexity · ArcVaultExtensions.ArcVault.TryApplyWatcherArcMergeIfEligible (cyclomatic 19) src/Electron/src/Main/ArcVault/ArcVault.fs
- Cyclomatic Complexity · ArcVaultExtensions.ArcVault.RenameOpenArcRoot (cyclomatic 19) src/Electron/src/Main/ArcVault/ArcVault.fs
- Cyclomatic Complexity · SpreadsheetView.Main (cyclomatic 18) src/Client/Views/SpreadsheetView.fs
- Cyclomatic Complexity · ProtocolState.update (cyclomatic 18) src/Client/Pages/ProtocolTemplates/ProtocolState.fs
- Cyclomatic Complexity · LazyLoadTable.Main (cyclomatic 18) src/Client/SharedComponents/LazyLoadTable.fs
- Cyclomatic Complexity · ProvenanceGraph.ProvenanceGraph (cyclomatic 18) src/Components/src/Page/ProvenanceGraph/ProvenanceGraph.fs
- Cyclomatic Complexity · GroupCard.OrganizerTab (cyclomatic 18) src/Components/src/Page/ProvenanceGrouping/GroupCard.fs
- Cyclomatic Complexity · Layout.layoutGraph (cyclomatic 18) src/Components/src/Composite/GraphCanvas/Layout.fs
- Cyclomatic Complexity · DataMapTable.DataMapTable (cyclomatic 18) src/Components/src/Composite/DataMapTable/DataMapTable.fs
- Cyclomatic Complexity · AnnotationTableContextMenuUtil.pasteCells (cyclomatic 18) src/Components/src/Composite/AnnotationTable/ContextMenu.fs
- Cyclomatic Complexity · GitWorkflow.routeFailure (cyclomatic 18) src/Electron/src/Renderer/Context/GitWorkflow.fs
- Cyclomatic Complexity · FileStateContext.FileStateCtxProviderWithSnapshots (cyclomatic 18) src/Electron/src/Renderer/Context/FileStateContext.fs
- Cyclomatic Complexity · Main.fillSelectedWithOntologyAnnotation (cyclomatic 17) src/Client/OfficeInterop/OfficeInterop.fs
- Cyclomatic Complexity · MergeConflicts.parseMergeConflictFragments (cyclomatic 17) src/Components/src/Page/GitComparison/GitTextComparison.Core.fs
- Cyclomatic Complexity · Controls.FilterToolbar (cyclomatic 17) src/Components/src/Page/ProvenanceGrouping/Controls.fs
- Cyclomatic Complexity · BuildingBlockWidget.Main (cyclomatic 17) src/Components/src/Composite/Widgets/BuildingBlockWidget/BuildingBlockWidget.fs
- Cyclomatic Complexity · JsonImport.JsonImport (cyclomatic 17) src/Components/src/Composite/Widgets/JsonImport/JsonImport.fs
- Cyclomatic Complexity · TargetSelector.Main (cyclomatic 17) src/Components/src/Composite/Notes/Editor/TargetSelector.fs
- Cyclomatic Complexity · AnnotationTable.ModalController (cyclomatic 17) src/Components/src/Composite/AnnotationTable/AnnotationTable.fs
- Cyclomatic Complexity · SemVer.SemVer.comparePreRelease.Static (cyclomatic 17) src/Components/src/Util/SemVer.fs
- Cyclomatic Complexity · ArcEntityPathRules.classifyRenameTarget (cyclomatic 17) src/Shared/PathHelpers.fs
- Cyclomatic Complexity · Main.convertBuildingBlock (cyclomatic 16) src/Client/OfficeInterop/OfficeInterop.fs
- Cyclomatic Complexity · FileExplorerItem.DirectoryRow (cyclomatic 16) src/Components/src/Page/FileExplorer/FileExplorerItem.fs
- Cyclomatic Complexity · Controls.ConnectionHandle (cyclomatic 16) src/Components/src/Page/ProvenanceGrouping/Controls.fs
- Cyclomatic Complexity · FlipColumn.View (cyclomatic 16) src/Components/src/Page/ProvenanceGrouping/ViewSupport.fs
- Cyclomatic Complexity · GridSelect.GetNextIndex (cyclomatic 16) src/Components/src/Composite/Table/KeyboardNavigation.fs
- Cyclomatic Complexity · TermSearch.TermItem (cyclomatic 16) src/Components/src/Composite/TermSearch/TermSearch.fs
- Cyclomatic Complexity · ErrorModalProvider.ErrorModalHost (cyclomatic 16) src/Components/src/Primitive/ErrorModal/Provider.fs
- Cyclomatic Complexity · Blankslate.Blankslate (cyclomatic 16) src/Components/src/Primitive/Blankslate/Blankslate.fs
- Cyclomatic Complexity · EmptyColumnJson.normalize (cyclomatic 16) src/Components/src/ARCtrl/EmptyColumnJson.fs
- Cyclomatic Complexity · BuildIndex.fillProcess (cyclomatic 16) src/Shared/ProvenanceGraph/BuildIndex.fs
- Cyclomatic Complexity · GitDiffTarget.backgroundReadingOf (cyclomatic 16) src/Electron/src/Renderer/Components/MainContent/GitDiffTarget.fs
Rebuild cost: about €160,000 · Estimate
| Cost to rebuild | €52,000 to €260,000, for 863 to 2,737 hours of work, about 1.1 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 46. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Large: 114,170 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 ARCtrl | 2 InteropLogging | 3 Main.ArcVaultState | 4 Routing | 5 Swate.Components | 6 Swate.Components.Api.GitLabApi | 7 Swate.Components.Composite.Authentication.Types | 8 Swate.Components.Composite.GraphCanvas.Types | 9 Swate.Components.Composite.MarkdownText.Plugins | 10 Swate.Components.Composite.TermSearch.Types | 11 Swate.Components.Composite.Widgets.Types | 12 Swate.Components.Page.FileExplorer.Types | 13 Swate.Components.Shared | 14 Swate.Components.Shared.ARCtrlHelper | 15 Swate.Components.Shared.Database | 16 Swate.Components.Shared.ProvenanceGraph.Types | 17 Swate.Components.Shared.ProvenanceGrouping.Types | 18 Swate.Electron.Shared.DTOs.ProvenanceGroupingDto | 19 Swate.Electron.Shared.FileIOTypes | 20 Swate.Electron.Shared.IPCTypes | 21 Swate.Electron.Shared.VersionControlTypes | 22 Types.FileImport | 23 Renderer.Components.LeftSidebar.FileExplorer.Types | 24 Renderer.Context.FileTreeStore | 25 Swate.Components.Composite.AnnotationTable | 26 Swate.Components.Page.ArcFileEditor.Types | 27 Swate.Components.Page.Landing | 28 Swate.Components.Page.ProvenanceGraph.Types | 29 Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter | 30 Swate.Components.Shared.ProvenanceGrouping.Edit | 31 Swate.Components.Shared.ProvenanceGrouping.Grouping | 32 Renderer.Types | 33 Spreadsheet | 34 Swate.Components.Shared.ProvenanceGrouping.Session | 35 Model | 36 Renderer.Context.GitWorkflow | 37 Swate.Components.Page.ProvenanceGrouping.Types | 38 MessagesModule | 39 Swate.Components.Page.ProvenanceGrouping | 40 Swate.Components.Page.ProvenanceGrouping.DragHandlers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ARCtrl | ||||||||||||||||||||||||||||||||||||||||
| 2 InteropLogging | ||||||||||||||||||||||||||||||||||||||||
| 3 Main.ArcVaultState | ||||||||||||||||||||||||||||||||||||||||
| 4 Routing | ||||||||||||||||||||||||||||||||||||||||
| 5 Swate.Components | ||||||||||||||||||||||||||||||||||||||||
| 6 Swate.Components.Api.GitLabApi | ||||||||||||||||||||||||||||||||||||||||
| 7 Swate.Components.Composite.Authentication.Types | ||||||||||||||||||||||||||||||||||||||||
| 8 Swate.Components.Composite.GraphCanvas.Types | ||||||||||||||||||||||||||||||||||||||||
| 9 Swate.Components.Composite.MarkdownText.Plugins | ||||||||||||||||||||||||||||||||||||||||
| 10 Swate.Components.Composite.TermSearch.Types | ||||||||||||||||||||||||||||||||||||||||
| 11 Swate.Components.Composite.Widgets.Types | ||||||||||||||||||||||||||||||||||||||||
| 12 Swate.Components.Page.FileExplorer.Types | ||||||||||||||||||||||||||||||||||||||||
| 13 Swate.Components.Shared | ||||||||||||||||||||||||||||||||||||||||
| 14 Swate.Components.Shared.ARCtrlHelper | ||||||||||||||||||||||||||||||||||||||||
| 15 Swate.Components.Shared.Database | ||||||||||||||||||||||||||||||||||||||||
| 16 Swate.Components.Shared.ProvenanceGraph.Types | ||||||||||||||||||||||||||||||||||||||||
| 17 Swate.Components.Shared.ProvenanceGrouping.Types | ||||||||||||||||||||||||||||||||||||||||
| 18 Swate.Electron.Shared.DTOs.ProvenanceGroupingDto | ||||||||||||||||||||||||||||||||||||||||
| 19 Swate.Electron.Shared.FileIOTypes | ||||||||||||||||||||||||||||||||||||||||
| 20 Swate.Electron.Shared.IPCTypes | ||||||||||||||||||||||||||||||||||||||||
| 21 Swate.Electron.Shared.VersionControlTypes | ||||||||||||||||||||||||||||||||||||||||
| 22 Types.FileImport | ||||||||||||||||||||||||||||||||||||||||
| 23 Renderer.Components.LeftSidebar.FileExplorer.Types | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Renderer.Context.FileTreeStore | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 25 Swate.Components.Composite.AnnotationTable | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Swate.Components.Page.ArcFileEditor.Types | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Swate.Components.Page.Landing | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Swate.Components.Page.ProvenanceGraph.Types | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter | 10 | |||||||||||||||||||||||||||||||||||||||
| 30 Swate.Components.Shared.ProvenanceGrouping.Edit | 22 | |||||||||||||||||||||||||||||||||||||||
| 31 Swate.Components.Shared.ProvenanceGrouping.Grouping | 13 | |||||||||||||||||||||||||||||||||||||||
| 32 Renderer.Types | 1 | 1 | 12 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 Spreadsheet | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 Swate.Components.Shared.ProvenanceGrouping.Session | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Model | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Renderer.Context.GitWorkflow | 1 | 3 | 47 | 7 | ||||||||||||||||||||||||||||||||||||
| 37 Swate.Components.Page.ProvenanceGrouping.Types | 14 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 MessagesModule | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Swate.Components.Page.ProvenanceGrouping | 16 | 6 | 5 | 7 | ||||||||||||||||||||||||||||||||||||
| 40 Swate.Components.Page.ProvenanceGrouping.DragHandlers | 2 | 1 | 1 | 1 | 1 |
23→12 Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Components.Page.FileExplorer.Types✕
- Connections
- 2 pairs of types, where a type in Renderer.Components.LeftSidebar.FileExplorer.Types uses a type in Swate.Components.Page.FileExplorer.Types.
- The types involved
Renderer.Components.LeftSidebar.FileExplorer.Types.ArcRenameDraft→Swate.Components.Page.FileExplorer.Types.FileItemRenderer.Components.LeftSidebar.FileExplorer.Types.FileSystemCreateDraft→Swate.Components.Page.FileExplorer.Types.FileItem
- Direction
- Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Components.Page.FileExplorer.Types, so a change to Swate.Components.Page.FileExplorer.Types can break Renderer.Components.LeftSidebar.FileExplorer.Types, while a change to Renderer.Components.LeftSidebar.FileExplorer.Types can't break Swate.Components.Page.FileExplorer.Types.
- Position
- Below the diagonal: Renderer.Components.LeftSidebar.FileExplorer.Types uses a module listed above it, which is the healthy direction.
23→14 Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Components.Shared.ARCtrlHelper✕
- Connections
- 2 pairs of types, where a type in Renderer.Components.LeftSidebar.FileExplorer.Types uses a type in Swate.Components.Shared.ARCtrlHelper.
- The types involved
Renderer.Components.LeftSidebar.FileExplorer.Types.ArcCreateDraft→Swate.Components.Shared.ARCtrlHelper.ArcFilesRenderer.Components.LeftSidebar.FileExplorer.Types.ArcCreateKindConfig→Swate.Components.Shared.ARCtrlHelper.ArcFilesDiscriminate
- Direction
- Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Components.Shared.ARCtrlHelper, so a change to Swate.Components.Shared.ARCtrlHelper can break Renderer.Components.LeftSidebar.FileExplorer.Types, while a change to Renderer.Components.LeftSidebar.FileExplorer.Types can't break Swate.Components.Shared.ARCtrlHelper.
- Position
- Below the diagonal: Renderer.Components.LeftSidebar.FileExplorer.Types uses a module listed above it, which is the healthy direction.
23→19 Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Electron.Shared.FileIOTypes✕
- Connections
- 1 pair of types, where a type in Renderer.Components.LeftSidebar.FileExplorer.Types uses a type in Swate.Electron.Shared.FileIOTypes.
- The types involved
Renderer.Components.LeftSidebar.FileExplorer.Types.FileSystemCreateDraft→Swate.Electron.Shared.FileIOTypes.FileSystemItemKind
- Direction
- Renderer.Components.LeftSidebar.FileExplorer.Types uses Swate.Electron.Shared.FileIOTypes, so a change to Swate.Electron.Shared.FileIOTypes can break Renderer.Components.LeftSidebar.FileExplorer.Types, while a change to Renderer.Components.LeftSidebar.FileExplorer.Types can't break Swate.Electron.Shared.FileIOTypes.
- Position
- Below the diagonal: Renderer.Components.LeftSidebar.FileExplorer.Types uses a module listed above it, which is the healthy direction.
24→13 Renderer.Context.FileTreeStore uses Swate.Components.Shared✕
- Connections
- 2 pairs of types, where a type in Renderer.Context.FileTreeStore uses a type in Swate.Components.Shared.
- The types involved
Renderer.Context.FileTreeStore.FileTreeSnapshot→Swate.Components.Shared.PathKeyRenderer.Context.FileTreeStore.FileTreeStore→Swate.Components.Shared.PathKey
- Direction
- Renderer.Context.FileTreeStore uses Swate.Components.Shared, so a change to Swate.Components.Shared can break Renderer.Context.FileTreeStore, while a change to Renderer.Context.FileTreeStore can't break Swate.Components.Shared.
- Position
- Below the diagonal: Renderer.Context.FileTreeStore uses a module listed above it, which is the healthy direction.
24→19 Renderer.Context.FileTreeStore uses Swate.Electron.Shared.FileIOTypes✕
- Connections
- 3 pairs of types, where a type in Renderer.Context.FileTreeStore uses a type in Swate.Electron.Shared.FileIOTypes.
- The types involved
Renderer.Context.FileTreeStore.FileTreeSnapshot→Swate.Electron.Shared.FileIOTypes.FileEntryRenderer.Context.FileTreeStore.FileTreeStore→Swate.Electron.Shared.FileIOTypes.FileEntryRenderer.Context.FileTreeStore.KnownState→Swate.Electron.Shared.FileIOTypes.FileEntry
- Direction
- Renderer.Context.FileTreeStore uses Swate.Electron.Shared.FileIOTypes, so a change to Swate.Electron.Shared.FileIOTypes can break Renderer.Context.FileTreeStore, while a change to Renderer.Context.FileTreeStore can't break Swate.Electron.Shared.FileIOTypes.
- Position
- Below the diagonal: Renderer.Context.FileTreeStore uses a module listed above it, which is the healthy direction.
25→1 Swate.Components.Composite.AnnotationTable uses ARCtrl✕
- Connections
- 3 pairs of types, where a type in Swate.Components.Composite.AnnotationTable uses a type in ARCtrl.
- The types involved
Swate.Components.Composite.AnnotationTable.EditColumnModal→ARCtrl.CompositeHeaderDiscriminateSwate.Components.Composite.AnnotationTable.State→ARCtrl.CompositeHeaderDiscriminateSwate.Components.Composite.AnnotationTable.TransformConfig→ARCtrl.CompositeCellDiscriminate
- Direction
- Swate.Components.Composite.AnnotationTable uses ARCtrl, so a change to ARCtrl can break Swate.Components.Composite.AnnotationTable, while a change to Swate.Components.Composite.AnnotationTable can't break ARCtrl.
- Position
- Below the diagonal: Swate.Components.Composite.AnnotationTable uses a module listed above it, which is the healthy direction.
25→10 Swate.Components.Composite.AnnotationTable uses Swate.Components.Composite.TermSearch.Types✕
- Connections
- 1 pair of types, where a type in Swate.Components.Composite.AnnotationTable uses a type in Swate.Components.Composite.TermSearch.Types.
- The types involved
Swate.Components.Composite.AnnotationTable.InputField→Swate.Components.Composite.TermSearch.Types.Term
- Direction
- Swate.Components.Composite.AnnotationTable uses Swate.Components.Composite.TermSearch.Types, so a change to Swate.Components.Composite.TermSearch.Types can break Swate.Components.Composite.AnnotationTable, while a change to Swate.Components.Composite.AnnotationTable can't break Swate.Components.Composite.TermSearch.Types.
- Position
- Below the diagonal: Swate.Components.Composite.AnnotationTable uses a module listed above it, which is the healthy direction.
26→11 Swate.Components.Page.ArcFileEditor.Types uses Swate.Components.Composite.Widgets.Types✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ArcFileEditor.Types uses a type in Swate.Components.Composite.Widgets.Types.
- The types involved
Swate.Components.Page.ArcFileEditor.Types.ActiveView→Swate.Components.Composite.Widgets.Types.WidgetHostView
- Direction
- Swate.Components.Page.ArcFileEditor.Types uses Swate.Components.Composite.Widgets.Types, so a change to Swate.Components.Composite.Widgets.Types can break Swate.Components.Page.ArcFileEditor.Types, while a change to Swate.Components.Page.ArcFileEditor.Types can't break Swate.Components.Composite.Widgets.Types.
- Position
- Below the diagonal: Swate.Components.Page.ArcFileEditor.Types uses a module listed above it, which is the healthy direction.
26→14 Swate.Components.Page.ArcFileEditor.Types uses Swate.Components.Shared.ARCtrlHelper✕
- Connections
- 2 pairs of types, where a type in Swate.Components.Page.ArcFileEditor.Types uses a type in Swate.Components.Shared.ARCtrlHelper.
- The types involved
Swate.Components.Page.ArcFileEditor.Types.ActiveView→Swate.Components.Shared.ARCtrlHelper.ArcFilesSwate.Components.Page.ArcFileEditor.Types.ArcFileEditorHeaderProps→Swate.Components.Shared.ARCtrlHelper.ArcFiles
- Direction
- Swate.Components.Page.ArcFileEditor.Types uses Swate.Components.Shared.ARCtrlHelper, so a change to Swate.Components.Shared.ARCtrlHelper can break Swate.Components.Page.ArcFileEditor.Types, while a change to Swate.Components.Page.ArcFileEditor.Types can't break Swate.Components.Shared.ARCtrlHelper.
- Position
- Below the diagonal: Swate.Components.Page.ArcFileEditor.Types uses a module listed above it, which is the healthy direction.
27→14 Swate.Components.Page.Landing uses Swate.Components.Shared.ARCtrlHelper✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.Landing uses a type in Swate.Components.Shared.ARCtrlHelper.
- The types involved
Swate.Components.Page.Landing.SubmitPayload→Swate.Components.Shared.ARCtrlHelper.ArcFiles
- Direction
- Swate.Components.Page.Landing uses Swate.Components.Shared.ARCtrlHelper, so a change to Swate.Components.Shared.ARCtrlHelper can break Swate.Components.Page.Landing, while a change to Swate.Components.Page.Landing can't break Swate.Components.Shared.ARCtrlHelper.
- Position
- Below the diagonal: Swate.Components.Page.Landing uses a module listed above it, which is the healthy direction.
28→8 Swate.Components.Page.ProvenanceGraph.Types uses Swate.Components.Composite.GraphCanvas.Types✕
- Connections
- 6 pairs of types, where a type in Swate.Components.Page.ProvenanceGraph.Types uses a type in Swate.Components.Composite.GraphCanvas.Types.
- The types involved
Swate.Components.Page.ProvenanceGraph.Types.CanvasGraph→Swate.Components.Composite.GraphCanvas.Types.CanvasEdgeSwate.Components.Page.ProvenanceGraph.Types.CanvasGraph→Swate.Components.Composite.GraphCanvas.Types.CanvasNodeSwate.Components.Page.ProvenanceGraph.Types.LegendSwatch→Swate.Components.Composite.GraphCanvas.Types.CanvasColorSwate.Components.Page.ProvenanceGraph.Types.LegendSwatch→Swate.Components.Composite.GraphCanvas.Types.PillCategorySwate.Components.Page.ProvenanceGraph.Types.LineageCanvas→Swate.Components.Composite.GraphCanvas.Types.CanvasEdgeSwate.Components.Page.ProvenanceGraph.Types.LineageCanvas→Swate.Components.Composite.GraphCanvas.Types.CanvasNode
- Direction
- Swate.Components.Page.ProvenanceGraph.Types uses Swate.Components.Composite.GraphCanvas.Types, so a change to Swate.Components.Composite.GraphCanvas.Types can break Swate.Components.Page.ProvenanceGraph.Types, while a change to Swate.Components.Page.ProvenanceGraph.Types can't break Swate.Components.Composite.GraphCanvas.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGraph.Types uses a module listed above it, which is the healthy direction.
28→16 Swate.Components.Page.ProvenanceGraph.Types uses Swate.Components.Shared.ProvenanceGraph.Types✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGraph.Types uses a type in Swate.Components.Shared.ProvenanceGraph.Types.
- The types involved
Swate.Components.Page.ProvenanceGraph.Types.LimitedLineage→Swate.Components.Shared.ProvenanceGraph.Types.LineageGraph
- Direction
- Swate.Components.Page.ProvenanceGraph.Types uses Swate.Components.Shared.ProvenanceGraph.Types, so a change to Swate.Components.Shared.ProvenanceGraph.Types can break Swate.Components.Page.ProvenanceGraph.Types, while a change to Swate.Components.Page.ProvenanceGraph.Types can't break Swate.Components.Shared.ProvenanceGraph.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGraph.Types uses a module listed above it, which is the healthy direction.
29→17 Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 10 pairs of types, where a type in Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ArcEndpointLocation→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceIOHeaderSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ArcProvenanceConversionResult→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ArcWritebackLocation→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.CandidatePropertyValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.CandidatePropertyValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyOriginSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.CandidatePropertyValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.CandidatePropertyValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ConvertState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceConnectionSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ConvertState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyValueSwate.Components.Shared.ProvenanceGrouping.ARCtrlConverter.ConvertState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSet
- Direction
- Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter, while a change to Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Shared.ProvenanceGrouping.ARCtrlConverter uses a module listed above it, which is the healthy direction.
30→17 Swate.Components.Shared.ProvenanceGrouping.Edit uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 22 pairs of types, where a type in Swate.Components.Shared.ProvenanceGrouping.Edit uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedPropertyValueCommand→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedPropertyValueCommand→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedPropertyValueCommand→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedSetCommand→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceIOHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedSetCommand→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceConnectionSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyOriginSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSetSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.Edit.Edit→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceWritebackAnchorSwate.Components.Shared.ProvenanceGrouping.Edit.EditError→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceIOHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatch→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceWritebackAnchorSwate.Components.Shared.ProvenanceGrouping.Edit.ResolvedPropertyTarget→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSet
- Direction
- Swate.Components.Shared.ProvenanceGrouping.Edit uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Shared.ProvenanceGrouping.Edit, while a change to Swate.Components.Shared.ProvenanceGrouping.Edit can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Shared.ProvenanceGrouping.Edit uses a module listed above it, which is the healthy direction.
31→17 Swate.Components.Shared.ProvenanceGrouping.Grouping uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 13 pairs of types, where a type in Swate.Components.Shared.ProvenanceGrouping.Grouping uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroup→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroupingValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroupingValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroupingValue→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyValueSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSetSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Shared.ProvenanceGrouping.Grouping.Grouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Shared.ProvenanceGrouping.Grouping.GroupingAssignment→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKey
- Direction
- Swate.Components.Shared.ProvenanceGrouping.Grouping uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Shared.ProvenanceGrouping.Grouping, while a change to Swate.Components.Shared.ProvenanceGrouping.Grouping can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Shared.ProvenanceGrouping.Grouping uses a module listed above it, which is the healthy direction.
32→14 Renderer.Types uses Swate.Components.Shared.ARCtrlHelper✕
- Connections
- 1 pair of types, where a type in Renderer.Types uses a type in Swate.Components.Shared.ARCtrlHelper.
- The types involved
Renderer.Types.PageState→Swate.Components.Shared.ARCtrlHelper.ArcFiles
- Direction
- Renderer.Types uses Swate.Components.Shared.ARCtrlHelper, so a change to Swate.Components.Shared.ARCtrlHelper can break Renderer.Types, while a change to Renderer.Types can't break Swate.Components.Shared.ARCtrlHelper.
- Position
- Below the diagonal: Renderer.Types uses a module listed above it, which is the healthy direction.
32→19 Renderer.Types uses Swate.Electron.Shared.FileIOTypes✕
- Connections
- 1 pair of types, where a type in Renderer.Types uses a type in Swate.Electron.Shared.FileIOTypes.
- The types involved
Renderer.Types.PageState→Swate.Electron.Shared.FileIOTypes.NoPreviewReason
- Direction
- Renderer.Types uses Swate.Electron.Shared.FileIOTypes, so a change to Swate.Electron.Shared.FileIOTypes can break Renderer.Types, while a change to Renderer.Types can't break Swate.Electron.Shared.FileIOTypes.
- Position
- Below the diagonal: Renderer.Types uses a module listed above it, which is the healthy direction.
32→21 Renderer.Types uses Swate.Electron.Shared.VersionControlTypes✕
- Connections
- 12 pairs of types, where a type in Renderer.Types uses a type in Swate.Electron.Shared.VersionControlTypes.
- The types involved
Renderer.Types.GitDiffBlockReason→Swate.Electron.Shared.VersionControlTypes.MemoryCauseDtoRenderer.Types.GitDiffLinePosition→Swate.Electron.Shared.VersionControlTypes.DiffSideDtoRenderer.Types.GitDiffPageData→Swate.Electron.Shared.VersionControlTypes.DiffHandleDtoRenderer.Types.GitDiffPageData→Swate.Electron.Shared.VersionControlTypes.DiffSourceInfoPairDtoRenderer.Types.GitDiffPageData→Swate.Electron.Shared.VersionControlTypes.DiffStorageDtoRenderer.Types.GitDiffPageData→Swate.Electron.Shared.VersionControlTypes.PendingPreviewDtoRenderer.Types.GitDiffPageData→Swate.Electron.Shared.VersionControlTypes.ScanProgressDtoRenderer.Types.GitDiffPageStatus→Swate.Electron.Shared.VersionControlTypes.DiffSideDtoRenderer.Types.GitDiffPageStatus→Swate.Electron.Shared.VersionControlTypes.EncodingCandidateDtoRenderer.Types.GitDiffPageStatus→Swate.Electron.Shared.VersionControlTypes.PreparationTokenDtoRenderer.Types.VersionControlConflictPage→Swate.Electron.Shared.VersionControlTypes.ConflictSessionHandleDtoRenderer.Types.VersionControlFileChoicePage→Swate.Electron.Shared.VersionControlTypes.ConflictSessionHandleDto
- Direction
- Renderer.Types uses Swate.Electron.Shared.VersionControlTypes, so a change to Swate.Electron.Shared.VersionControlTypes can break Renderer.Types, while a change to Renderer.Types can't break Swate.Electron.Shared.VersionControlTypes.
- Position
- Below the diagonal: Renderer.Types uses a module listed above it, which is the healthy direction.
32→26 Renderer.Types uses Swate.Components.Page.ArcFileEditor.Types✕
- Connections
- 1 pair of types, where a type in Renderer.Types uses a type in Swate.Components.Page.ArcFileEditor.Types.
- The types involved
Renderer.Types.PageState→Swate.Components.Page.ArcFileEditor.Types.ActiveView
- Direction
- Renderer.Types uses Swate.Components.Page.ArcFileEditor.Types, so a change to Swate.Components.Page.ArcFileEditor.Types can break Renderer.Types, while a change to Renderer.Types can't break Swate.Components.Page.ArcFileEditor.Types.
- Position
- Below the diagonal: Renderer.Types uses a module listed above it, which is the healthy direction.
33→10 Spreadsheet uses Swate.Components.Composite.TermSearch.Types✕
- Connections
- 1 pair of types, where a type in Spreadsheet uses a type in Swate.Components.Composite.TermSearch.Types.
- The types involved
Spreadsheet.Msg→Swate.Components.Composite.TermSearch.Types.Term
- Direction
- Spreadsheet uses Swate.Components.Composite.TermSearch.Types, so a change to Swate.Components.Composite.TermSearch.Types can break Spreadsheet, while a change to Spreadsheet can't break Swate.Components.Composite.TermSearch.Types.
- Position
- Below the diagonal: Spreadsheet uses a module listed above it, which is the healthy direction.
33→14 Spreadsheet uses Swate.Components.Shared.ARCtrlHelper✕
- Connections
- 3 pairs of types, where a type in Spreadsheet uses a type in Swate.Components.Shared.ARCtrlHelper.
- The types involved
Spreadsheet.Model→Swate.Components.Shared.ARCtrlHelper.ArcFilesSpreadsheet.Msg→Swate.Components.Shared.ARCtrlHelper.ArcFilesSpreadsheet.Msg→Swate.Components.Shared.ARCtrlHelper.JsonExportFormat
- Direction
- Spreadsheet uses Swate.Components.Shared.ARCtrlHelper, so a change to Swate.Components.Shared.ARCtrlHelper can break Spreadsheet, while a change to Spreadsheet can't break Swate.Components.Shared.ARCtrlHelper.
- Position
- Below the diagonal: Spreadsheet uses a module listed above it, which is the healthy direction.
33→22 Spreadsheet uses Types.FileImport✕
- Connections
- 1 pair of types, where a type in Spreadsheet uses a type in Types.FileImport.
- The types involved
Spreadsheet.Msg→Types.FileImport.SelectiveImportConfig
- Direction
- Spreadsheet uses Types.FileImport, so a change to Types.FileImport can break Spreadsheet, while a change to Spreadsheet can't break Types.FileImport.
- Position
- Below the diagonal: Spreadsheet uses a module listed above it, which is the healthy direction.
33→26 Spreadsheet uses Swate.Components.Page.ArcFileEditor.Types✕
- Connections
- 2 pairs of types, where a type in Spreadsheet uses a type in Swate.Components.Page.ArcFileEditor.Types.
- The types involved
Spreadsheet.Model→Swate.Components.Page.ArcFileEditor.Types.ActiveViewSpreadsheet.Msg→Swate.Components.Page.ArcFileEditor.Types.ActiveView
- Direction
- Spreadsheet uses Swate.Components.Page.ArcFileEditor.Types, so a change to Swate.Components.Page.ArcFileEditor.Types can break Spreadsheet, while a change to Spreadsheet can't break Swate.Components.Page.ArcFileEditor.Types.
- Position
- Below the diagonal: Spreadsheet uses a module listed above it, which is the healthy direction.
34→17 Swate.Components.Shared.ProvenanceGrouping.Session uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 2 pairs of types, where a type in Swate.Components.Shared.ProvenanceGrouping.Session uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceLayer→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSetReference→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSide
- Direction
- Swate.Components.Shared.ProvenanceGrouping.Session uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Shared.ProvenanceGrouping.Session, while a change to Swate.Components.Shared.ProvenanceGrouping.Session can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Shared.ProvenanceGrouping.Session uses a module listed above it, which is the healthy direction.
34→30 Swate.Components.Shared.ProvenanceGrouping.Session uses Swate.Components.Shared.ProvenanceGrouping.Edit✕
- Connections
- 2 pairs of types, where a type in Swate.Components.Shared.ProvenanceGrouping.Session uses a type in Swate.Components.Shared.ProvenanceGrouping.Edit.
- The types involved
Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSession→Swate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatchSwate.Components.Shared.ProvenanceGrouping.Session.SessionError→Swate.Components.Shared.ProvenanceGrouping.Edit.EditError
- Direction
- Swate.Components.Shared.ProvenanceGrouping.Session uses Swate.Components.Shared.ProvenanceGrouping.Edit, so a change to Swate.Components.Shared.ProvenanceGrouping.Edit can break Swate.Components.Shared.ProvenanceGrouping.Session, while a change to Swate.Components.Shared.ProvenanceGrouping.Session can't break Swate.Components.Shared.ProvenanceGrouping.Edit.
- Position
- Below the diagonal: Swate.Components.Shared.ProvenanceGrouping.Session uses a module listed above it, which is the healthy direction.
35→2 Model uses InteropLogging✕
- Connections
- 1 pair of types, where a type in Model uses a type in InteropLogging.
- The types involved
Model.LogItem→InteropLogging.Msg
- Direction
- Model uses InteropLogging, so a change to InteropLogging can break Model, while a change to Model can't break InteropLogging.
- Position
- Below the diagonal: Model uses a module listed above it, which is the healthy direction.
35→4 Model uses Routing✕
- Connections
- 2 pairs of types, where a type in Model uses a type in Routing.
- The types involved
Model.PageState→Routing.MainPageModel.PageState→Routing.SidebarPage
- Direction
- Model uses Routing, so a change to Routing can break Model, while a change to Model can't break Routing.
- Position
- Below the diagonal: Model uses a module listed above it, which is the healthy direction.
35→33 Model uses Spreadsheet✕
- Connections
- 1 pair of types, where a type in Model uses a type in Spreadsheet.
- The types involved
Model.Model→Spreadsheet.Model
- Direction
- Model uses Spreadsheet, so a change to Spreadsheet can break Model, while a change to Model can't break Spreadsheet.
- Position
- Below the diagonal: Model uses a module listed above it, which is the healthy direction.
36→6 Renderer.Context.GitWorkflow uses Swate.Components.Api.GitLabApi✕
- Connections
- 1 pair of types, where a type in Renderer.Context.GitWorkflow uses a type in Swate.Components.Api.GitLabApi.
- The types involved
Renderer.Context.GitWorkflow.GitWorkflow→Swate.Components.Api.GitLabApi.PublishOwnersDto
- Direction
- Renderer.Context.GitWorkflow uses Swate.Components.Api.GitLabApi, so a change to Swate.Components.Api.GitLabApi can break Renderer.Context.GitWorkflow, while a change to Renderer.Context.GitWorkflow can't break Swate.Components.Api.GitLabApi.
- Position
- Below the diagonal: Renderer.Context.GitWorkflow uses a module listed above it, which is the healthy direction.
36→20 Renderer.Context.GitWorkflow uses Swate.Electron.Shared.IPCTypes✕
- Connections
- 3 pairs of types, where a type in Renderer.Context.GitWorkflow uses a type in Swate.Electron.Shared.IPCTypes.
- The types involved
Renderer.Context.GitWorkflow.GitState→Swate.Electron.Shared.IPCTypes.UserDefaultValuesDtoRenderer.Context.GitWorkflow.GitWorkflow→Swate.Electron.Shared.IPCTypes.UserDefaultValuesDtoRenderer.Context.GitWorkflow.Msg→Swate.Electron.Shared.IPCTypes.UserDefaultValuesDto
- Direction
- Renderer.Context.GitWorkflow uses Swate.Electron.Shared.IPCTypes, so a change to Swate.Electron.Shared.IPCTypes can break Renderer.Context.GitWorkflow, while a change to Renderer.Context.GitWorkflow can't break Swate.Electron.Shared.IPCTypes.
- Position
- Below the diagonal: Renderer.Context.GitWorkflow uses a module listed above it, which is the healthy direction.
36→21 Renderer.Context.GitWorkflow uses Swate.Electron.Shared.VersionControlTypes✕
- Connections
- 47 pairs of types, where a type in Renderer.Context.GitWorkflow uses a type in Swate.Electron.Shared.VersionControlTypes. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Renderer.Context.GitWorkflow.ConfirmMergeResolutionOutcome→Swate.Electron.Shared.VersionControlTypes.WorkspaceStatusDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.DiffPageDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.DiffSideDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ExpandTextDiffRequestDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.OpenTextDiffRequestDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.OperationResultDto`1Renderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ReadTextDiffLineRequestDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ReadTextDiffPageRequestDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ReplayTextDiffPageRequestDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ResumableLineDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ResumableOpenDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ResumablePageDtoRenderer.Context.GitWorkflow.GitDiffMsg→Swate.Electron.Shared.VersionControlTypes.ResumablePartsDtoRenderer.Context.GitWorkflow.GitMergeResolutionRequest→Swate.Electron.Shared.VersionControlTypes.ConflictResolutionDtoRenderer.Context.GitWorkflow.GitMergeResolutionRequest→Swate.Electron.Shared.VersionControlTypes.ConflictSessionHandleDtoRenderer.Context.GitWorkflow.GitRefreshResult→Swate.Electron.Shared.VersionControlTypes.LogicalRefDtoRenderer.Context.GitWorkflow.GitRefreshResult→Swate.Electron.Shared.VersionControlTypes.OperationFailureDtoRenderer.Context.GitWorkflow.GitRefreshResult→Swate.Electron.Shared.VersionControlTypes.StoragePolicySettingsDtoRenderer.Context.GitWorkflow.GitRefreshResult→Swate.Electron.Shared.VersionControlTypes.WorkspaceSessionInfoDtoRenderer.Context.GitWorkflow.GitRefreshResult→Swate.Electron.Shared.VersionControlTypes.WorkspaceStatusDtoRenderer.Context.GitWorkflow.GitState→Swate.Electron.Shared.VersionControlTypes.ConflictSessionSummaryDtoRenderer.Context.GitWorkflow.GitState→Swate.Electron.Shared.VersionControlTypes.LogicalRefDtoRenderer.Context.GitWorkflow.GitState→Swate.Electron.Shared.VersionControlTypes.OperationRequestDtoRenderer.Context.GitWorkflow.GitState→Swate.Electron.Shared.VersionControlTypes.ServiceAvailabilityDtoRenderer.Context.GitWorkflow.GitWorkflow→Swate.Electron.Shared.VersionControlTypes.CloneWorkspaceRequestDto
- Direction
- Renderer.Context.GitWorkflow uses Swate.Electron.Shared.VersionControlTypes, so a change to Swate.Electron.Shared.VersionControlTypes can break Renderer.Context.GitWorkflow, while a change to Renderer.Context.GitWorkflow can't break Swate.Electron.Shared.VersionControlTypes.
- Position
- Below the diagonal: Renderer.Context.GitWorkflow uses a module listed above it, which is the healthy direction.
36→32 Renderer.Context.GitWorkflow uses Renderer.Types✕
- Connections
- 7 pairs of types, where a type in Renderer.Context.GitWorkflow uses a type in Renderer.Types.
- The types involved
Renderer.Context.GitWorkflow.GitDiffMsg→Renderer.Types.PageStateRenderer.Context.GitWorkflow.GitDiffReopen→Renderer.Types.GitDiffLinePositionRenderer.Context.GitWorkflow.GitPageChange→Renderer.Types.PageStateRenderer.Context.GitWorkflow.GitState→Renderer.Types.GitDiffPageDataRenderer.Context.GitWorkflow.GitWorkflow→Renderer.Types.FileChoiceVersionRenderer.Context.GitWorkflow.GitWorkflow→Renderer.Types.PageStateRenderer.Context.GitWorkflow.GitWorkflow→Renderer.Types.VersionControlFileChoicePage
- Direction
- Renderer.Context.GitWorkflow uses Renderer.Types, so a change to Renderer.Types can break Renderer.Context.GitWorkflow, while a change to Renderer.Context.GitWorkflow can't break Renderer.Types.
- Position
- Below the diagonal: Renderer.Context.GitWorkflow uses a module listed above it, which is the healthy direction.
37→17 Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 14 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping.Types uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Page.ProvenanceGrouping.Types.ConnectionHandleRef→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.Types.PropertyStats→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.Types.ProvenanceDetail→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.Types.UiState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.Types.UiState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyValueSwate.Components.Page.ProvenanceGrouping.Types.UiState→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentError→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentSource→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentSource→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentSource→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentWarning→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentWarning→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceTermSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentWarning→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceValueSwate.Components.Page.ProvenanceGrouping.Types.VisiblePropertyColorKey→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKey
- Direction
- Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Page.ProvenanceGrouping.Types, while a change to Swate.Components.Page.ProvenanceGrouping.Types can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.Types uses a module listed above it, which is the healthy direction.
37→30 Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Edit✕
- Connections
- 4 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping.Types uses a type in Swate.Components.Shared.ProvenanceGrouping.Edit.
- The types involved
Swate.Components.Page.ProvenanceGrouping.Types.PropertyAssignmentBatch→Swate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedPropertyValueCommandSwate.Components.Page.ProvenanceGrouping.Types.ProvenanceEditorChange→Swate.Components.Shared.ProvenanceGrouping.Edit.ProvenanceTablePatchSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentPlan→Swate.Components.Shared.ProvenanceGrouping.Edit.CreateLoadedPropertyValueCommandSwate.Components.Page.ProvenanceGrouping.Types.ValueAssignmentWarning→Swate.Components.Shared.ProvenanceGrouping.Edit.ProvenancePropertyTarget
- Direction
- Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Edit, so a change to Swate.Components.Shared.ProvenanceGrouping.Edit can break Swate.Components.Page.ProvenanceGrouping.Types, while a change to Swate.Components.Page.ProvenanceGrouping.Types can't break Swate.Components.Shared.ProvenanceGrouping.Edit.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.Types uses a module listed above it, which is the healthy direction.
37→31 Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Grouping✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.Types uses a type in Swate.Components.Shared.ProvenanceGrouping.Grouping.
- The types involved
Swate.Components.Page.ProvenanceGrouping.Types.SideViewState→Swate.Components.Shared.ProvenanceGrouping.Grouping.GroupingAssignment
- Direction
- Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Grouping, so a change to Swate.Components.Shared.ProvenanceGrouping.Grouping can break Swate.Components.Page.ProvenanceGrouping.Types, while a change to Swate.Components.Page.ProvenanceGrouping.Types can't break Swate.Components.Shared.ProvenanceGrouping.Grouping.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.Types uses a module listed above it, which is the healthy direction.
37→34 Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Session✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.Types uses a type in Swate.Components.Shared.ProvenanceGrouping.Session.
- The types involved
Swate.Components.Page.ProvenanceGrouping.Types.ProvenanceEditorChange→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSession
- Direction
- Swate.Components.Page.ProvenanceGrouping.Types uses Swate.Components.Shared.ProvenanceGrouping.Session, so a change to Swate.Components.Shared.ProvenanceGrouping.Session can break Swate.Components.Page.ProvenanceGrouping.Types, while a change to Swate.Components.Page.ProvenanceGrouping.Types can't break Swate.Components.Shared.ProvenanceGrouping.Session.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.Types uses a module listed above it, which is the healthy direction.
38→2 MessagesModule uses InteropLogging✕
- Connections
- 1 pair of types, where a type in MessagesModule uses a type in InteropLogging.
- The types involved
MessagesModule.DevMsg→InteropLogging.Msg
- Direction
- MessagesModule uses InteropLogging, so a change to InteropLogging can break MessagesModule, while a change to MessagesModule can't break InteropLogging.
- Position
- Below the diagonal: MessagesModule uses a module listed above it, which is the healthy direction.
38→33 MessagesModule uses Spreadsheet✕
- Connections
- 1 pair of types, where a type in MessagesModule uses a type in Spreadsheet.
- The types involved
MessagesModule.Msg→Spreadsheet.Msg
- Direction
- MessagesModule uses Spreadsheet, so a change to Spreadsheet can break MessagesModule, while a change to MessagesModule can't break Spreadsheet.
- Position
- Below the diagonal: MessagesModule uses a module listed above it, which is the healthy direction.
38→35 MessagesModule uses Model✕
- Connections
- 1 pair of types, where a type in MessagesModule uses a type in Model.
- The types involved
MessagesModule.DevMsg→Model.LogItem
- Direction
- MessagesModule uses Model, so a change to Model can break MessagesModule, while a change to MessagesModule can't break Model.
- Position
- Below the diagonal: MessagesModule uses a module listed above it, which is the healthy direction.
39→17 Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 16 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Page.ProvenanceGrouping.ConnectorOverlay→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Page.ProvenanceGrouping.ConnectorOverlay→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceKindSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyHeaderSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyOriginSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyValueSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSourceRefSwate.Components.Page.ProvenanceGrouping.GroupCard→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Page.ProvenanceGrouping.GroupCard→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.PropertyShelfItemPayload→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyKeySwate.Components.Page.ProvenanceGrouping.PropertyShelfItemPayload→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.ProvenanceGrouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceModelSwate.Components.Page.ProvenanceGrouping.ProvenanceGrouping→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSideSwate.Components.Page.ProvenanceGrouping.ProvenanceTutorialCheckpoint→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSide
- Direction
- Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Page.ProvenanceGrouping, while a change to Swate.Components.Page.ProvenanceGrouping can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping uses a module listed above it, which is the healthy direction.
39→31 Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Grouping✕
- Connections
- 6 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping uses a type in Swate.Components.Shared.ProvenanceGrouping.Grouping.
- The types involved
Swate.Components.Page.ProvenanceGrouping.ConnectorOverlay→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayConnectionSwate.Components.Page.ProvenanceGrouping.ConnectorOverlay→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroupSwate.Components.Page.ProvenanceGrouping.ConnectorSpec→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayConnectionSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Grouping.GroupingAssignmentSwate.Components.Page.ProvenanceGrouping.GroupCard→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroupSwate.Components.Page.ProvenanceGrouping.MeasuredConnector→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayConnection
- Direction
- Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Grouping, so a change to Swate.Components.Shared.ProvenanceGrouping.Grouping can break Swate.Components.Page.ProvenanceGrouping, while a change to Swate.Components.Page.ProvenanceGrouping can't break Swate.Components.Shared.ProvenanceGrouping.Grouping.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping uses a module listed above it, which is the healthy direction.
39→34 Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Session✕
- Connections
- 5 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping uses a type in Swate.Components.Shared.ProvenanceGrouping.Session.
- The types involved
Swate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Session.PropertyValueSourceInfoSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSessionSwate.Components.Page.ProvenanceGrouping.DragContext→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceLayerSwate.Components.Page.ProvenanceGrouping.DragContext→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSessionSwate.Components.Page.ProvenanceGrouping.ProvenanceGrouping→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceSession
- Direction
- Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Shared.ProvenanceGrouping.Session, so a change to Swate.Components.Shared.ProvenanceGrouping.Session can break Swate.Components.Page.ProvenanceGrouping, while a change to Swate.Components.Page.ProvenanceGrouping can't break Swate.Components.Shared.ProvenanceGrouping.Session.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping uses a module listed above it, which is the healthy direction.
39→37 Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Page.ProvenanceGrouping.Types✕
- Connections
- 7 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping uses a type in Swate.Components.Page.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Page.ProvenanceGrouping.ConnectorSpec→Swate.Components.Page.ProvenanceGrouping.Types.ConnectionHandleRefSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Page.ProvenanceGrouping.Types.ConnectionHandleRefSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Page.ProvenanceGrouping.Types.FilterStateSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Page.ProvenanceGrouping.Types.PropertyCountBadgeSwate.Components.Page.ProvenanceGrouping.Controls→Swate.Components.Page.ProvenanceGrouping.Types.PropertyStatsSwate.Components.Page.ProvenanceGrouping.DragContext→Swate.Components.Page.ProvenanceGrouping.Types.UiStateSwate.Components.Page.ProvenanceGrouping.MeasuredConnector→Swate.Components.Page.ProvenanceGrouping.Types.ConnectionPoint
- Direction
- Swate.Components.Page.ProvenanceGrouping uses Swate.Components.Page.ProvenanceGrouping.Types, so a change to Swate.Components.Page.ProvenanceGrouping.Types can break Swate.Components.Page.ProvenanceGrouping, while a change to Swate.Components.Page.ProvenanceGrouping can't break Swate.Components.Page.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping uses a module listed above it, which is the healthy direction.
40→17 Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Types✕
- Connections
- 2 pairs of types, where a type in Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a type in Swate.Components.Shared.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenancePropertyValueSwate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Shared.ProvenanceGrouping.Types.ProvenanceSide
- Direction
- Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Types, so a change to Swate.Components.Shared.ProvenanceGrouping.Types can break Swate.Components.Page.ProvenanceGrouping.DragHandlers, while a change to Swate.Components.Page.ProvenanceGrouping.DragHandlers can't break Swate.Components.Shared.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a module listed above it, which is the healthy direction.
40→31 Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Grouping✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a type in Swate.Components.Shared.ProvenanceGrouping.Grouping.
- The types involved
Swate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Shared.ProvenanceGrouping.Grouping.DisplayGroup
- Direction
- Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Grouping, so a change to Swate.Components.Shared.ProvenanceGrouping.Grouping can break Swate.Components.Page.ProvenanceGrouping.DragHandlers, while a change to Swate.Components.Page.ProvenanceGrouping.DragHandlers can't break Swate.Components.Shared.ProvenanceGrouping.Grouping.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a module listed above it, which is the healthy direction.
40→34 Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Session✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a type in Swate.Components.Shared.ProvenanceGrouping.Session.
- The types involved
Swate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Shared.ProvenanceGrouping.Session.ProvenanceLayer
- Direction
- Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Shared.ProvenanceGrouping.Session, so a change to Swate.Components.Shared.ProvenanceGrouping.Session can break Swate.Components.Page.ProvenanceGrouping.DragHandlers, while a change to Swate.Components.Page.ProvenanceGrouping.DragHandlers can't break Swate.Components.Shared.ProvenanceGrouping.Session.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a module listed above it, which is the healthy direction.
40→37 Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Page.ProvenanceGrouping.Types✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a type in Swate.Components.Page.ProvenanceGrouping.Types.
- The types involved
Swate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Page.ProvenanceGrouping.Types.ConnectionHandleRef
- Direction
- Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Page.ProvenanceGrouping.Types, so a change to Swate.Components.Page.ProvenanceGrouping.Types can break Swate.Components.Page.ProvenanceGrouping.DragHandlers, while a change to Swate.Components.Page.ProvenanceGrouping.DragHandlers can't break Swate.Components.Page.ProvenanceGrouping.Types.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a module listed above it, which is the healthy direction.
40→39 Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Page.ProvenanceGrouping✕
- Connections
- 1 pair of types, where a type in Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a type in Swate.Components.Page.ProvenanceGrouping.
- The types involved
Swate.Components.Page.ProvenanceGrouping.DragHandlers.DragHandlers→Swate.Components.Page.ProvenanceGrouping.DragContext
- Direction
- Swate.Components.Page.ProvenanceGrouping.DragHandlers uses Swate.Components.Page.ProvenanceGrouping, so a change to Swate.Components.Page.ProvenanceGrouping can break Swate.Components.Page.ProvenanceGrouping.DragHandlers, while a change to Swate.Components.Page.ProvenanceGrouping.DragHandlers can't break Swate.Components.Page.ProvenanceGrouping.
- Position
- Below the diagonal: Swate.Components.Page.ProvenanceGrouping.DragHandlers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 55 | High / Critical |
| A05:2025 — Injection | 35 | High / Critical |
| A07:2025 — Authentication Failures | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
Roadmap
Top priorities: Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED; 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; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. | +13.0 pts | Low | REDACTED Scanning |
| 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. | +5.1 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +5.1 pts | Medium | Dependency Hygiene |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.0 pts | Medium | Keyboard semantics |
| Add tests that import the unreached modules (directly or through their public entry). | +2.9 pts | Medium | Test Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.0 pts | Low | ADR Quality |
| Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. | +0.8 pts | Low | Secrets (history) |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +1.5 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.3 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/Electron/src/Main/IPC/IArcVaultsApi.fs | 7.0 | Mixed | God Classes: FileTooLong: IPC/IArcVaultsApi.fs |
| src/Electron/src/Main/VersionControl/Mappings.fs | 7.0 | Mixed | God Classes: FileTooLong: VersionControl/Mappings.fs |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 62 of 62 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 62 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, 354 of 376 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Cyclomatic Complexity couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
- D2 Cognitive Complexity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Cognitive Complexity couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
- D4 Code Duplication — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Code Duplication couldn't be assessed within its 9-minute budget on a solution this large — not included in this run.
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 30 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 139 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Electron/src/Main/ArcVault/ArcVaultFileWatcher.fs, src/Shared/PathHelpers.fs, src/Electron/src/Main/IPC/IArcVaultsApi.fs, src/Electron/src/Swate.Electron.Shared/FileIOHelper.fs, src/Electron/src/Main/ArcVault/ArcVault.fs, … that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), 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.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Build/Dockerfile.publish.dockerignore carries no `FROM` instruction, so it declares no build stage and every Dockerfile rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 2 of 3 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Components/src/Composite/Actionbar/Actionbar.stories.tsx`, `src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx`, `src/Components/src/Composite/AnnotationTable/ResetTableConfirmationModal.stories.tsx`, `src/Components/src/Composite/ArcSelector/ArcSelector.stories.tsx`, `src/Components/src/Composite/ArcVaultActions/ArcVaultActions.stories.tsx`, … (+42 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AC1 Text alternatives — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 72 further occurrence(s) are not listed individually; the score already reflects all 112.
- AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC5 ARIA correctness — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 14 Feliz (F#) template file(s) carrying 91 markup element(s) (e.g. tests/Electron.Renderer/FileStateContextReload.test.fs, tests/Electron.Renderer/FileTreeRenameWorkflow.test.fs, tests/Electron.Renderer/GitDiffPageWorkflow.test.fs) — and the accessibility cards on this run were measured over the 212 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 14 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 212 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:7474: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:7474/ Call log: - navigating to "http://127.0.0.1:7474/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:7687: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:7687/ Call log: - navigating to "http://127.0.0.1:7687/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:6379: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:6379/ Call log: - navigating to "http://127.0.0.1:6379/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:1111: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:1111/ Call log: - navigating to "http://127.0.0.1:1111/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:8000: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:8000/ Call log: - navigating to "http://127.0.0.1:8000/", waiting until "load" .
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
40 god class(es) detected.
What to do
- Resolve the 34 FileTooLong finding(s) in God Classes — start with GitWorkflow.fs, GitPagedDiffViewer.fs, GitSidebar.fs. — One of this dimension's main actionable groups (34 warning-level).
- Resolve the 5 TooManyFunctions finding(s) in God Classes — start with GitWorkflow.fs (2), Session.fs, VersionControlApiClient.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Icons.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
16 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 13 classes have LCOM4 above 3.
D9 · Test Distribution
30 test methods: 30 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 30 `it`/`test` case(s) across 2 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 30 tests. Measured on the JavaScript/TypeScript suite only — at least 139 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D13 · REDACTED Scanning
5 secret(s) detected.
What to do
- Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 89 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 35 direct `PackageReference`(s), and 85 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Electron/src/Renderer/Context/GitWorkflow.fs (100×227=22700); src/Electron/src/Main/IPC/IArcVaultsApi.fs (91×170=15470); src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs (28×166=4648) Repeated repair below the complexity floor: src/Components/src/ClipboardContract/Contract.fs (3 of 5 changes were fixes); src/Components/src/Composite/TemplateBrowser/Helper.fs (3 of 4 changes were fixes)
What to do
- Resolve the 46 Hotspot finding(s) in Churn × Complexity Hotspots — start with ContextMenu.fs (2), GitWorkflow.fs, IArcVaultsApi.fs. — One of this dimension's main actionable groups (46 warning-level).
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Contract.fs, Helper.fs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
114 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Electron/src/Renderer/Context/GitWorkflow.fs. Counted over 370 of the 605 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 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
4 of 10 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
96 % of calls cross a namespace and 3 % go through an interface, but 54 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
35 finding(s): 0 critical, 30 high, 5 medium, 0 low. 29 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 47 file(s) — `src/Components/src/Composite/Actionbar/Actionbar.stories.tsx` (line 40), `src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx` (line 43), `src/Components/src/Composite/AnnotationTable/ResetTableConfirmationModal.stories.tsx` (line 41), `src/Components/src/Composite/ArcSelector/ArcSelector.stories.tsx` (line 11), `src/Components/src/Composite/ArcVaultActions/ArcVaultActions.stories.tsx` (line 17), … (+42 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 29 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (29 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
48 finding(s): 7 critical, 22 high, 16 medium, 3 low.
What to do
- Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20), REDACTED. — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 7 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 5 high, 5 medium, 1 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 370 of the 605 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: main.fs↔preload.fs 70%; REDACTED↔Server.fs 62%; Mappings.fs↔GitWorkflow.fs 60%
What to do
- Resolve the 8 Change coupling finding(s) in Change Coupling — start with REDACTED, Mappings.fs, FileTreeCreator.fs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with main.fs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 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.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — src/Client/Pages/Info/InfoView.fs:44
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×23) — src/Client/Index.fs:70, src/Client/MainComponents/EmptyTableModals.fs:132, src/Client/MainComponents/FooterTabs.fs:94, …
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×8) — src/Client/Modals/SelectiveImportModal.fs:94, src/Client/Pages/Settings/SettingsView.fs:135, src/Client/SharedComponents/Metadata/Forms.fs:197, …
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — src/Client/Modals/SelectiveImportModal.fs:130
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — src/Client/Pages/BuildingBlock/Dropdown.fs:20, src/Client/Pages/BuildingBlock/SearchComponent.fs:129
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — src/Client/Pages/ProtocolTemplates/ProtocolView.fs:264, src/Components/src/Composite/Actionbar/Actionbar.fs:44
- This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — src/Components/playground/App.tsx:43, src/Components/playground/App.tsx:65, src/Components/playground/App.tsx:77
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — src/Components/playground/App.tsx:127
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×3) — src/Client/Pages/FilePicker/FilePickerView.fs:244, src/Components/src/Composite/SortableList/SortableList.fs:218, src/Components/src/Primitive/BaseModal/BaseModal.fs:249
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — src/Client/index.html:2, src/Electron/index.html:2, src/Server/public/test.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — src/Components/src/Page/Changelog/Changelog.fs:292
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — src/Components/src/Page/ProvenanceGrouping/EditorPanels.fs:292
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/Electron/src/Renderer/Components/MainContent/PDFViewer.fs:42
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/Server/public/test.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". (×10) — src/Client/MainComponents/FooterTabs.fs:120, src/Client/MainComponents/FooterTabs.fs:167, src/Client/MainComponents/FooterTabs.fs:196, …
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×9) — src/Client/MainComponents/NoFileElement.fs:67, src/Client/Pages/BuildingBlock/Dropdown.fs:96, src/Client/Pages/BuildingBlock/Dropdown.fs:112, …
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×8) — src/Client/Modals/InteropLoggingModal.fs:44, src/Client/SharedComponents/Logo.fs:11, src/Client/Views/MainPageViews.fs:20, …
- An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — src/Client/Pages/BuildingBlock/Dropdown.fs:49
- This <div> announces itself as a role="tab" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="tab" or point aria-activedescendant at it. — src/Components/src/Composite/TermSearch/TermSearch.fs:676
- This <article> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — src/Components/src/Page/ProvenanceGrouping/GroupCard.fs:417
- This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. — src/Components/src/Primitive/CardGrid/CardGrid.fs:15
- This <ul> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. Give it a role as well, so assistive tech can announce what it is. — src/Components/src/Primitive/Dropdown/Dropdown.fs:44
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.swt\:menu :where(li>details>summary)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.swt\:menu :where(li)>:not(ul,.swt\:menu-title,details,.swt\:btn).swt\:menu-active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.swt\:collapse:is(details) summary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.swt\:outline-hidden` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.swt\:\!outline-0` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.swt\:outline-none` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Components/src/swate-components.css:2
- `.animated-border::before` moves (`animation: border-gradient-flow 8s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×3) — src/Electron/src/Renderer/tailwind.css:254, src/Components/tailwind.css:218, src/Client/tailwind.css:207
- `:is(.swt\:menu :where(li>details>summary),.swt\:menu :where(li>.swt\:menu-dropdown-toggle)):after` moves (`transition-property: rotate,translate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
- `.swt\:toggle>*` moves (`transition: opacity .2s,rotate .4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
- `.swt\:toggle:before` moves (`transition: background-color .1s,translate .2s,inset-inline-start .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
- `.swt\:checkbox:before` moves (`transition: clip-path .3s .1s,opacity .1s .1s,rotate .3s .1s,translate .3s .1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
- `.swt\:modal-box` moves (`transition: translate .3s ease-out,scale .3s ease-out,opacity .2s ease-out 50ms,box-shadow .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
- `.animated-border:before` moves (`animation: 8s ease-in-out infinite border-gradient-flow`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Components/src/swate-components.css:2
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 212 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — REDACTED:15
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
- `Client.Tests` (production) references the test project `Shared.Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — tests/Client/Client.Tests.fsproj:18
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 3 project(s) that lack one — worth up to 1.3 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `build`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability.
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 16255 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `Directory.Packages.props` 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`. — Directory.Packages.props:6
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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- src/Components/playground/App.tsx:90 · src/Components/playground/App.tsx:106 · src/Components/playground/App.tsx:120 · src/Components/playground/App.tsx:141 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Components/playground/App.tsx:90
- src/Components/playground/App.tsx:112 · src/Components/playground/App.tsx:126 · src/Components/playground/App.tsx:147 · src/Components/playground/App.tsx:184 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Components/playground/App.tsx:112
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- src/Electron/scripts/forge-make.cjs:8 imports @electron-forge/cli/dist/electron-forge-make.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/Electron/scripts/forge-make.cjs:8
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
- src/Components/src/Page/GitComparison/GitPagedDiffViewer.stories.tsx has 2896 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Page/GitComparison/GitPagedDiffViewer.stories.tsx:1
- REDACTED has 2449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- src/Components/src/Page/GitSidebar/GitSidebar.stories.tsx has 954 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Page/GitSidebar/GitSidebar.stories.tsx:1
- src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx has 945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx:1
- src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx has 800 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx:1
- src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx:1
- src/Components/src/Page/GitComparison/GitMergeConflictViewer.stories.tsx has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Components/src/Page/GitComparison/GitMergeConflictViewer.stories.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — src/Components/playground/App.tsx:1, src/Electron/scripts/forge-make.cjs:1, src/Components/playground/main.tsx:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's REDACTED 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 as REDACTED scripts and run them in CI.
R7 · Dead Code
- 3 file(s) (~162 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- 1 file(s) (~47 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/Client
- 67 file(s) (~18359 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: src/Components/src/index.ts imports './dist/Composite/SortableList/SortableList.fs', 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. — src/Components
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×25) — src/Components/playground/App.tsx:34, src/Components/playground/App.tsx:94, src/Components/playground/App.tsx:101, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root REDACTED 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. (×3)
- Only test files import it (first: src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx:3) — move it to devDependencies. — src/Components/REDACTED:57
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/cytoscape/3.18.0/cytoscape.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — src/Server/public/test.html:4
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Solid. |
| Architecture | 86% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 72% | Strong | Solid. |
| Readiness | 30% | Weak — gated by D13, R4, R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D30 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 42% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 66 check(s) not relevant to this codebase
- AX1 Captive dependencies — 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
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:7474: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:7474/ Call log: - navigating to "http://127.0.0.1:7474/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:7687: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:7687/ Call log: - navigating to "http://127.0.0.1:7687/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:6379: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:6379/ Call log: - navigating to "http://127.0.0.1:6379/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:1111: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:1111/ Call log: - navigating to "http://127.0.0.1:1111/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:8000: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:8000/ Call log: - navigating to "http://127.0.0.1:8000/", waiting until "load" . This repository also has a user interface (212 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — 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 included (time budget)
- D11 Test Reliability — Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root; vitest via `npm ci --ignore-scripts` in src/Components/): not included — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
- D12 Dependency Hygiene — Dependency hygiene not measured
- 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.
- D2 Cognitive Complexity — Cognitive Complexity not included (time budget)
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 47 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- 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 repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half could not be measured — the repository root 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. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 strongly-typed id(s); 439 value object(s); 39 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 130,110 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- 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.
- 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.
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 146 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label src/Client/Index.fs:70
- <input> without a programmatic label src/Client/MainComponents/FooterTabs.fs:94
- <input> without a programmatic label src/Client/MainComponents/NoFileElement.fs:22
- <input> without a programmatic label src/Client/MainComponents/TableFooter.fs:25
- <input> without a programmatic label src/Client/Modals/SelectiveImportModal.fs:67
- <input> without a programmatic label src/Client/Modals/SelectiveImportModal.fs:234
- <input> without a programmatic label src/Client/Pages/BuildingBlock/Dropdown.fs:20
- <input> without a programmatic label src/Client/Pages/BuildingBlock/SearchComponent.fs:129
- <input> without a programmatic label src/Client/Pages/BuildingBlock/SearchComponent.fs:155
- <input> without a programmatic label src/Client/Pages/FilePicker/FilePickerView.fs:51
- <input> without a programmatic label src/Client/Pages/JsonImport/JsonImport.fs:93
- <input> without a programmatic label src/Client/Pages/ProtocolTemplates/ProtocolView.fs:63
- <input> without a programmatic label src/Client/Pages/Settings/SettingsView.fs:156
- <input> without a programmatic label src/Client/SharedComponents/Metadata/Forms.fs:203
- <input> without a programmatic label src/Client/SharedComponents/Metadata/Forms.fs:897
- <input> without a programmatic label src/Client/SharedComponents/Metadata/Forms.fs:928
- <input> without a programmatic label src/Client/SharedComponents/Metadata/Forms.fs:1226
- <input> without a programmatic label src/Client/SharedComponents/Metadata/Generic.fs:64
- <input> without a programmatic label src/Components/src/Composite/AnnotationTable/Modals.fs:205
- <input> without a programmatic label src/Components/src/Composite/AnnotationTable/Modals.fs:1127
- Click handler on a non-interactive <div> src/Client/MainComponents/FooterTabs.fs:120
- Click handler on a non-interactive <div> src/Client/MainComponents/FooterTabs.fs:167
- Click handler on a non-interactive <div> src/Client/MainComponents/FooterTabs.fs:196
- Click handler on a non-interactive <div> src/Client/MainComponents/FooterTabs.fs:224
- Click handler on a non-interactive <div> src/Client/MainComponents/FooterTabs.fs:257
- Click handler on a non-interactive <div> src/Client/Modals/InteropLoggingModal.fs:44
- Click handler on a non-interactive <div> src/Client/SharedComponents/Logo.fs:11
- Click handler on a non-interactive <div> src/Client/Views/SpreadsheetView.fs:12
- Click handler on a non-interactive <div> src/Components/src/Composite/AnnotationTable/Modals.fs:1686
- Click handler on a non-interactive <div> src/Components/src/Composite/AnnotationTable/Modals.fs:1695
- Click handler on a non-interactive <div> src/Components/src/Composite/AnnotationTable/Modals.fs:1704
- Click handler on a non-interactive <div> src/Components/src/Composite/Notes/NoteSearch/NoteSearch.fs:118
- Click handler on a non-interactive <div> src/Components/src/Composite/Widgets/DataAnnotator/DataAnnotator.fs:101
- Click handler on a non-interactive <div> src/Components/src/Page/ProvenanceGrouping/GroupCard.fs:524
- Click handler on a non-interactive <div> src/Components/src/Page/SettingsPage/SettingsPage.fs:400
- <label> that labels no control src/Client/Modals/SelectiveImportModal.fs:94
- <label> that labels no control src/Client/Pages/Settings/SettingsView.fs:135
- <label> that labels no control src/Client/SharedComponents/Metadata/Forms.fs:197
- <label> that labels no control src/Client/SharedComponents/Metadata/Forms.fs:1342
- <label> that labels no control src/Client/SharedComponents/NavbarBurger.fs:14
- <label> that labels no control src/Components/playground/App.tsx:43
- <label> that labels no control src/Components/playground/App.tsx:65
- <label> that labels no control src/Components/playground/App.tsx:77
- <label> that labels no control src/Components/src/Composite/AnnotationTable/Modals.fs:204
- <label> that labels no control src/Components/src/Composite/AnnotationTable/Modals.fs:230
- <label> that labels no control src/Components/src/Composite/AnnotationTable/Modals.fs:1080
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label src/Client/MainComponents/EmptyTableModals.fs:132
- <select> without a programmatic label src/Client/Pages/JsonExporter/JsonExporter.fs:58
- <select> without a programmatic label src/Client/Pages/JsonImport/JsonImport.fs:70
- <select> without a programmatic label src/Client/SharedComponents/Metadata/Forms.fs:881
- <select> without a programmatic label src/Components/src/Composite/AnnotationTable/Modals.fs:1243
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang src/Client/index.html:2
- <html> without a lang src/Electron/index.html:2
- <html> without a lang src/Server/public/test.html:2
- <button> with no accessible text src/Client/Pages/ProtocolTemplates/ProtocolView.fs:264
- <button> with no accessible text src/Components/src/Composite/Actionbar/Actionbar.fs:44
- Click handler on a non-interactive <li> src/Client/Views/MainPageViews.fs:20
- Click handler on a non-interactive <li> src/Components/src/Composite/ArcSelector/ArcSelector.fs:28
- Test suite cannot be installed from its own lockfile: the repository root
- Test suite cannot be installed from its own lockfile: src/Components/
- <img> without a text alternative src/Client/Pages/Info/InfoView.fs:44
- <iframe> without a title src/Electron/src/Renderer/Components/MainContent/PDFViewer.fs:42
- Document without a <title> src/Server/public/test.html:2
- Clickable role="tab" that no keyboard user can reach src/Components/src/Composite/TermSearch/TermSearch.fs:676
- Click handler on a non-interactive <span> src/Components/src/Page/FileExplorer/FileExplorerItem.fs:271
- Hover-only interaction on <article> src/Components/src/Page/ProvenanceGrouping/GroupCard.fs:417
- Focusable <div> isn't keyboard-operable src/Components/src/Primitive/CardGrid/CardGrid.fs:15
- Focusable <ul> isn't keyboard-operable src/Components/src/Primitive/Dropdown/Dropdown.fs:44
- Production project references a test project: Client.Tests → Shared.Tests tests/Client/Client.Tests.fsproj:18
- REDACTED
- REDACTED
- REDACTED
Serious — 181 finding(s)
- Hotspot: src/Electron/src/Renderer/Context/GitWorkflow.fs src/Electron/src/Renderer/Context/GitWorkflow.fs:4823
- Hotspot: src/Electron/src/Main/IPC/IArcVaultsApi.fs src/Electron/src/Main/IPC/IArcVaultsApi.fs:220
- Hotspot: src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs:1194
- Hotspot: src/Electron/src/Renderer/Components/LeftSidebar/FileExplorer/FileTree.fs src/Electron/src/Renderer/Components/LeftSidebar/FileExplorer/FileTree.fs:44
- Hotspot: src/Electron/src/Main/ArcVault/ArcVault.fs src/Electron/src/Main/ArcVault/ArcVault.fs:339
- Hotspot: src/Electron/src/Main/IPC/IVersionControlApi.fs src/Electron/src/Main/IPC/IVersionControlApi.fs:464
- Hotspot: src/Components/src/Composite/GraphCanvas/GraphCanvas.fs src/Components/src/Composite/GraphCanvas/GraphCanvas.fs:919
- Hotspot: src/Components/src/Page/GitSidebar/GitSidebar.fs src/Components/src/Page/GitSidebar/GitSidebar.fs:1844
- Hotspot: src/Electron/src/Main/ArcVault/ArcVaultHelper.fs src/Electron/src/Main/ArcVault/ArcVaultHelper.fs:65
- Hotspot: src/Shared/PathHelpers.fs src/Shared/PathHelpers.fs:399
- Hotspot: src/Electron/src/Renderer/Components/MainContent/GitDiffTarget.fs src/Electron/src/Renderer/Components/MainContent/GitDiffTarget.fs:110
- Hotspot: src/Electron/src/Renderer/Components/MainContent/Main.fs src/Electron/src/Renderer/Components/MainContent/Main.fs:86
- Hotspot: src/Components/src/Page/FileExplorer/FileExplorer.fs src/Components/src/Page/FileExplorer/FileExplorer.fs:142
- Hotspot: src/Components/src/Page/ProvenanceGraph/ProvenanceGraph.fs src/Components/src/Page/ProvenanceGraph/ProvenanceGraph.fs:296
- Hotspot: src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs:267
- Hotspot: src/Electron/src/Renderer/Components/MainContent/ArcFilePreviewTarget.fs src/Electron/src/Renderer/Components/MainContent/ArcFilePreviewTarget.fs:19
- Hotspot: src/Shared/ARCtrl.Helper.fs src/Shared/ARCtrl.Helper.fs:21
- Hotspot: src/Electron/src/Renderer/Context/FileStateContext.fs src/Electron/src/Renderer/Context/FileStateContext.fs:89
- Hotspot: src/Components/src/Page/ArcFileEditor/ArcFileFooterTabs.fs src/Components/src/Page/ArcFileEditor/ArcFileFooterTabs.fs:331
- Hotspot: src/Electron/src/Swate.Electron.Shared/FileIOHelper.fs src/Electron/src/Swate.Electron.Shared/FileIOHelper.fs:196
- Hotspot: src/Electron/src/Renderer/Components/Helper/FileExplorerStateReconciliation.fs src/Electron/src/Renderer/Components/Helper/FileExplorerStateReconciliation.fs:115
- Hotspot: src/Components/src/Composite/AnnotationTable/ContextMenu.fs src/Components/src/Composite/AnnotationTable/ContextMenu.fs:202
- Hotspot: src/Electron/src/Renderer/Context/FileTreeExpansionContext.fs src/Electron/src/Renderer/Context/FileTreeExpansionContext.fs:141
- Hotspot: src/Components/src/Page/FileExplorer/FileExplorerItem.fs src/Components/src/Page/FileExplorer/FileExplorerItem.fs:118
- Hotspot: src/Components/src/Page/ValidationPackageBrowser/ValidationPackageBrowser.fs src/Components/src/Page/ValidationPackageBrowser/ValidationPackageBrowser.fs:121
- FileTooLong: Context/GitWorkflow.fs src/Electron/src/Renderer/Context/GitWorkflow.fs
- FileTooLong: GitComparison/GitPagedDiffViewer.fs src/Components/src/Page/GitComparison/GitPagedDiffViewer.fs
- FileTooLong: GitSidebar/GitSidebar.fs src/Components/src/Page/GitSidebar/GitSidebar.fs
- FileTooLong: ProvenanceGrouping/Controls.fs src/Components/src/Page/ProvenanceGrouping/Controls.fs
- FileTooLong: OfficeInterop/OfficeInterop.fs src/Client/OfficeInterop/OfficeInterop.fs
- FileTooLong: ProvenanceGrouping/ProvenanceGrouping.fs src/Components/src/Page/ProvenanceGrouping/ProvenanceGrouping.fs
- FileTooLong: GraphCanvas/GraphCanvas.fs src/Components/src/Composite/GraphCanvas/GraphCanvas.fs
- FileTooLong: AnnotationTable/Modals.fs src/Components/src/Composite/AnnotationTable/Modals.fs
- FileTooLong: Metadata/Forms.fs src/Client/SharedComponents/Metadata/Forms.fs
- FileTooLong: IPC/IVersionControlApi.fs src/Electron/src/Main/IPC/IVersionControlApi.fs
- FileTooLong: IPC/IArcVaultsApi.fs src/Electron/src/Main/IPC/IArcVaultsApi.fs
- FileTooLong: TermSearch/TermSearch.fs src/Components/src/Composite/TermSearch/TermSearch.fs
- FileTooLong: Api/GitLabApi.fs src/Components/src/Api/GitLabApi.fs
- FileTooLong: IPC/FileSystemIO.fs src/Electron/src/Main/IPC/FileSystemIO.fs
- FileTooLong: DataHubBrowser/DataHubBrowser.fs src/Components/src/Page/DataHubBrowser/DataHubBrowser.fs
- FileTooLong: ArcVault/ArcVault.fs src/Electron/src/Main/ArcVault/ArcVault.fs
- FileTooLong: GitComparison/GitMergeConflictViewer.fs src/Components/src/Page/GitComparison/GitMergeConflictViewer.fs
- FileTooLong: AnnotationTable/ContextMenu.fs src/Components/src/Composite/AnnotationTable/ContextMenu.fs
- FileTooLong: ProvenanceGrouping/ARCtrlConverter.fs src/Shared/ProvenanceGrouping/ARCtrlConverter.fs
- FileTooLong: ArcVault/ArcVaultFileWatcher.fs src/Electron/src/Main/ArcVault/ArcVaultFileWatcher.fs
- FileTooLong: ProvenanceGrouping/State.fs src/Components/src/Page/ProvenanceGrouping/State.fs
- FileTooLong: Api/IOntologyAPI.fs src/Server/Api/IOntologyAPI.fs
- FileTooLong: VersionControl/Mappings.fs src/Electron/src/Main/VersionControl/Mappings.fs
- FileTooLong: Shared/PathHelpers.fs src/Shared/PathHelpers.fs
- FileTooLong: ProvenanceGrouping/PropertyModel.fs src/Components/src/Page/ProvenanceGrouping/PropertyModel.fs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anchor without href src/Client/MainComponents/NoFileElement.fs:67
- Anchor without href src/Client/Pages/BuildingBlock/Dropdown.fs:96
- Anchor without href src/Client/Pages/BuildingBlock/Dropdown.fs:112
- Anchor without href src/Client/SharedComponents/NavbarBurger.fs:53
- Anchor without href src/Client/Views/MainPageViews.fs:23
- Anchor without href src/Components/src/Composite/AnnotationTable/Modals.fs:766
- Anchor without href src/Components/src/Composite/Layout/Layout.fs:573
- Anchor without href src/Components/src/Composite/Layout/Layout.fs:581
- Anchor without href src/Components/src/Composite/TermSearch/TermSearch.fs:270
- Animation without a prefers-reduced-motion guard src/Electron/src/Renderer/tailwind.css:254
- Animation without a prefers-reduced-motion guard src/Components/tailwind.css:218
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Components/src/swate-components.css:2
- Animation without a prefers-reduced-motion guard src/Client/tailwind.css:207
- Change coupling: REDACTED ↔ Server.fs REDACTED:1
- Change coupling: Mappings.fs ↔ GitWorkflow.fs src/Electron/src/Main/VersionControl/Mappings.fs:1
- Change coupling: FileTreeCreator.fs ↔ FileExplorerLfs.fs src/Electron/src/Main/FileTreeCreator.fs:1
- Change coupling: IArcVaultsApi.fs ↔ InitState.fs src/Electron/src/Main/IPC/IArcVaultsApi.fs:1
- Change coupling: ArcFileEditor.fs ↔ REDACTED src/Components/src/Page/ArcFileEditor/ArcFileEditor.fs:1
- Change coupling: FileExplorer.stories.tsx ↔ FileExplorerItem.fs src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx:1
- Change coupling: Virtual.fs ↔ GitPagedDiffViewer.stories.tsx src/Components/src/JsBindings/Virtual.fs:1
- Change coupling: Actionbar.fs ↔ ArcSelector.stories.tsx src/Components/src/Composite/Actionbar/Actionbar.fs:1
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- Focus outline removed in CSS without a :focus replacement src/Components/src/swate-components.css:2
- TooManyFunctions: GitWorkflow src/Electron/src/Renderer/Context/GitWorkflow.fs:1
- TooManyFunctions: GitDiffPageLoader src/Electron/src/Renderer/Context/GitWorkflow.fs:1532
- TooManyFunctions: Session src/Shared/ProvenanceGrouping/Session.fs:89
- TooManyFunctions: VersionControlApiClient src/Electron/src/Renderer/VersionControlApiClient.fs:5
- TooManyFunctions: AuthService src/Electron/src/Main/Auth/AuthService.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Data table has no header cells src/Client/Pages/FilePicker/FilePickerView.fs:244
- Data table has no header cells src/Components/src/Composite/SortableList/SortableList.fs:218
- Data table has no header cells src/Components/src/Primitive/BaseModal/BaseModal.fs:249
- No test reaches this file src/Components/playground/App.tsx:1
- No test reaches this file src/Electron/scripts/forge-make.cjs:1
- No test reaches this file src/Components/playground/main.tsx:1
- Repeated repair: src/Components/src/ClipboardContract/Contract.fs src/Components/src/ClipboardContract/Contract.fs:50
- Repeated repair: src/Components/src/Composite/TemplateBrowser/Helper.fs src/Components/src/Composite/TemplateBrowser/Helper.fs:111
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <fieldset> without a <legend> src/Client/Modals/SelectiveImportModal.fs:130
- <ComboBox> field component without a label src/Components/playground/App.tsx:127
- Heading level jumps from h1 to h3 src/Components/src/Page/Changelog/Changelog.fs:292
- Empty <h3> heading src/Components/src/Page/ProvenanceGrouping/EditorPanels.fs:292
- Link used as a button (placeholder href) src/Client/Pages/BuildingBlock/Dropdown.fs:49
- Accessibility enforcement below the top rung REDACTED:15
- Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile
- REDACTED
- TooManyMethods: Icons src/Components/src/Primitive/Icons.fs:9
- Change coupling clique: main.fs, preload.fs, REDACTED src/Electron/src/Main/main.fs
- REDACTED
- Coverage not measured — .NET and JavaScript/TypeScript suite
- Duplicated block (12 lines × 6 locations) src/Components/playground/App.tsx:90
- Duplicated block (12 lines × 5 locations) src/Components/playground/App.tsx:112
- Boundary violation [package:third-party-deep-import] src/Electron/scripts/forge-make.cjs:8
- src/Components/src/Page/GitComparison/GitPagedDiffViewer.stories.tsx: 2896 lines of code src/Components/src/Page/GitComparison/GitPagedDiffViewer.stories.tsx:1
- REDACTED: 2449 lines of code REDACTED:1
- src/Components/src/Page/GitSidebar/GitSidebar.stories.tsx: 954 lines of code src/Components/src/Page/GitSidebar/GitSidebar.stories.tsx:1
- src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx: 945 lines of code src/Components/src/Page/FileExplorer/FileExplorer.stories.tsx:1
- src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx: 800 lines of code src/Components/src/Composite/FolderedDraggableList/FolderedDraggableList.stories.tsx:1
- src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx: 647 lines of code src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx:1
- src/Components/src/Page/GitComparison/GitMergeConflictViewer.stories.tsx: 575 lines of code src/Components/src/Page/GitComparison/GitMergeConflictViewer.stories.tsx:1
- No lint script
- Unused dependency '@fable-org/fable-library-js'
- Unused dependency '@iconify-json/fluent'
- Unused dependency '@iconify/tailwind4'
- Third-party script without Subresource Integrity src/Server/public/test.html:4
Minor — 49 finding(s)
- Duplicated predicate src/Components/src/Composite/MarkdownText/Plugins/AddImage.fs:34
- Duplicated predicate src/Client/Pages/BuildingBlock/Helper.fs:58
- Duplicated predicate src/Electron/src/Main/Helper/WindowSend.fs:9
- Duplicated predicate src/Electron/src/Renderer/Components/LeftSidebar/Git/GitSidebarPanel.fs:27
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- REDACTED
- REDACTED
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:4
- No dependency-update automation Directory.Packages.props:6
- No rollback/health safety
- Unused module-local declaration 'TermSearchContainer' src/Components/playground/App.tsx:34
- Unused module-local declaration 'TableContainer' src/Components/playground/App.tsx:94
- Unused module-local declaration 'AnnoTableContainer' src/Components/playground/App.tsx:101
- Unused module-local declaration 'ContextMenuContainer' src/Components/playground/App.tsx:110
- Unused module-local declaration 'TemplateFilterContainer' src/Components/playground/App.tsx:117
- Unused module-local declaration 'ComboBoxContainer' src/Components/playground/App.tsx:124
- Unused module-local declaration 'BaseModalContainer' src/Components/playground/App.tsx:138
- Unused module-local declaration 'DataMapTableContainer' src/Components/playground/App.tsx:145
- Unused module-local declaration 'FileExplorerContainer' src/Components/playground/App.tsx:152
- Unused module-local declaration 'WidgetControllerContainer' src/Components/playground/App.tsx:159
- Unused module-local declaration 'LandingContainer' src/Components/playground/App.tsx:166
- Unused module-local declaration 'MarkdownTextContainer' src/Components/playground/App.tsx:182
- Unused module-local declaration 'AuthButtonContainer' src/Components/playground/App.tsx:189
- Unused module-local declaration 'DataHubBrowserContainer' src/Components/playground/App.tsx:196
- Unused module-local declaration 'ARCSelectorContainer' src/Components/playground/App.tsx:203
- Unused module-local declaration 'WorkspaceContainer' src/Components/playground/App.tsx:216
- Unused module-local declaration 'ValidationPackageBrowserFixtureContainer' src/Components/playground/App.tsx:224
- Unused module-local declaration 'SortableListContainer' src/Components/playground/App.tsx:232
- Unused module-local declaration 'DataAnnotatorContainer' src/Components/playground/App.tsx:242
- Unused module-local declaration 'getLayoutLeafCount' src/Components/src/Composite/Workspace/Helper/WorkspaceModel.test.ts:47
- Unused module-local declaration 'dragByPointer' src/Components/src/Composite/Workspace/Workspace.stories.tsx:24
- Unused module-local declaration 'dragToPaneEdge' src/Components/src/Composite/Workspace/Workspace.stories.tsx:66
- Unused module-local declaration 'SingleTabHarness' src/Components/src/Composite/Workspace/Workspace.stories.tsx:139
- Unused module-local declaration 'ButtonProps' src/Components/src/Primitive/BaseModal/BaseModal.stories.tsx:7
- Unused module-local declaration 'proxyTarget' tests/Client/vite.config.mts:5
- Test-only dependency '@dnd-kit/core' in production deps src/Components/REDACTED:57
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bf2ff86ed7af46f292825d394b614db3/history.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bf2ff86ed7af46f292825d394b614db3/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 35 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Swate.sln package --vulnerable --include-transitive --format json | 48 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 47 file(s) — `src/Components/src/Composite/Actionbar/Actionbar.stories.tsx`, `src/Components/src/Composite/AnnotationTable/AnnotationTable.stories.tsx`, `src/Components/src/Composite/AnnotationTable/ResetTableConfirmationModal.stories.tsx`, `src/Components/src/Composite/ArcSelector/ArcSelector.stories.tsx`, `src/Components/src/Composite/ArcVaultActions/ArcVaultActions.stories.tsx`, … (+42 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |