Executive summary
microsoft/vscode-fabric meets our standard for a preview release, though it has uses of packages that aren't listed. It scores 66.0 out of 100 and is rated Strong, and six of its 11 critical findings are security problems.
Production Readiness, at 51.1, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 9.3 points. Tidying the declared packages would lift Production Readiness itself, worth about 8.4 points. Raising Production Readiness to 62 would lift the score to about 71.0.
Three known security holes in the packages the code depends on can be used by attackers. Two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Updating the vulnerable packages and passing outside input through environment variables would close both risks. The password or key in the code's history needs replacing, with the old one switched off. The two loops of files that import each other need breaking.
The product code is 16,977 lines, about €44,000 to rebuild.
If Production Readiness rose from 51.1 to 62, the lowest score rated Strong, the score would rise from 66.0 to about 71.0.
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €74,000, for 245 to 777 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 16,977 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 api.src.FabricApiClient | 2 extension.src.authentication.interfaces | 3 extension.src.collections.definitions | 4 util.src.logger.Logger | 5 util.src.settings.ConfigurationProvider | 6 util.src.telemetry.TelemetryActivity | 7 util.src.telemetry.TelemetryService | 8 api.src.treeView | 9 extension.src.CapacityManager | 10 extension.src.settings.definitions | 11 util.src.settings.FabricEnvironmentProvider | 12 api.src.satelliteFabricExtension | 13 extension.src.LocalFolderService | 14 extension.src.fabric.FabricApiClient | 15 extension.src.internalSatellites.database.AbstractDatabaseTreeNode | 16 api.src.fabricExtension | 17 extension.src.fabric.FakeFabricApiClient | 18 extension.src.apis.internal.fabricExtensionInternal | 19 extension.src.workspace.DefinitionFileSystemProvider | 20 extension.src.workspace.WorkspaceFilterManager | 21 extension.src.extensionManager.FabricExtensionManager | 22 extension.src.workspace.WorkspaceManager | 23 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection | 24 extension.src.workspace | 25 extension.src.workspace.definitions | 26 extension.src.workspace.mockWorkspaceManager | 27 extension.src.workspace.treeNodes.ArtifactTypeTreeNode | 28 extension.src.localProject.LocalProjectTreeDataProvider | 29 extension.src.workspace.treeNodes.RootTreeNode | 30 extension.src.workspace.treeNodes.TenantTreeNode | 31 extension.src.workspace.treeNodes.WorkspaceTreeNode | 32 extension.src.workspace.treeView | 33 extension.src.artifactManager | 34 extension.src.artifactManager.ArtifactManager | 35 extension.src.commands.IFabricCommandManager | 36 extension.src.localProject | 37 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode | 38 extension.src.artifactManager.MockArtifactManager | 39 extension.src.commands.FabricCommand | 40 extension.src.commands.FabricCommandManager |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 api.src.FabricApiClient | ||||||||||||||||||||||||||||||||||||||||
| 2 extension.src.authentication.interfaces | ||||||||||||||||||||||||||||||||||||||||
| 3 extension.src.collections.definitions | ||||||||||||||||||||||||||||||||||||||||
| 4 util.src.logger.Logger | ||||||||||||||||||||||||||||||||||||||||
| 5 util.src.settings.ConfigurationProvider | ||||||||||||||||||||||||||||||||||||||||
| 6 util.src.telemetry.TelemetryActivity | ||||||||||||||||||||||||||||||||||||||||
| 7 util.src.telemetry.TelemetryService | ||||||||||||||||||||||||||||||||||||||||
| 8 api.src.treeView | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 9 extension.src.CapacityManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 extension.src.settings.definitions | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 util.src.settings.FabricEnvironmentProvider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 api.src.satelliteFabricExtension | 26 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 extension.src.LocalFolderService | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 extension.src.fabric.FabricApiClient | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 extension.src.internalSatellites.database.AbstractDatabaseTreeNode | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 api.src.fabricExtension | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 extension.src.fabric.FakeFabricApiClient | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 18 extension.src.apis.internal.fabricExtensionInternal | 3 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 19 extension.src.workspace.DefinitionFileSystemProvider | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 extension.src.workspace.WorkspaceFilterManager | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 21 extension.src.extensionManager.FabricExtensionManager | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 extension.src.workspace.WorkspaceManager | 4 | 2 | 2 | 2 | 2 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||
| 23 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 extension.src.workspace | 2 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 25 extension.src.workspace.definitions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 extension.src.workspace.mockWorkspaceManager | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 extension.src.workspace.treeNodes.ArtifactTypeTreeNode | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 extension.src.localProject.LocalProjectTreeDataProvider | 1 | 4 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 29 extension.src.workspace.treeNodes.RootTreeNode | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 30 extension.src.workspace.treeNodes.TenantTreeNode | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 extension.src.workspace.treeNodes.WorkspaceTreeNode | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 extension.src.workspace.treeView | 2 | 1 | 2 | 2 | 1 | 2 | 2 | 2 | 1 | 2 | 3 | |||||||||||||||||||||||||||||
| 33 extension.src.artifactManager | 9 | 1 | 4 | 4 | 8 | 2 | 2 | 4 | 11 | 6 | 2 | 4 | ||||||||||||||||||||||||||||
| 34 extension.src.artifactManager.ArtifactManager | 4 | 1 | 1 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 35 extension.src.commands.IFabricCommandManager | 1 | 1 | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 extension.src.localProject | 1 | 2 | 1 | 1 | 2 | 2 | 2 | 3 | 3 | 2 | 2 | |||||||||||||||||||||||||||||
| 37 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 extension.src.artifactManager.MockArtifactManager | 3 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 39 extension.src.commands.FabricCommand | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 extension.src.commands.FabricCommandManager | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 2 |
8→1 api.src.treeView uses api.src.FabricApiClient✕
- Connections
- 2 pairs of types, where a type in api.src.treeView uses a type in api.src.FabricApiClient.
- The types involved
api.src.treeView.ArtifactTreeNode→api.src.FabricApiClient.IArtifactapi.src.treeView.ArtifactTreeNodeProvider→api.src.FabricApiClient.IArtifact
- Direction
- api.src.treeView uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break api.src.treeView, while a change to api.src.treeView can't break api.src.FabricApiClient.
- Position
- Below the diagonal: api.src.treeView uses a module listed above it, which is the healthy direction.
8→12 api.src.treeView uses api.src.satelliteFabricExtension part of a loop✕
- Connections
- 4 pairs of types, where a type in api.src.treeView uses a type in api.src.satelliteFabricExtension.
- The types involved
api.src.treeView.ArtifactTreeNode→api.src.satelliteFabricExtension.ArtifactDesignerActionsapi.src.treeView.ArtifactTreeNodeProvider→api.src.satelliteFabricExtension.IFabricTreeNodeProviderapi.src.treeView.LocalProjectTreeNode→api.src.satelliteFabricExtension.LocalProjectDesignerActionsapi.src.treeView.LocalProjectTreeNodeProvider→api.src.satelliteFabricExtension.ILocalProjectTreeNodeProvider
- Direction
- api.src.treeView uses api.src.satelliteFabricExtension, so a change to api.src.satelliteFabricExtension can break api.src.treeView, while a change to api.src.treeView can't break api.src.satelliteFabricExtension.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 extension.src.CapacityManager uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.CapacityManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.CapacityManager.CapacityManager→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.CapacityManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.CapacityManager, while a change to extension.src.CapacityManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.CapacityManager uses a module listed above it, which is the healthy direction.
10→2 extension.src.settings.definitions uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.settings.definitions uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.settings.definitions.IFabricExtensionSettings→extension.src.authentication.interfaces.ITenantSettings
- Direction
- extension.src.settings.definitions uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.settings.definitions, while a change to extension.src.settings.definitions can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.settings.definitions uses a module listed above it, which is the healthy direction.
11→4 util.src.settings.FabricEnvironmentProvider uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in util.src.settings.FabricEnvironmentProvider uses a type in util.src.logger.Logger.
- The types involved
util.src.settings.FabricEnvironmentProvider.FabricEnvironmentProvider→util.src.logger.Logger.ILogger
- Direction
- util.src.settings.FabricEnvironmentProvider uses util.src.logger.Logger, so a change to util.src.logger.Logger can break util.src.settings.FabricEnvironmentProvider, while a change to util.src.settings.FabricEnvironmentProvider can't break util.src.logger.Logger.
- Position
- Below the diagonal: util.src.settings.FabricEnvironmentProvider uses a module listed above it, which is the healthy direction.
11→5 util.src.settings.FabricEnvironmentProvider uses util.src.settings.ConfigurationProvider✕
- Connections
- 1 pair of types, where a type in util.src.settings.FabricEnvironmentProvider uses a type in util.src.settings.ConfigurationProvider.
- The types involved
util.src.settings.FabricEnvironmentProvider.FabricEnvironmentProvider→util.src.settings.ConfigurationProvider.IConfigurationProvider
- Direction
- util.src.settings.FabricEnvironmentProvider uses util.src.settings.ConfigurationProvider, so a change to util.src.settings.ConfigurationProvider can break util.src.settings.FabricEnvironmentProvider, while a change to util.src.settings.FabricEnvironmentProvider can't break util.src.settings.ConfigurationProvider.
- Position
- Below the diagonal: util.src.settings.FabricEnvironmentProvider uses a module listed above it, which is the healthy direction.
12→1 api.src.satelliteFabricExtension uses api.src.FabricApiClient✕
- Connections
- 26 pairs of types, where a type in api.src.satelliteFabricExtension uses a type in api.src.FabricApiClient. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
api.src.satelliteFabricExtension.IArtifactHandler→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IArtifactHandler→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.IArtifactHandler→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.ICreateArtifactWithDefinitionWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.ICreateArtifactWithDefinitionWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.ICreateArtifactWithDefinitionWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.ICreateArtifactWithDefinitionWorkflow→api.src.FabricApiClient.IItemDefinitionapi.src.satelliteFabricExtension.ICreateArtifactWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.ICreateArtifactWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.ICreateArtifactWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IDeleteArtifactWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IDeleteArtifactWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.IDeleteArtifactWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IFabricTreeNodeProvider→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IGetArtifactDefinitionWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IGetArtifactDefinitionWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.IGetArtifactDefinitionWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IReadArtifactWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IReadArtifactWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IRenameArtifactWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IRenameArtifactWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.IRenameArtifactWorkflow→api.src.FabricApiClient.IArtifactapi.src.satelliteFabricExtension.IUpdateArtifactDefinitionWorkflow→api.src.FabricApiClient.IApiClientRequestOptionsapi.src.satelliteFabricExtension.IUpdateArtifactDefinitionWorkflow→api.src.FabricApiClient.IApiClientResponseapi.src.satelliteFabricExtension.IUpdateArtifactDefinitionWorkflow→api.src.FabricApiClient.IArtifact
- Direction
- api.src.satelliteFabricExtension uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break api.src.satelliteFabricExtension, while a change to api.src.satelliteFabricExtension can't break api.src.FabricApiClient.
- Position
- Below the diagonal: api.src.satelliteFabricExtension uses a module listed above it, which is the healthy direction.
12→8 api.src.satelliteFabricExtension uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in api.src.satelliteFabricExtension uses a type in api.src.treeView.
- The types involved
api.src.satelliteFabricExtension.IFabricTreeNodeProvider→api.src.treeView.ArtifactTreeNode
- Direction
- api.src.satelliteFabricExtension uses api.src.treeView, so a change to api.src.treeView can break api.src.satelliteFabricExtension, while a change to api.src.satelliteFabricExtension can't break api.src.treeView.
- Position
- Below the diagonal: api.src.satelliteFabricExtension uses a module listed above it, which is the healthy direction.
12→16 api.src.satelliteFabricExtension uses api.src.fabricExtension part of a loop✕
- Connections
- 2 pairs of types, where a type in api.src.satelliteFabricExtension uses a type in api.src.fabricExtension.
- The types involved
api.src.satelliteFabricExtension.IArtifactHandler→api.src.fabricExtension.IOpenArtifactOptionsapi.src.satelliteFabricExtension.IArtifactHandler→api.src.fabricExtension.OperationRequestType
- Direction
- api.src.satelliteFabricExtension uses api.src.fabricExtension, so a change to api.src.fabricExtension can break api.src.satelliteFabricExtension, while a change to api.src.satelliteFabricExtension can't break api.src.fabricExtension.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 extension.src.LocalFolderService uses api.src.FabricApiClient✕
- Connections
- 2 pairs of types, where a type in extension.src.LocalFolderService uses a type in api.src.FabricApiClient.
- The types involved
extension.src.LocalFolderService.ILocalFolderService→api.src.FabricApiClient.IArtifactextension.src.LocalFolderService.LocalFolderService→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.LocalFolderService uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.LocalFolderService, while a change to extension.src.LocalFolderService can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.LocalFolderService uses a module listed above it, which is the healthy direction.
13→10 extension.src.LocalFolderService uses extension.src.settings.definitions✕
- Connections
- 2 pairs of types, where a type in extension.src.LocalFolderService uses a type in extension.src.settings.definitions.
- The types involved
extension.src.LocalFolderService.LocalFolderService→extension.src.settings.definitions.IFabricExtensionsSettingStorageextension.src.LocalFolderService.LocalFolderService→extension.src.settings.definitions.ILocalFolderSettingsStore
- Direction
- extension.src.LocalFolderService uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.LocalFolderService, while a change to extension.src.LocalFolderService can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.LocalFolderService uses a module listed above it, which is the healthy direction.
13→11 extension.src.LocalFolderService uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.LocalFolderService uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.LocalFolderService.LocalFolderService→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.LocalFolderService uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.LocalFolderService, while a change to extension.src.LocalFolderService can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.LocalFolderService uses a module listed above it, which is the healthy direction.
14→1 extension.src.fabric.FabricApiClient uses api.src.FabricApiClient✕
- Connections
- 3 pairs of types, where a type in extension.src.fabric.FabricApiClient uses a type in api.src.FabricApiClient.
- The types involved
extension.src.fabric.FabricApiClient.FabricApiClient→api.src.FabricApiClient.IApiClientRequestOptionsextension.src.fabric.FabricApiClient.FabricApiClient→api.src.FabricApiClient.IApiClientResponseextension.src.fabric.FabricApiClient.FabricApiClient→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.fabric.FabricApiClient uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.fabric.FabricApiClient, while a change to extension.src.fabric.FabricApiClient can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.fabric.FabricApiClient uses a module listed above it, which is the healthy direction.
14→2 extension.src.fabric.FabricApiClient uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FabricApiClient uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.fabric.FabricApiClient.FabricApiClient→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.fabric.FabricApiClient uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.fabric.FabricApiClient, while a change to extension.src.fabric.FabricApiClient can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.fabric.FabricApiClient uses a module listed above it, which is the healthy direction.
14→4 extension.src.fabric.FabricApiClient uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FabricApiClient uses a type in util.src.logger.Logger.
- The types involved
extension.src.fabric.FabricApiClient.FabricApiClient→util.src.logger.Logger.ILogger
- Direction
- extension.src.fabric.FabricApiClient uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.fabric.FabricApiClient, while a change to extension.src.fabric.FabricApiClient can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.fabric.FabricApiClient uses a module listed above it, which is the healthy direction.
14→5 extension.src.fabric.FabricApiClient uses util.src.settings.ConfigurationProvider✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FabricApiClient uses a type in util.src.settings.ConfigurationProvider.
- The types involved
extension.src.fabric.FabricApiClient.FabricApiClient→util.src.settings.ConfigurationProvider.IConfigurationProvider
- Direction
- extension.src.fabric.FabricApiClient uses util.src.settings.ConfigurationProvider, so a change to util.src.settings.ConfigurationProvider can break extension.src.fabric.FabricApiClient, while a change to extension.src.fabric.FabricApiClient can't break util.src.settings.ConfigurationProvider.
- Position
- Below the diagonal: extension.src.fabric.FabricApiClient uses a module listed above it, which is the healthy direction.
14→11 extension.src.fabric.FabricApiClient uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FabricApiClient uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.fabric.FabricApiClient.FabricApiClient→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.fabric.FabricApiClient uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.fabric.FabricApiClient, while a change to extension.src.fabric.FabricApiClient can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.fabric.FabricApiClient uses a module listed above it, which is the healthy direction.
15→1 extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses api.src.FabricApiClient✕
- Connections
- 3 pairs of types, where a type in extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses a type in api.src.FabricApiClient.
- The types involved
extension.src.internalSatellites.database.AbstractDatabaseTreeNode.AbstractDatabaseTreeNode→api.src.FabricApiClient.IApiClientResponseextension.src.internalSatellites.database.AbstractDatabaseTreeNode.AbstractDatabaseTreeNode→api.src.FabricApiClient.IArtifactextension.src.internalSatellites.database.AbstractDatabaseTreeNode.AbstractDatabaseTreeNode→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.internalSatellites.database.AbstractDatabaseTreeNode, while a change to extension.src.internalSatellites.database.AbstractDatabaseTreeNode can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses a module listed above it, which is the healthy direction.
15→8 extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses a type in api.src.treeView.
- The types involved
extension.src.internalSatellites.database.AbstractDatabaseTreeNode.AbstractDatabaseTreeNode→api.src.treeView.ArtifactTreeNode
- Direction
- extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses api.src.treeView, so a change to api.src.treeView can break extension.src.internalSatellites.database.AbstractDatabaseTreeNode, while a change to extension.src.internalSatellites.database.AbstractDatabaseTreeNode can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.internalSatellites.database.AbstractDatabaseTreeNode uses a module listed above it, which is the healthy direction.
16→1 api.src.fabricExtension uses api.src.FabricApiClient✕
- Connections
- 7 pairs of types, where a type in api.src.fabricExtension uses a type in api.src.FabricApiClient.
- The types involved
api.src.fabricExtension.IArtifactManager→api.src.FabricApiClient.IApiClientResponseapi.src.fabricExtension.IArtifactManager→api.src.FabricApiClient.IArtifactapi.src.fabricExtension.IArtifactManager→api.src.FabricApiClient.IItemDefinitionapi.src.fabricExtension.IFabricExtensionServiceCollection→api.src.FabricApiClient.IFabricApiClientapi.src.fabricExtension.IFolderManager→api.src.FabricApiClient.IApiClientResponseapi.src.fabricExtension.IWorkspaceManager→api.src.FabricApiClient.IApiClientResponseapi.src.fabricExtension.IWorkspaceManager→api.src.FabricApiClient.IArtifact
- Direction
- api.src.fabricExtension uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break api.src.fabricExtension, while a change to api.src.fabricExtension can't break api.src.FabricApiClient.
- Position
- Below the diagonal: api.src.fabricExtension uses a module listed above it, which is the healthy direction.
16→12 api.src.fabricExtension uses api.src.satelliteFabricExtension✕
- Connections
- 1 pair of types, where a type in api.src.fabricExtension uses a type in api.src.satelliteFabricExtension.
- The types involved
api.src.fabricExtension.IFabricExtensionManager→api.src.satelliteFabricExtension.IFabricExtension
- Direction
- api.src.fabricExtension uses api.src.satelliteFabricExtension, so a change to api.src.satelliteFabricExtension can break api.src.fabricExtension, while a change to api.src.fabricExtension can't break api.src.satelliteFabricExtension.
- Position
- Below the diagonal: api.src.fabricExtension uses a module listed above it, which is the healthy direction.
17→2 extension.src.fabric.FakeFabricApiClient uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FakeFabricApiClient uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.fabric.FakeFabricApiClient.FakeFabricApiClient→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.fabric.FakeFabricApiClient uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.fabric.FakeFabricApiClient, while a change to extension.src.fabric.FakeFabricApiClient can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.fabric.FakeFabricApiClient uses a module listed above it, which is the healthy direction.
17→4 extension.src.fabric.FakeFabricApiClient uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FakeFabricApiClient uses a type in util.src.logger.Logger.
- The types involved
extension.src.fabric.FakeFabricApiClient.FakeFabricApiClient→util.src.logger.Logger.ILogger
- Direction
- extension.src.fabric.FakeFabricApiClient uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.fabric.FakeFabricApiClient, while a change to extension.src.fabric.FakeFabricApiClient can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.fabric.FakeFabricApiClient uses a module listed above it, which is the healthy direction.
17→5 extension.src.fabric.FakeFabricApiClient uses util.src.settings.ConfigurationProvider✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FakeFabricApiClient uses a type in util.src.settings.ConfigurationProvider.
- The types involved
extension.src.fabric.FakeFabricApiClient.FakeFabricApiClient→util.src.settings.ConfigurationProvider.IConfigurationProvider
- Direction
- extension.src.fabric.FakeFabricApiClient uses util.src.settings.ConfigurationProvider, so a change to util.src.settings.ConfigurationProvider can break extension.src.fabric.FakeFabricApiClient, while a change to extension.src.fabric.FakeFabricApiClient can't break util.src.settings.ConfigurationProvider.
- Position
- Below the diagonal: extension.src.fabric.FakeFabricApiClient uses a module listed above it, which is the healthy direction.
17→11 extension.src.fabric.FakeFabricApiClient uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FakeFabricApiClient uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.fabric.FakeFabricApiClient.FakeFabricApiClient→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.fabric.FakeFabricApiClient uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.fabric.FakeFabricApiClient, while a change to extension.src.fabric.FakeFabricApiClient can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.fabric.FakeFabricApiClient uses a module listed above it, which is the healthy direction.
17→14 extension.src.fabric.FakeFabricApiClient uses extension.src.fabric.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.fabric.FakeFabricApiClient uses a type in extension.src.fabric.FabricApiClient.
- The types involved
extension.src.fabric.FakeFabricApiClient.FakeFabricApiClient→extension.src.fabric.FabricApiClient.FabricApiClient
- Direction
- extension.src.fabric.FakeFabricApiClient uses extension.src.fabric.FabricApiClient, so a change to extension.src.fabric.FabricApiClient can break extension.src.fabric.FakeFabricApiClient, while a change to extension.src.fabric.FakeFabricApiClient can't break extension.src.fabric.FabricApiClient.
- Position
- Below the diagonal: extension.src.fabric.FakeFabricApiClient uses a module listed above it, which is the healthy direction.
18→1 extension.src.apis.internal.fabricExtensionInternal uses api.src.FabricApiClient✕
- Connections
- 3 pairs of types, where a type in extension.src.apis.internal.fabricExtensionInternal uses a type in api.src.FabricApiClient.
- The types involved
extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternal→api.src.FabricApiClient.IApiClientResponseextension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternal→api.src.FabricApiClient.IArtifactextension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.apis.internal.fabricExtensionInternal uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.apis.internal.fabricExtensionInternal, while a change to extension.src.apis.internal.fabricExtensionInternal can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.apis.internal.fabricExtensionInternal uses a module listed above it, which is the healthy direction.
18→3 extension.src.apis.internal.fabricExtensionInternal uses extension.src.collections.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.apis.internal.fabricExtensionInternal uses a type in extension.src.collections.definitions.
- The types involved
extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→extension.src.collections.definitions.IObservableReadOnlyMap
- Direction
- extension.src.apis.internal.fabricExtensionInternal uses extension.src.collections.definitions, so a change to extension.src.collections.definitions can break extension.src.apis.internal.fabricExtensionInternal, while a change to extension.src.apis.internal.fabricExtensionInternal can't break extension.src.collections.definitions.
- Position
- Below the diagonal: extension.src.apis.internal.fabricExtensionInternal uses a module listed above it, which is the healthy direction.
18→12 extension.src.apis.internal.fabricExtensionInternal uses api.src.satelliteFabricExtension✕
- Connections
- 3 pairs of types, where a type in extension.src.apis.internal.fabricExtensionInternal uses a type in api.src.satelliteFabricExtension.
- The types involved
extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→api.src.satelliteFabricExtension.IArtifactHandlerextension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→api.src.satelliteFabricExtension.IFabricTreeNodeProviderextension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→api.src.satelliteFabricExtension.ILocalProjectTreeNodeProvider
- Direction
- extension.src.apis.internal.fabricExtensionInternal uses api.src.satelliteFabricExtension, so a change to api.src.satelliteFabricExtension can break extension.src.apis.internal.fabricExtensionInternal, while a change to extension.src.apis.internal.fabricExtensionInternal can't break api.src.satelliteFabricExtension.
- Position
- Below the diagonal: extension.src.apis.internal.fabricExtensionInternal uses a module listed above it, which is the healthy direction.
18→16 extension.src.apis.internal.fabricExtensionInternal uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.apis.internal.fabricExtensionInternal uses a type in api.src.fabricExtension.
- The types involved
extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternal→api.src.fabricExtension.OperationRequestTypeextension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal→api.src.fabricExtension.IFabricExtensionServiceCollection
- Direction
- extension.src.apis.internal.fabricExtensionInternal uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.apis.internal.fabricExtensionInternal, while a change to extension.src.apis.internal.fabricExtensionInternal can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.apis.internal.fabricExtensionInternal uses a module listed above it, which is the healthy direction.
19→1 extension.src.workspace.DefinitionFileSystemProvider uses api.src.FabricApiClient✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.DefinitionFileSystemProvider uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider→api.src.FabricApiClient.IArtifactextension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider→api.src.FabricApiClient.IItemDefinition
- Direction
- extension.src.workspace.DefinitionFileSystemProvider uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.DefinitionFileSystemProvider, while a change to extension.src.workspace.DefinitionFileSystemProvider can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.DefinitionFileSystemProvider uses a module listed above it, which is the healthy direction.
19→4 extension.src.workspace.DefinitionFileSystemProvider uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.DefinitionFileSystemProvider uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.DefinitionFileSystemProvider uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.DefinitionFileSystemProvider, while a change to extension.src.workspace.DefinitionFileSystemProvider can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.DefinitionFileSystemProvider uses a module listed above it, which is the healthy direction.
19→11 extension.src.workspace.DefinitionFileSystemProvider uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.DefinitionFileSystemProvider uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace.DefinitionFileSystemProvider uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace.DefinitionFileSystemProvider, while a change to extension.src.workspace.DefinitionFileSystemProvider can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace.DefinitionFileSystemProvider uses a module listed above it, which is the healthy direction.
19→16 extension.src.workspace.DefinitionFileSystemProvider uses api.src.fabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.DefinitionFileSystemProvider uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider→api.src.fabricExtension.IArtifactManager
- Direction
- extension.src.workspace.DefinitionFileSystemProvider uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.DefinitionFileSystemProvider, while a change to extension.src.workspace.DefinitionFileSystemProvider can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.DefinitionFileSystemProvider uses a module listed above it, which is the healthy direction.
20→2 extension.src.workspace.WorkspaceFilterManager uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.workspace.WorkspaceFilterManager uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
20→4 extension.src.workspace.WorkspaceFilterManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.WorkspaceFilterManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
20→6 extension.src.workspace.WorkspaceFilterManager uses util.src.telemetry.TelemetryActivity✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in util.src.telemetry.TelemetryActivity.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→util.src.telemetry.TelemetryActivity.TelemetryActivity
- Direction
- extension.src.workspace.WorkspaceFilterManager uses util.src.telemetry.TelemetryActivity, so a change to util.src.telemetry.TelemetryActivity can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break util.src.telemetry.TelemetryActivity.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
20→10 extension.src.workspace.WorkspaceFilterManager uses extension.src.settings.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in extension.src.settings.definitions.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→extension.src.settings.definitions.IFabricExtensionsSettingStorage
- Direction
- extension.src.workspace.WorkspaceFilterManager uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
20→11 extension.src.workspace.WorkspaceFilterManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace.WorkspaceFilterManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
20→16 extension.src.workspace.WorkspaceFilterManager uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceFilterManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.WorkspaceFilterManager.WorkspaceFilterManager→api.src.fabricExtension.IWorkspaceManagerextension.src.workspace.WorkspaceFilterManager.WorkspacePickItem→api.src.fabricExtension.IWorkspace
- Direction
- extension.src.workspace.WorkspaceFilterManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.WorkspaceFilterManager, while a change to extension.src.workspace.WorkspaceFilterManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceFilterManager uses a module listed above it, which is the healthy direction.
21→1 extension.src.extensionManager.FabricExtensionManager uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.extensionManager.FabricExtensionManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.extensionManager.FabricExtensionManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.extensionManager.FabricExtensionManager, while a change to extension.src.extensionManager.FabricExtensionManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.extensionManager.FabricExtensionManager uses a module listed above it, which is the healthy direction.
21→4 extension.src.extensionManager.FabricExtensionManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.extensionManager.FabricExtensionManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.extensionManager.FabricExtensionManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.extensionManager.FabricExtensionManager, while a change to extension.src.extensionManager.FabricExtensionManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.extensionManager.FabricExtensionManager uses a module listed above it, which is the healthy direction.
21→12 extension.src.extensionManager.FabricExtensionManager uses api.src.satelliteFabricExtension✕
- Connections
- 4 pairs of types, where a type in extension.src.extensionManager.FabricExtensionManager uses a type in api.src.satelliteFabricExtension.
- The types involved
extension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.satelliteFabricExtension.IArtifactHandlerextension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.satelliteFabricExtension.IFabricExtensionextension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.satelliteFabricExtension.IFabricTreeNodeProviderextension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.satelliteFabricExtension.ILocalProjectTreeNodeProvider
- Direction
- extension.src.extensionManager.FabricExtensionManager uses api.src.satelliteFabricExtension, so a change to api.src.satelliteFabricExtension can break extension.src.extensionManager.FabricExtensionManager, while a change to extension.src.extensionManager.FabricExtensionManager can't break api.src.satelliteFabricExtension.
- Position
- Below the diagonal: extension.src.extensionManager.FabricExtensionManager uses a module listed above it, which is the healthy direction.
21→16 extension.src.extensionManager.FabricExtensionManager uses api.src.fabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.extensionManager.FabricExtensionManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→api.src.fabricExtension.IFabricExtensionServiceCollection
- Direction
- extension.src.extensionManager.FabricExtensionManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.extensionManager.FabricExtensionManager, while a change to extension.src.extensionManager.FabricExtensionManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.extensionManager.FabricExtensionManager uses a module listed above it, which is the healthy direction.
21→18 extension.src.extensionManager.FabricExtensionManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.extensionManager.FabricExtensionManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.extensionManager.FabricExtensionManager.FabricExtensionManager→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.extensionManager.FabricExtensionManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.extensionManager.FabricExtensionManager, while a change to extension.src.extensionManager.FabricExtensionManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.extensionManager.FabricExtensionManager uses a module listed above it, which is the healthy direction.
22→1 extension.src.workspace.WorkspaceManager uses api.src.FabricApiClient✕
- Connections
- 4 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→api.src.FabricApiClient.IFabricApiClientextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.FabricApiClient.IApiClientResponseextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.FabricApiClient.IArtifactextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.workspace.WorkspaceManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→2 extension.src.workspace.WorkspaceManager uses extension.src.authentication.interfaces✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→extension.src.authentication.interfaces.IAccountProviderextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.workspace.WorkspaceManager uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→4 extension.src.workspace.WorkspaceManager uses util.src.logger.Logger✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→util.src.logger.Logger.ILoggerextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.WorkspaceManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→10 extension.src.workspace.WorkspaceManager uses extension.src.settings.definitions✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in extension.src.settings.definitions.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→extension.src.settings.definitions.IFabricExtensionsSettingStorageextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→extension.src.settings.definitions.IFabricExtensionsSettingStorage
- Direction
- extension.src.workspace.WorkspaceManager uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→11 extension.src.workspace.WorkspaceManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProviderextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace.WorkspaceManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→13 extension.src.workspace.WorkspaceManager uses extension.src.LocalFolderService✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→extension.src.LocalFolderService.ILocalFolderServiceextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.WorkspaceManager uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→16 extension.src.workspace.WorkspaceManager uses api.src.fabricExtension✕
- Connections
- 3 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.fabricExtension.IFolderManagerextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.fabricExtension.IWorkspaceextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.WorkspaceManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
22→18 extension.src.workspace.WorkspaceManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.WorkspaceManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.WorkspaceManager.WorkspaceManager→extension.src.apis.internal.fabricExtensionInternal.IGitOperatorextension.src.workspace.WorkspaceManager.WorkspaceManagerBase→extension.src.apis.internal.fabricExtensionInternal.IGitOperator
- Direction
- extension.src.workspace.WorkspaceManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.WorkspaceManager, while a change to extension.src.workspace.WorkspaceManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.WorkspaceManager uses a module listed above it, which is the healthy direction.
23→1 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses api.src.FabricApiClient✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.ArtifactChildNodeProviderCollection→api.src.FabricApiClient.IArtifactextension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, while a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a module listed above it, which is the healthy direction.
23→4 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.ArtifactChildNodeProviderCollection→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, while a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a module listed above it, which is the healthy direction.
23→16 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses api.src.fabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.ArtifactChildNodeProviderCollection→api.src.fabricExtension.IArtifactManager
- Direction
- extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, while a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a module listed above it, which is the healthy direction.
23→18 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.ArtifactChildNodeProviderCollection→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, while a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a module listed above it, which is the healthy direction.
23→19 extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses extension.src.workspace.DefinitionFileSystemProvider✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a type in extension.src.workspace.DefinitionFileSystemProvider.
- The types involved
extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.ArtifactChildNodeProviderCollection→extension.src.workspace.DefinitionFileSystemProvider.DefinitionFileSystemProvider
- Direction
- extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses extension.src.workspace.DefinitionFileSystemProvider, so a change to extension.src.workspace.DefinitionFileSystemProvider can break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, while a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can't break extension.src.workspace.DefinitionFileSystemProvider.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection uses a module listed above it, which is the healthy direction.
24→2 extension.src.workspace uses extension.src.authentication.interfaces✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.commands→extension.src.authentication.interfaces.IAccountProviderextension.src.workspace.viewExpansionState→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.workspace uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace, while a change to extension.src.workspace can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→4 extension.src.workspace uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.commands→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace, while a change to extension.src.workspace can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→8 extension.src.workspace uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeView→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace, while a change to extension.src.workspace can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→9 extension.src.workspace uses extension.src.CapacityManager✕
- Connections
- 1 pair of types, where a type in extension.src.workspace uses a type in extension.src.CapacityManager.
- The types involved
extension.src.workspace.commands→extension.src.CapacityManager.ICapacityManager
- Direction
- extension.src.workspace uses extension.src.CapacityManager, so a change to extension.src.CapacityManager can break extension.src.workspace, while a change to extension.src.workspace can't break extension.src.CapacityManager.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→10 extension.src.workspace uses extension.src.settings.definitions✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace uses a type in extension.src.settings.definitions.
- The types involved
extension.src.workspace.viewExpansionState→extension.src.settings.definitions.IFabricExtensionsSettingStorageextension.src.workspace.viewExpansionState→extension.src.settings.definitions.IFabricViewState
- Direction
- extension.src.workspace uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.workspace, while a change to extension.src.workspace can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→11 extension.src.workspace uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.commands→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProviderextension.src.workspace.viewExpansionState→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace, while a change to extension.src.workspace can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→20 extension.src.workspace uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.workspace uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.workspace.commands→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.workspace uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.workspace, while a change to extension.src.workspace can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
24→22 extension.src.workspace uses extension.src.workspace.WorkspaceManager✕
- Connections
- 1 pair of types, where a type in extension.src.workspace uses a type in extension.src.workspace.WorkspaceManager.
- The types involved
extension.src.workspace.commands→extension.src.workspace.WorkspaceManager.WorkspaceManagerBase
- Direction
- extension.src.workspace uses extension.src.workspace.WorkspaceManager, so a change to extension.src.workspace.WorkspaceManager can break extension.src.workspace, while a change to extension.src.workspace can't break extension.src.workspace.WorkspaceManager.
- Position
- Below the diagonal: extension.src.workspace uses a module listed above it, which is the healthy direction.
25→2 extension.src.workspace.definitions uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.definitions uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.definitions.IRootTreeNodeProvider→extension.src.authentication.interfaces.ITenantSettings
- Direction
- extension.src.workspace.definitions uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.definitions, while a change to extension.src.workspace.definitions can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.definitions uses a module listed above it, which is the healthy direction.
25→8 extension.src.workspace.definitions uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.definitions uses a type in api.src.treeView.
- The types involved
extension.src.workspace.definitions.IRootTreeNodeProvider→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.definitions uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.definitions, while a change to extension.src.workspace.definitions can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.definitions uses a module listed above it, which is the healthy direction.
25→23 extension.src.workspace.definitions uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.definitions uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.definitions.IRootTreeNodeProvider→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.definitions uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.definitions, while a change to extension.src.workspace.definitions can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.definitions uses a module listed above it, which is the healthy direction.
26→1 extension.src.workspace.mockWorkspaceManager uses api.src.FabricApiClient✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→api.src.FabricApiClient.IArtifactextension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.workspace.mockWorkspaceManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→2 extension.src.workspace.mockWorkspaceManager uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.workspace.mockWorkspaceManager uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→4 extension.src.workspace.mockWorkspaceManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.mockWorkspaceManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→10 extension.src.workspace.mockWorkspaceManager uses extension.src.settings.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in extension.src.settings.definitions.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→extension.src.settings.definitions.IFabricExtensionsSettingStorage
- Direction
- extension.src.workspace.mockWorkspaceManager uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→11 extension.src.workspace.mockWorkspaceManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace.mockWorkspaceManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→13 extension.src.workspace.mockWorkspaceManager uses extension.src.LocalFolderService✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.mockWorkspaceManager uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→18 extension.src.workspace.mockWorkspaceManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→extension.src.apis.internal.fabricExtensionInternal.IGitOperator
- Direction
- extension.src.workspace.mockWorkspaceManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
26→22 extension.src.workspace.mockWorkspaceManager uses extension.src.workspace.WorkspaceManager✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.mockWorkspaceManager uses a type in extension.src.workspace.WorkspaceManager.
- The types involved
extension.src.workspace.mockWorkspaceManager.MockWorkspaceManager→extension.src.workspace.WorkspaceManager.WorkspaceManagerBase
- Direction
- extension.src.workspace.mockWorkspaceManager uses extension.src.workspace.WorkspaceManager, so a change to extension.src.workspace.WorkspaceManager can break extension.src.workspace.mockWorkspaceManager, while a change to extension.src.workspace.mockWorkspaceManager can't break extension.src.workspace.WorkspaceManager.
- Position
- Below the diagonal: extension.src.workspace.mockWorkspaceManager uses a module listed above it, which is the healthy direction.
27→1 extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.treeNodes.ArtifactTypeTreeNode, while a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a module listed above it, which is the healthy direction.
27→8 extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.treeNodes.ArtifactTypeTreeNode, while a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a module listed above it, which is the healthy direction.
27→13 extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.LocalFolderService✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.treeNodes.ArtifactTypeTreeNode, while a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a module listed above it, which is the healthy direction.
27→18 extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.ArtifactTypeTreeNode, while a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a module listed above it, which is the healthy direction.
27→23 extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.treeNodes.ArtifactTypeTreeNode, while a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ArtifactTypeTreeNode uses a module listed above it, which is the healthy direction.
28→4 extension.src.localProject.LocalProjectTreeDataProvider uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.localProject.LocalProjectTreeDataProvider uses a type in util.src.logger.Logger.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider.LocalProjectTreeDataProvider→util.src.logger.Logger.ILogger
- Direction
- extension.src.localProject.LocalProjectTreeDataProvider uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.localProject.LocalProjectTreeDataProvider, while a change to extension.src.localProject.LocalProjectTreeDataProvider can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.localProject.LocalProjectTreeDataProvider uses a module listed above it, which is the healthy direction.
28→8 extension.src.localProject.LocalProjectTreeDataProvider uses api.src.treeView✕
- Connections
- 4 pairs of types, where a type in extension.src.localProject.LocalProjectTreeDataProvider uses a type in api.src.treeView.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider.ArtifactTypeTreeNode→api.src.treeView.FabricTreeNodeextension.src.localProject.LocalProjectTreeDataProvider.DefinitionLocalProjectTreeNodeProvider→api.src.treeView.LocalProjectTreeNodeProviderextension.src.localProject.LocalProjectTreeDataProvider.LocalProjectTreeDataProvider→api.src.treeView.FabricTreeNodeextension.src.localProject.LocalProjectTreeDataProvider.MissingExtensionLocalProjectTreeNodeProvider→api.src.treeView.LocalProjectTreeNodeProvider
- Direction
- extension.src.localProject.LocalProjectTreeDataProvider uses api.src.treeView, so a change to api.src.treeView can break extension.src.localProject.LocalProjectTreeDataProvider, while a change to extension.src.localProject.LocalProjectTreeDataProvider can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.localProject.LocalProjectTreeDataProvider uses a module listed above it, which is the healthy direction.
28→12 extension.src.localProject.LocalProjectTreeDataProvider uses api.src.satelliteFabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.localProject.LocalProjectTreeDataProvider uses a type in api.src.satelliteFabricExtension.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider.ArtifactTypeTreeNode→api.src.satelliteFabricExtension.ILocalProjectTreeNodeProvider
- Direction
- extension.src.localProject.LocalProjectTreeDataProvider uses api.src.satelliteFabricExtension, so a change to api.src.satelliteFabricExtension can break extension.src.localProject.LocalProjectTreeDataProvider, while a change to extension.src.localProject.LocalProjectTreeDataProvider can't break api.src.satelliteFabricExtension.
- Position
- Below the diagonal: extension.src.localProject.LocalProjectTreeDataProvider uses a module listed above it, which is the healthy direction.
28→18 extension.src.localProject.LocalProjectTreeDataProvider uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 3 pairs of types, where a type in extension.src.localProject.LocalProjectTreeDataProvider uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider.ArtifactTypeTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.localProject.LocalProjectTreeDataProvider.LocalProjectTreeDataProvider→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.localProject.LocalProjectTreeDataProvider.LocalProjectTreeNodeCollection→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.localProject.LocalProjectTreeDataProvider uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.localProject.LocalProjectTreeDataProvider, while a change to extension.src.localProject.LocalProjectTreeDataProvider can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.localProject.LocalProjectTreeDataProvider uses a module listed above it, which is the healthy direction.
28→27 extension.src.localProject.LocalProjectTreeDataProvider uses extension.src.workspace.treeNodes.ArtifactTypeTreeNode✕
- Connections
- 1 pair of types, where a type in extension.src.localProject.LocalProjectTreeDataProvider uses a type in extension.src.workspace.treeNodes.ArtifactTypeTreeNode.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider.LocalProjectTreeNodeCollection→extension.src.workspace.treeNodes.ArtifactTypeTreeNode.ArtifactTypeTreeNode
- Direction
- extension.src.localProject.LocalProjectTreeDataProvider uses extension.src.workspace.treeNodes.ArtifactTypeTreeNode, so a change to extension.src.workspace.treeNodes.ArtifactTypeTreeNode can break extension.src.localProject.LocalProjectTreeDataProvider, while a change to extension.src.localProject.LocalProjectTreeDataProvider can't break extension.src.workspace.treeNodes.ArtifactTypeTreeNode.
- Position
- Below the diagonal: extension.src.localProject.LocalProjectTreeDataProvider uses a module listed above it, which is the healthy direction.
29→2 extension.src.workspace.treeNodes.RootTreeNode uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→8 extension.src.workspace.treeNodes.RootTreeNode uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→13 extension.src.workspace.treeNodes.RootTreeNode uses extension.src.LocalFolderService✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→16 extension.src.workspace.treeNodes.RootTreeNode uses api.src.fabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→18 extension.src.workspace.treeNodes.RootTreeNode uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→23 extension.src.workspace.treeNodes.RootTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
29→25 extension.src.workspace.treeNodes.RootTreeNode uses extension.src.workspace.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.RootTreeNode uses a type in extension.src.workspace.definitions.
- The types involved
extension.src.workspace.treeNodes.RootTreeNode.RootTreeNode→extension.src.workspace.definitions.DisplayStyle
- Direction
- extension.src.workspace.treeNodes.RootTreeNode uses extension.src.workspace.definitions, so a change to extension.src.workspace.definitions can break extension.src.workspace.treeNodes.RootTreeNode, while a change to extension.src.workspace.treeNodes.RootTreeNode can't break extension.src.workspace.definitions.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.RootTreeNode uses a module listed above it, which is the healthy direction.
30→2 extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→extension.src.authentication.interfaces.ITenantSettings
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→8 extension.src.workspace.treeNodes.TenantTreeNode uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→13 extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.LocalFolderService✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→16 extension.src.workspace.treeNodes.TenantTreeNode uses api.src.fabricExtension✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→18 extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→23 extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
30→25 extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.workspace.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.TenantTreeNode uses a type in extension.src.workspace.definitions.
- The types involved
extension.src.workspace.treeNodes.TenantTreeNode.TenantTreeNode→extension.src.workspace.definitions.DisplayStyle
- Direction
- extension.src.workspace.treeNodes.TenantTreeNode uses extension.src.workspace.definitions, so a change to extension.src.workspace.definitions can break extension.src.workspace.treeNodes.TenantTreeNode, while a change to extension.src.workspace.treeNodes.TenantTreeNode can't break extension.src.workspace.definitions.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.TenantTreeNode uses a module listed above it, which is the healthy direction.
31→1 extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.WorkspaceTreeNode uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.treeNodes.WorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.WorkspaceTreeNode uses a module listed above it, which is the healthy direction.
31→8 extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.WorkspaceTreeNode uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.treeNodes.WorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.WorkspaceTreeNode uses a module listed above it, which is the healthy direction.
31→16 extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeNodes.WorkspaceTreeNode uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→api.src.fabricExtension.IWorkspaceextension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.treeNodes.WorkspaceTreeNode uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeNodes.WorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.WorkspaceTreeNode uses a module listed above it, which is the healthy direction.
31→18 extension.src.workspace.treeNodes.WorkspaceTreeNode uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.WorkspaceTreeNode uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.WorkspaceTreeNode uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.WorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.WorkspaceTreeNode uses a module listed above it, which is the healthy direction.
31→25 extension.src.workspace.treeNodes.WorkspaceTreeNode uses extension.src.workspace.definitions✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.WorkspaceTreeNode uses a type in extension.src.workspace.definitions.
- The types involved
extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode→extension.src.workspace.definitions.DisplayStyle
- Direction
- extension.src.workspace.treeNodes.WorkspaceTreeNode uses extension.src.workspace.definitions, so a change to extension.src.workspace.definitions can break extension.src.workspace.treeNodes.WorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can't break extension.src.workspace.definitions.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.WorkspaceTreeNode uses a module listed above it, which is the healthy direction.
32→2 extension.src.workspace.treeView uses extension.src.authentication.interfaces✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.authentication.interfaces.IAccountProviderextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.authentication.interfaces.ITenantSettings
- Direction
- extension.src.workspace.treeView uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→4 extension.src.workspace.treeView uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeView uses a type in util.src.logger.Logger.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→util.src.logger.Logger.ILogger
- Direction
- extension.src.workspace.treeView uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→8 extension.src.workspace.treeView uses api.src.treeView✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in api.src.treeView.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→api.src.treeView.FabricTreeNodeextension.src.workspace.treeView.RootTreeNodeProvider→api.src.treeView.FabricTreeNode
- Direction
- extension.src.workspace.treeView uses api.src.treeView, so a change to api.src.treeView can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→10 extension.src.workspace.treeView uses extension.src.settings.definitions✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.settings.definitions.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.settings.definitions.IFabricExtensionsSettingStorageextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.settings.definitions.IFabricExtensionsSettingStorage
- Direction
- extension.src.workspace.treeView uses extension.src.settings.definitions, so a change to extension.src.settings.definitions can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.settings.definitions.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→11 extension.src.workspace.treeView uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeView uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.workspace.treeView uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→13 extension.src.workspace.treeView uses extension.src.LocalFolderService✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.LocalFolderService.ILocalFolderServiceextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.treeView uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→16 extension.src.workspace.treeView uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→api.src.fabricExtension.IWorkspaceManagerextension.src.workspace.treeView.RootTreeNodeProvider→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.treeView uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→18 extension.src.workspace.treeView uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeView uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→20 extension.src.workspace.treeView uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeView uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.workspace.treeView uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→23 extension.src.workspace.treeView uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollectionextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.treeView uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
32→25 extension.src.workspace.treeView uses extension.src.workspace.definitions✕
- Connections
- 3 pairs of types, where a type in extension.src.workspace.treeView uses a type in extension.src.workspace.definitions.
- The types involved
extension.src.workspace.treeView.FabricWorkspaceDataProvider→extension.src.workspace.definitions.IRootTreeNodeProviderextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.workspace.definitions.DisplayStyleextension.src.workspace.treeView.RootTreeNodeProvider→extension.src.workspace.definitions.IRootTreeNodeProvider
- Direction
- extension.src.workspace.treeView uses extension.src.workspace.definitions, so a change to extension.src.workspace.definitions can break extension.src.workspace.treeView, while a change to extension.src.workspace.treeView can't break extension.src.workspace.definitions.
- Position
- Below the diagonal: extension.src.workspace.treeView uses a module listed above it, which is the healthy direction.
33→1 extension.src.artifactManager uses api.src.FabricApiClient✕
- Connections
- 9 pairs of types, where a type in extension.src.artifactManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.artifactManager.changeLocalFolderCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.commands→api.src.FabricApiClient.IArtifactextension.src.artifactManager.createArtifactCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.deleteArtifactCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.exportArtifactCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.localFolderCommandHelpers→api.src.FabricApiClient.IArtifactextension.src.artifactManager.openLocalFolderCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.readArtifactCommand→api.src.FabricApiClient.IArtifactextension.src.artifactManager.renameArtifactCommand→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.artifactManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→2 extension.src.artifactManager uses extension.src.authentication.interfaces✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager uses a type in extension.src.authentication.interfaces.
- The types involved
extension.src.artifactManager.commands.export→extension.src.authentication.interfaces.IAccountProvider
- Direction
- extension.src.artifactManager uses extension.src.authentication.interfaces, so a change to extension.src.authentication.interfaces can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.authentication.interfaces.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→4 extension.src.artifactManager uses util.src.logger.Logger✕
- Connections
- 4 pairs of types, where a type in extension.src.artifactManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.artifactManager.commands→util.src.logger.Logger.ILoggerextension.src.artifactManager.commands.export→util.src.logger.Logger.ILoggerextension.src.artifactManager.createArtifactCommand→util.src.logger.Logger.ILoggerextension.src.artifactManager.deleteArtifactCommand→util.src.logger.Logger.ILogger
- Direction
- extension.src.artifactManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→5 extension.src.artifactManager uses util.src.settings.ConfigurationProvider✕
- Connections
- 4 pairs of types, where a type in extension.src.artifactManager uses a type in util.src.settings.ConfigurationProvider.
- The types involved
extension.src.artifactManager.changeLocalFolderCommand→util.src.settings.ConfigurationProvider.IConfigurationProviderextension.src.artifactManager.commands.export→util.src.settings.ConfigurationProvider.IConfigurationProviderextension.src.artifactManager.exportArtifactCommand→util.src.settings.ConfigurationProvider.IConfigurationProviderextension.src.artifactManager.openLocalFolderCommand→util.src.settings.ConfigurationProvider.IConfigurationProvider
- Direction
- extension.src.artifactManager uses util.src.settings.ConfigurationProvider, so a change to util.src.settings.ConfigurationProvider can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break util.src.settings.ConfigurationProvider.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→6 extension.src.artifactManager uses util.src.telemetry.TelemetryActivity✕
- Connections
- 8 pairs of types, where a type in extension.src.artifactManager uses a type in util.src.telemetry.TelemetryActivity.
- The types involved
extension.src.artifactManager.changeLocalFolderCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.createArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.deleteArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.exportArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.localFolderCommandHelpers→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.openLocalFolderCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.readArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivityextension.src.artifactManager.renameArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivity
- Direction
- extension.src.artifactManager uses util.src.telemetry.TelemetryActivity, so a change to util.src.telemetry.TelemetryActivity can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break util.src.telemetry.TelemetryActivity.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→9 extension.src.artifactManager uses extension.src.CapacityManager✕
- Connections
- 2 pairs of types, where a type in extension.src.artifactManager uses a type in extension.src.CapacityManager.
- The types involved
extension.src.artifactManager.commands→extension.src.CapacityManager.ICapacityManagerextension.src.artifactManager.createArtifactCommand→extension.src.CapacityManager.ICapacityManager
- Direction
- extension.src.artifactManager uses extension.src.CapacityManager, so a change to extension.src.CapacityManager can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.CapacityManager.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→11 extension.src.artifactManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 2 pairs of types, where a type in extension.src.artifactManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.artifactManager.commands→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProviderextension.src.artifactManager.commands.export→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.artifactManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→13 extension.src.artifactManager uses extension.src.LocalFolderService✕
- Connections
- 4 pairs of types, where a type in extension.src.artifactManager uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.artifactManager.changeLocalFolderCommand→extension.src.LocalFolderService.ILocalFolderServiceextension.src.artifactManager.commands.export→extension.src.LocalFolderService.ILocalFolderServiceextension.src.artifactManager.exportArtifactCommand→extension.src.LocalFolderService.ILocalFolderServiceextension.src.artifactManager.openLocalFolderCommand→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.artifactManager uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→16 extension.src.artifactManager uses api.src.fabricExtension✕
- Connections
- 11 pairs of types, where a type in extension.src.artifactManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.artifactManager.changeLocalFolderCommand→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.commands→api.src.fabricExtension.IWorkspaceManagerextension.src.artifactManager.commands.export→api.src.fabricExtension.IWorkspaceManagerextension.src.artifactManager.createArtifactCommand→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.createArtifactCommand→api.src.fabricExtension.IWorkspaceManagerextension.src.artifactManager.deleteArtifactCommand→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.deleteArtifactCommand→api.src.fabricExtension.IWorkspaceManagerextension.src.artifactManager.exportArtifactCommand→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.localFolderCommandHelpers→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.openLocalFolderCommand→api.src.fabricExtension.IArtifactManagerextension.src.artifactManager.renameArtifactCommand→api.src.fabricExtension.IArtifactManager
- Direction
- extension.src.artifactManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→18 extension.src.artifactManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 6 pairs of types, where a type in extension.src.artifactManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.artifactManager.commands→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.artifactManager.commands→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.artifactManager.commands.export→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.artifactManager.createArtifactCommand→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.artifactManager.createArtifactCommand→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.artifactManager.readArtifactCommand→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternal
- Direction
- extension.src.artifactManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→20 extension.src.artifactManager uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 2 pairs of types, where a type in extension.src.artifactManager uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.artifactManager.commands→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManagerextension.src.artifactManager.createArtifactCommand→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.artifactManager uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
33→32 extension.src.artifactManager uses extension.src.workspace.treeView✕
- Connections
- 4 pairs of types, where a type in extension.src.artifactManager uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.artifactManager.commands→extension.src.workspace.treeView.FabricWorkspaceDataProviderextension.src.artifactManager.createArtifactCommand→extension.src.workspace.treeView.FabricWorkspaceDataProviderextension.src.artifactManager.deleteArtifactCommand→extension.src.workspace.treeView.FabricWorkspaceDataProviderextension.src.artifactManager.renameArtifactCommand→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.artifactManager uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.artifactManager, while a change to extension.src.artifactManager can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.artifactManager uses a module listed above it, which is the healthy direction.
34→1 extension.src.artifactManager.ArtifactManager uses api.src.FabricApiClient✕
- Connections
- 4 pairs of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.FabricApiClient.IApiClientResponseextension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.FabricApiClient.IArtifactextension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.FabricApiClient.IFabricApiClientextension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.FabricApiClient.IItemDefinition
- Direction
- extension.src.artifactManager.ArtifactManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→4 extension.src.artifactManager.ArtifactManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.artifactManager.ArtifactManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→11 extension.src.artifactManager.ArtifactManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.artifactManager.ArtifactManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→16 extension.src.artifactManager.ArtifactManager uses api.src.fabricExtension✕
- Connections
- 3 pairs of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.fabricExtension.IWorkspaceextension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.fabricExtension.IWorkspaceManagerextension.src.artifactManager.ArtifactManager.ArtifactManager→api.src.fabricExtension.OperationRequestType
- Direction
- extension.src.artifactManager.ArtifactManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→18 extension.src.artifactManager.ArtifactManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 2 pairs of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.artifactManager.ArtifactManager.ArtifactManager→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.artifactManager.ArtifactManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→20 extension.src.artifactManager.ArtifactManager uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.artifactManager.ArtifactManager uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
34→32 extension.src.artifactManager.ArtifactManager uses extension.src.workspace.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.ArtifactManager uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.artifactManager.ArtifactManager.ArtifactManager→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.artifactManager.ArtifactManager uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.artifactManager.ArtifactManager, while a change to extension.src.artifactManager.ArtifactManager can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.artifactManager.ArtifactManager uses a module listed above it, which is the healthy direction.
35→4 extension.src.commands.IFabricCommandManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.commands.IFabricCommandManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.commands.IFabricCommandManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→9 extension.src.commands.IFabricCommandManager uses extension.src.CapacityManager✕
- Connections
- 1 pair of types, where a type in extension.src.commands.IFabricCommandManager uses a type in extension.src.CapacityManager.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→extension.src.CapacityManager.ICapacityManager
- Direction
- extension.src.commands.IFabricCommandManager uses extension.src.CapacityManager, so a change to extension.src.CapacityManager can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break extension.src.CapacityManager.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→11 extension.src.commands.IFabricCommandManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.commands.IFabricCommandManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.commands.IFabricCommandManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→16 extension.src.commands.IFabricCommandManager uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.IFabricCommandManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→api.src.fabricExtension.IFolderManagerextension.src.commands.IFabricCommandManager.IFabricCommandManager→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.commands.IFabricCommandManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→18 extension.src.commands.IFabricCommandManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.IFabricCommandManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.commands.IFabricCommandManager.IFabricCommandManager→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.commands.IFabricCommandManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→20 extension.src.commands.IFabricCommandManager uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.commands.IFabricCommandManager uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.commands.IFabricCommandManager uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
35→32 extension.src.commands.IFabricCommandManager uses extension.src.workspace.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.commands.IFabricCommandManager uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.commands.IFabricCommandManager.IFabricCommandManager→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.commands.IFabricCommandManager uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.commands.IFabricCommandManager, while a change to extension.src.commands.IFabricCommandManager can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.commands.IFabricCommandManager uses a module listed above it, which is the healthy direction.
36→1 extension.src.localProject uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.localProject uses a type in api.src.FabricApiClient.
- The types involved
extension.src.localProject.importArtifactCommand→api.src.FabricApiClient.IItemDefinition
- Direction
- extension.src.localProject uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.localProject, while a change to extension.src.localProject can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→4 extension.src.localProject uses util.src.logger.Logger✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in util.src.logger.Logger.
- The types involved
extension.src.localProject.commands→util.src.logger.Logger.ILoggerextension.src.localProject.importArtifactCommand→util.src.logger.Logger.ILogger
- Direction
- extension.src.localProject uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.localProject, while a change to extension.src.localProject can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→6 extension.src.localProject uses util.src.telemetry.TelemetryActivity✕
- Connections
- 1 pair of types, where a type in extension.src.localProject uses a type in util.src.telemetry.TelemetryActivity.
- The types involved
extension.src.localProject.importArtifactCommand→util.src.telemetry.TelemetryActivity.TelemetryActivity
- Direction
- extension.src.localProject uses util.src.telemetry.TelemetryActivity, so a change to util.src.telemetry.TelemetryActivity can break extension.src.localProject, while a change to extension.src.localProject can't break util.src.telemetry.TelemetryActivity.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→8 extension.src.localProject uses api.src.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.localProject uses a type in api.src.treeView.
- The types involved
extension.src.localProject.LocalProjectTreeDataProvider→api.src.treeView.LocalProjectTreeNode
- Direction
- extension.src.localProject uses api.src.treeView, so a change to api.src.treeView can break extension.src.localProject, while a change to extension.src.localProject can't break api.src.treeView.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→9 extension.src.localProject uses extension.src.CapacityManager✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in extension.src.CapacityManager.
- The types involved
extension.src.localProject.commands→extension.src.CapacityManager.ICapacityManagerextension.src.localProject.importArtifactCommand→extension.src.CapacityManager.ICapacityManager
- Direction
- extension.src.localProject uses extension.src.CapacityManager, so a change to extension.src.CapacityManager can break extension.src.localProject, while a change to extension.src.localProject can't break extension.src.CapacityManager.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→11 extension.src.localProject uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.localProject.commands→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProviderextension.src.localProject.importArtifactCommand→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.localProject uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.localProject, while a change to extension.src.localProject can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→13 extension.src.localProject uses extension.src.LocalFolderService✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.localProject.commands→extension.src.LocalFolderService.ILocalFolderServiceextension.src.localProject.importArtifactCommand→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.localProject uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.localProject, while a change to extension.src.localProject can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→16 extension.src.localProject uses api.src.fabricExtension✕
- Connections
- 3 pairs of types, where a type in extension.src.localProject uses a type in api.src.fabricExtension.
- The types involved
extension.src.localProject.commands→api.src.fabricExtension.IWorkspaceManagerextension.src.localProject.importArtifactCommand→api.src.fabricExtension.IArtifactManagerextension.src.localProject.importArtifactCommand→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.localProject uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.localProject, while a change to extension.src.localProject can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→18 extension.src.localProject uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 3 pairs of types, where a type in extension.src.localProject uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.localProject.commands→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.localProject.commands→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternalextension.src.localProject.importArtifactCommand→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.localProject uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.localProject, while a change to extension.src.localProject can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→20 extension.src.localProject uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.localProject.commands→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManagerextension.src.localProject.importArtifactCommand→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.localProject uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.localProject, while a change to extension.src.localProject can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
36→32 extension.src.localProject uses extension.src.workspace.treeView✕
- Connections
- 2 pairs of types, where a type in extension.src.localProject uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.localProject.commands→extension.src.workspace.treeView.FabricWorkspaceDataProviderextension.src.localProject.importArtifactCommand→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.localProject uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.localProject, while a change to extension.src.localProject can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.localProject uses a module listed above it, which is the healthy direction.
37→1 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses api.src.FabricApiClient✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in api.src.FabricApiClient.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→api.src.FabricApiClient.IArtifact
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
37→13 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.LocalFolderService✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in extension.src.LocalFolderService.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→extension.src.LocalFolderService.ILocalFolderService
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.LocalFolderService, so a change to extension.src.LocalFolderService can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break extension.src.LocalFolderService.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
37→16 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in api.src.fabricExtension.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→api.src.fabricExtension.IWorkspaceextension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
37→18 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
37→23 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.IArtifactChildNodeProviderCollection
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection, so a change to extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break extension.src.workspace.treeNodes.childNodeProviders.ArtifactChildNodeProviderCollection.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
37→31 extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.workspace.treeNodes.WorkspaceTreeNode✕
- Connections
- 1 pair of types, where a type in extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a type in extension.src.workspace.treeNodes.WorkspaceTreeNode.
- The types involved
extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode.ListViewWorkspaceTreeNode→extension.src.workspace.treeNodes.WorkspaceTreeNode.WorkspaceTreeNode
- Direction
- extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses extension.src.workspace.treeNodes.WorkspaceTreeNode, so a change to extension.src.workspace.treeNodes.WorkspaceTreeNode can break extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode, while a change to extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode can't break extension.src.workspace.treeNodes.WorkspaceTreeNode.
- Position
- Below the diagonal: extension.src.workspace.treeNodes.ListViewWorkspaceTreeNode uses a module listed above it, which is the healthy direction.
38→1 extension.src.artifactManager.MockArtifactManager uses api.src.FabricApiClient✕
- Connections
- 3 pairs of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in api.src.FabricApiClient.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→api.src.FabricApiClient.IApiClientResponseextension.src.artifactManager.MockArtifactManager.MockArtifactManager→api.src.FabricApiClient.IArtifactextension.src.artifactManager.MockArtifactManager.MockArtifactManager→api.src.FabricApiClient.IFabricApiClient
- Direction
- extension.src.artifactManager.MockArtifactManager uses api.src.FabricApiClient, so a change to api.src.FabricApiClient can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break api.src.FabricApiClient.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→4 extension.src.artifactManager.MockArtifactManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.artifactManager.MockArtifactManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→11 extension.src.artifactManager.MockArtifactManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.artifactManager.MockArtifactManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→16 extension.src.artifactManager.MockArtifactManager uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→api.src.fabricExtension.IOpenArtifactOptionsextension.src.artifactManager.MockArtifactManager.MockArtifactManager→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.artifactManager.MockArtifactManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→18 extension.src.artifactManager.MockArtifactManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.artifactManager.MockArtifactManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→20 extension.src.artifactManager.MockArtifactManager uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.artifactManager.MockArtifactManager uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→32 extension.src.artifactManager.MockArtifactManager uses extension.src.workspace.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.artifactManager.MockArtifactManager uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
38→34 extension.src.artifactManager.MockArtifactManager uses extension.src.artifactManager.ArtifactManager✕
- Connections
- 1 pair of types, where a type in extension.src.artifactManager.MockArtifactManager uses a type in extension.src.artifactManager.ArtifactManager.
- The types involved
extension.src.artifactManager.MockArtifactManager.MockArtifactManager→extension.src.artifactManager.ArtifactManager.ArtifactManager
- Direction
- extension.src.artifactManager.MockArtifactManager uses extension.src.artifactManager.ArtifactManager, so a change to extension.src.artifactManager.ArtifactManager can break extension.src.artifactManager.MockArtifactManager, while a change to extension.src.artifactManager.MockArtifactManager can't break extension.src.artifactManager.ArtifactManager.
- Position
- Below the diagonal: extension.src.artifactManager.MockArtifactManager uses a module listed above it, which is the healthy direction.
39→6 extension.src.commands.FabricCommand uses util.src.telemetry.TelemetryActivity✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommand uses a type in util.src.telemetry.TelemetryActivity.
- The types involved
extension.src.commands.FabricCommand.FabricCommand→util.src.telemetry.TelemetryActivity.TelemetryActivity
- Direction
- extension.src.commands.FabricCommand uses util.src.telemetry.TelemetryActivity, so a change to util.src.telemetry.TelemetryActivity can break extension.src.commands.FabricCommand, while a change to extension.src.commands.FabricCommand can't break util.src.telemetry.TelemetryActivity.
- Position
- Below the diagonal: extension.src.commands.FabricCommand uses a module listed above it, which is the healthy direction.
39→35 extension.src.commands.FabricCommand uses extension.src.commands.IFabricCommandManager✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.FabricCommand uses a type in extension.src.commands.IFabricCommandManager.
- The types involved
extension.src.commands.FabricCommand.FabricCommand→extension.src.commands.IFabricCommandManager.IFabricCommandextension.src.commands.FabricCommand.FabricCommand→extension.src.commands.IFabricCommandManager.IFabricCommandManager
- Direction
- extension.src.commands.FabricCommand uses extension.src.commands.IFabricCommandManager, so a change to extension.src.commands.IFabricCommandManager can break extension.src.commands.FabricCommand, while a change to extension.src.commands.FabricCommand can't break extension.src.commands.IFabricCommandManager.
- Position
- Below the diagonal: extension.src.commands.FabricCommand uses a module listed above it, which is the healthy direction.
40→4 extension.src.commands.FabricCommandManager uses util.src.logger.Logger✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommandManager uses a type in util.src.logger.Logger.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→util.src.logger.Logger.ILogger
- Direction
- extension.src.commands.FabricCommandManager uses util.src.logger.Logger, so a change to util.src.logger.Logger can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break util.src.logger.Logger.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→9 extension.src.commands.FabricCommandManager uses extension.src.CapacityManager✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommandManager uses a type in extension.src.CapacityManager.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.CapacityManager.ICapacityManager
- Direction
- extension.src.commands.FabricCommandManager uses extension.src.CapacityManager, so a change to extension.src.CapacityManager can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break extension.src.CapacityManager.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→11 extension.src.commands.FabricCommandManager uses util.src.settings.FabricEnvironmentProvider✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommandManager uses a type in util.src.settings.FabricEnvironmentProvider.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→util.src.settings.FabricEnvironmentProvider.IFabricEnvironmentProvider
- Direction
- extension.src.commands.FabricCommandManager uses util.src.settings.FabricEnvironmentProvider, so a change to util.src.settings.FabricEnvironmentProvider can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break util.src.settings.FabricEnvironmentProvider.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→16 extension.src.commands.FabricCommandManager uses api.src.fabricExtension✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.FabricCommandManager uses a type in api.src.fabricExtension.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→api.src.fabricExtension.IFolderManagerextension.src.commands.FabricCommandManager.FabricCommandManager→api.src.fabricExtension.IWorkspaceManager
- Direction
- extension.src.commands.FabricCommandManager uses api.src.fabricExtension, so a change to api.src.fabricExtension can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break api.src.fabricExtension.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→18 extension.src.commands.FabricCommandManager uses extension.src.apis.internal.fabricExtensionInternal✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.FabricCommandManager uses a type in extension.src.apis.internal.fabricExtensionInternal.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.apis.internal.fabricExtensionInternal.IArtifactManagerInternalextension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.apis.internal.fabricExtensionInternal.IFabricExtensionManagerInternal
- Direction
- extension.src.commands.FabricCommandManager uses extension.src.apis.internal.fabricExtensionInternal, so a change to extension.src.apis.internal.fabricExtensionInternal can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break extension.src.apis.internal.fabricExtensionInternal.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→20 extension.src.commands.FabricCommandManager uses extension.src.workspace.WorkspaceFilterManager✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommandManager uses a type in extension.src.workspace.WorkspaceFilterManager.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.workspace.WorkspaceFilterManager.IWorkspaceFilterManager
- Direction
- extension.src.commands.FabricCommandManager uses extension.src.workspace.WorkspaceFilterManager, so a change to extension.src.workspace.WorkspaceFilterManager can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break extension.src.workspace.WorkspaceFilterManager.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→32 extension.src.commands.FabricCommandManager uses extension.src.workspace.treeView✕
- Connections
- 1 pair of types, where a type in extension.src.commands.FabricCommandManager uses a type in extension.src.workspace.treeView.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.workspace.treeView.FabricWorkspaceDataProvider
- Direction
- extension.src.commands.FabricCommandManager uses extension.src.workspace.treeView, so a change to extension.src.workspace.treeView can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break extension.src.workspace.treeView.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
40→35 extension.src.commands.FabricCommandManager uses extension.src.commands.IFabricCommandManager✕
- Connections
- 2 pairs of types, where a type in extension.src.commands.FabricCommandManager uses a type in extension.src.commands.IFabricCommandManager.
- The types involved
extension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.commands.IFabricCommandManager.IFabricCommandextension.src.commands.FabricCommandManager.FabricCommandManager→extension.src.commands.IFabricCommandManager.IFabricCommandManager
- Direction
- extension.src.commands.FabricCommandManager uses extension.src.commands.IFabricCommandManager, so a change to extension.src.commands.IFabricCommandManager can break extension.src.commands.FabricCommandManager, while a change to extension.src.commands.FabricCommandManager can't break extension.src.commands.IFabricCommandManager.
- Position
- Below the diagonal: extension.src.commands.FabricCommandManager uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 12 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A05:2025 — Injection | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 Assertions commented out finding(s) in Test Quality — start with importArtifactCommand.unit.test.ts; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Assertions commented out finding(s) in Test Quality — start with importArtifactCommand.unit.test.ts. | +9.3 pts | Low | Test Quality |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +8.4 pts | Medium | Dependency Hygiene |
| Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). | +2.5 pts | Low | Dependency Hygiene |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.8 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.0 pts | Medium | Deployment & Rollback |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. | +0.9 pts | Low | Project Cohesion |
| Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract. | +1.8 pts | Medium | Code Duplication |
| Swallowed exception (empty catch) | +1.7 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| extension/src/extension.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| extension/src/authentication/AccountProvider.ts | 6.6 | Mixed | Explicit Debt: TodoComment |
| extension/src/workspace/treeView.ts | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.7 | Mixed | Secrets (history): REDACTED: REDACTED |
| extension/src/localProject/importArtifactCommand.ts | 6.9 | Mixed | Cyclomatic Complexity: importArtifactCommand.importArtifactCommand (cyclomatic 22) |
| extension/src/artifactManager/createArtifactCommand.ts | 7.3 | Near-clean | Cyclomatic Complexity: createArtifactCommand.promptForArtifactTypeAndName (cyclomatic 20) |
| extension/src/LocalFolderService.ts | 7.3 | Near-clean | Cyclomatic Complexity: LocalFolderService.getLocalFolder (cyclomatic 16) |
| extension/src/web/extension.ts | 7.3 | Near-clean | Explicit Debt: TodoComment |
| extension/src/artifactManager/ArtifactManager.ts | 7.3 | Near-clean | Explicit Debt: TodoComment |
| extension/test/integration/WorkspaceArtifactManagement.integration.test.ts | 7.3 | Near-clean | Explicit Debt: TodoComment |
| extension/src/artifactManager/commands.ts | 7.4 | Near-clean | Cyclomatic Complexity: commands.registerArtifactCommands (cyclomatic 23) |
| extension/test/unit/localProject/importArtifactCommand.unit.test.ts | 7.5 | Near-clean | Test Quality: Assertions commented out: Does NOT call setLocalFolderForFabricWorkspace when forcePromptForWorkspace is true |
| extension/src/workspace/treeNodes/childNodeProviders/DefinitionFilesChildNodeProvider.ts | 7.6 | Near-clean | Cognitive Complexity: DefinitionFilesChildNodeProvider.buildTreeStructure (cognitive 31) |
| extension/src/fabric/FabricApiClient.ts | 7.8 | Near-clean | Cyclomatic Complexity: FabricApiClient.sendRequest (cyclomatic 21) |
| extension/src/utilities.ts | 7.8 | Near-clean | Cyclomatic Complexity: utilities.handleLongRunningOperation (cyclomatic 20) |
| extension/src/ui/showItemQuickPick.ts | 7.8 | Near-clean | Cyclomatic Complexity: showItemQuickPick.showItemQuickPick (cyclomatic 19) |
| extension/src/workspace/WorkspaceManager.ts | 7.8 | Near-clean | Cognitive Complexity: WorkspaceManagerBase.processAutoLogin (cognitive 19) |
| extension/src/artifactManager/commands.export.ts | 7.8 | Near-clean | Cognitive Complexity: commands.export.registerArtifactExportCommands (cognitive 19) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 69 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, 304 of 315 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.ts, .mjs, .js) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but no REDACTED in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .ts/.mjs/.js runner and not a verdict that this repository runs no tests.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts, .mjs, .js) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but no REDACTED in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .ts/.mjs/.js runner and not a verdict that this repository runs no tests.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is @wessberg/di, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 170 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was commands.registerArtifactCommands at 23.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with commands.registerArtifactCommands (cyclomatic 23), importArtifactCommand.importArtifactCommand (cyclomatic 22), FabricApiClient.sendRequest (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was importArtifactCommand.importArtifactCommand at 37.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with importArtifactCommand.importArtifactCommand (cognitive 37), utilities.handleLongRunningOperation (cognitive 33), DefinitionFilesChildNodeProvider.buildTreeStructure (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 16 together lifts Cognitive Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with commands.ts, importArtifactCommand.ts, commands.export.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with AppBackendWebviewPanel.ts. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 62 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 · Test Quality
0 skipped, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 911 tests.
What to do
- Resolve the 1 Assertions commented out finding(s) in Test Quality — start with importArtifactCommand.unit.test.ts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 No assertions finding(s) in Test Quality — start with FabricFeatureConfiguration.unit.test.ts (2), TokenAquisitionService.test.ts (2), FabricEnvironmentProvider.unit.test.ts. — One of this dimension's main actionable groups (6 warning-level).
D12 · Dependency Hygiene
6 outdated direct production npm dependency(ies) of 9 graded, 0 pinning defect(s), across 4 REDACTED (4 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 104 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 104 package(s) this repository's committed lockfile installs for a consumer — its 9 production, optional and peer dependency(ies), across 4 product REDACTED manifest(s), and everything those install in turn. Its 37 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT / SEE LICENSE IN LICENSE.md, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is extension/src/bufferUtilities.ts. Counted over 101 of the 178 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
13 deducted task-comment markers across 16728 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 13 TodoComment finding(s) in Explicit Debt — start with AccountProvider.ts (4), extension.ts (2), ArtifactManager.ts (2). — One of this dimension's main actionable groups (13 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 17 document(s) read across 4 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
0 of 6 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D22 · Internal API Consistency
0 API inconsistencies among 47 exposed members measured against a convention their peers follow.
D23 · Boundary Type-Coupling
3 domain type(s) cross context boundaries across 3 contexts; they are measured and withheld (not published, not scored). Contexts: api, extension, util.
D24 · Comment Value
91 of 1208 judged comments only repeat the code they sit on (7.5 %). 29 comment(s) in another language or script were not judged.
What to do
- Resolve the 91 redundant comment finding(s) in Comment Value — start with extension.ts (8), DefinitionFilesChildNodeProvider.ts (4), createArtifactCommand.unit.test.ts (4). — One of this dimension's main actionable groups (91 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
47 % of calls cross a namespace and 24 % go through an interface, but 53 % 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)
1 finding(s): 0 critical, 1 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 1 REDACTED 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
12 finding(s): 0 critical, 3 high, 7 medium, 2 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
D34 · Knowledge Freshness
6 of 101 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extension/src/commands/FabricCommandManager.ts. Counted over 101 of the 178 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 0 platform declaration(s) and 4 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
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
- A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. — extension/src/authentication/FakeTokenAcquisitionService.ts:9
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `getArmAccessToken` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — extension/src/authentication/FakeTokenAcquisitionService.ts:9
- `deactivate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — extension/src/extension.ts:437, extension/src/web/extension.ts:338
- `showLocalFolderQuickPick` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — extension/src/ui/showLocalFolderQuickPick.ts:8
- A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — api/src/FabricApiClient.ts:169
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 9 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/ci.yml:8
- `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:2
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `fs.statSync` in `normalCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — extension/src/fabric/MockApiClient.ts:72
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- 11 of the duplicated blocks reported below have copies in at least two of the sibling directories artifactManager, commands, internalSatellites, itemDefinition, localProject, tenant (+1 more sibling(s) not listed) under extension/src/. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — extension/src/artifactManager/commands.ts:320
- extension/src/extension.ts:101 · extension/src/web/extension.ts:88 — the two spans are one implementation copied and then locally edited — 549 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/extension.ts:101
- extension/src/artifactManager/ArtifactManager.ts:188 · extension/src/artifactManager/ArtifactManager.ts:352 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/artifactManager/ArtifactManager.ts:188
- extension/src/workspace/treeNodes/RootTreeNode.ts:18 · extension/src/workspace/treeNodes/TenantTreeNode.ts:16 — the two spans are one implementation copied and then locally edited — 172 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/workspace/treeNodes/RootTreeNode.ts:18
- extension/src/extension.ts:582 · extension/src/web/extension.ts:383 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — extension/src/extension.ts:582
- extension/src/commands/folders/CreateFolderCommand.ts:64 · extension/src/commands/folders/RenameFolderCommand.ts:45 — the two spans are one implementation copied and then locally edited — 216 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/commands/folders/CreateFolderCommand.ts:64
- extension/src/extension.ts:343 · extension/src/web/extension.ts:285 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/extension.ts:343
- extension/src/extension.ts:255 · extension/src/web/extension.ts:228 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — extension/src/extension.ts:255
- extension/webpack.config.js:28 · extension/webpack.config.js:83 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/webpack.config.js:28
- extension/src/extension.ts:437 · extension/src/web/extension.ts:338 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — extension/src/extension.ts:437
- extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:10 · extension/src/internalSatellites/database/WarehouseTreeNode.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:10
- extension/src/artifactManager/commands.export.ts:49 · extension/src/artifactManager/commands.export.ts:150 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/commands.export.ts:49
- extension/src/extension.ts:310 · extension/src/web/extension.ts:257 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/extension.ts:310
- extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:6 · extension/src/internalSatellites/database/SqlEndpointTreeNode.ts:5 · extension/src/internalSatellites/database/WarehouseTreeNode.ts:2 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:6
- extension/src/commands/folders/DeleteFolderCommand.ts:17 · extension/src/commands/folders/RenameFolderCommand.ts:17 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/commands/folders/DeleteFolderCommand.ts:17
- extension/src/extensionManager/FabricExtensionManager.ts:118 · extension/src/extensionManager/MockFabricExtensionManager.ts:103 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/extensionManager/FabricExtensionManager.ts:118
- extension/src/internalSatellites/database/copyConnectionString.ts:15 · extension/src/internalSatellites/database/openSqlExtension.ts:15 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — extension/src/internalSatellites/database/copyConnectionString.ts:15
- extension/src/workspace/treeNodes/ListViewWorkspaceTreeNode.ts:24 · extension/src/workspace/treeNodes/TreeViewWorkspaceTreeNode.ts:18 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — extension/src/workspace/treeNodes/ListViewWorkspaceTreeNode.ts:24
- extension/src/artifactManager/commands.ts:133 · extension/src/artifactManager/commands.ts:242 · extension/src/artifactManager/commands.ts:270 — all 3 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. — extension/src/artifactManager/commands.ts:133
- extension/src/artifactManager/commands.ts:320 · extension/src/localProject/commands.ts:113 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/commands.ts:320
- extension/src/commands/FabricCommand.ts:48 · util/src/FabricError.ts:243 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/commands/FabricCommand.ts:48
- extension/src/localProject/LocalProjectTreeDataProvider.ts:33 · extension/src/workspace/treeView.ts:88 — the two spans are one implementation copied and then locally edited — 155 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/localProject/LocalProjectTreeDataProvider.ts:33
- util/src/VSCodeUIBypass.ts:156 · util/src/VSCodeUIBypass.ts:201 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — util/src/VSCodeUIBypass.ts:156
- extension/src/artifactManager/commands.export.ts:133 · extension/src/artifactManager/commands.ts:320 · extension/src/localProject/commands.ts:113 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/commands.export.ts:133
- extension/src/internalSatellites/database/commands.ts:39 · extension/src/internalSatellites/database/commands.ts:54 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — extension/src/internalSatellites/database/commands.ts:39
- extension/src/internalSatellites/report/ReportArtifactHandler.ts:78 · extension/src/internalSatellites/report/ReportArtifactHandler.ts:94 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/internalSatellites/report/ReportArtifactHandler.ts:78
- util/src/testSupport.ts:15 · util/src/testSupport.ts:37 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — util/src/testSupport.ts:15
- extension/src/artifactManager/changeLocalFolderCommand.ts:138 · extension/src/artifactManager/exportArtifactCommand.ts:79 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/changeLocalFolderCommand.ts:138
- extension/src/extension.ts:238 · extension/src/web/extension.ts:213 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/extension.ts:238
- extension/src/fabric/FabricApiClient.ts:103 · extension/src/fabric/MockApiClient.ts:81 — the two spans are one implementation copied and then locally edited — 76 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/fabric/FabricApiClient.ts:103
- extension/src/DefaultArtifactHandler.ts:17 · extension/src/artifactManager/readArtifactCommand.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — extension/src/DefaultArtifactHandler.ts:17
- extension/src/artifactManager/deleteArtifactCommand.ts:81 · extension/src/artifactManager/readArtifactCommand.ts:38 · extension/src/artifactManager/renameArtifactCommand.ts:38 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — extension/src/artifactManager/deleteArtifactCommand.ts:81
- extension/src/commands/EditItemDefinitionCommand.ts:19 · extension/src/commands/folders/RenameFolderCommand.ts:17 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — extension/src/commands/EditItemDefinitionCommand.ts:19
- extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:27 · extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:80 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:27
- extension/src/workspace/treeNodes/DefinitionFolderTreeNode.ts:38 · extension/src/workspace/treeNodes/childNodeProviders/DefinitionFilesChildNodeProvider.ts:161 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — extension/src/workspace/treeNodes/DefinitionFolderTreeNode.ts:38
- util/src/settings/FabricEnvironmentProvider.ts:53 · util/src/settings/FabricEnvironmentProvider.ts:102 — the two spans are one implementation copied and then locally edited — 85 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — util/src/settings/FabricEnvironmentProvider.ts:53
- extension/src/artifactManager/renameArtifactCommand.ts:34 · extension/src/commands/folders/RenameFolderCommand.ts:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/renameArtifactCommand.ts:34
- extension/src/commands/folders/CreateFolderCommand.ts:96 · extension/src/commands/folders/RenameFolderCommand.ts:72 · extension/src/localProject/importArtifactCommand.ts:188 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/commands/folders/CreateFolderCommand.ts:96
- extension/src/extension.ts:565 · extension/src/web/extension.ts:366 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/extension.ts:565
- extension/src/artifactManager/ArtifactManager.ts:315 · extension/src/artifactManager/ArtifactManager.ts:339 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extension/src/artifactManager/ArtifactManager.ts:315
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
- api/.vscode-test.mjs:2 reaches into another package with a relative path (../extension/.vscode-test.shared.cjs) — import the package by name instead. — api/.vscode-test.mjs:2
- extension/src/extensionManager/MockFabricExtensionManager.ts:8 imports extension/test/unit/general/serviceCollection.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — extension/src/extensionManager/MockFabricExtensionManager.ts:8
- util/.vscode-test.mjs:2 reaches into another package with a relative path (../extension/.vscode-test.shared.cjs) — import the package by name instead. — util/.vscode-test.mjs:2
What to do
- Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (2 rows); move the shared test helper into a source directory production code may depend on (1 row).
R2 · Cyclomatic Complexity
- handleLongRunningOperation has cyclomatic complexity 26 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/utilities.ts:191
- (anonymous) has cyclomatic complexity 26 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/fabric/FabricApiClient.ts:71
- (anonymous) has cyclomatic complexity 23 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/test/integration/WorkspaceArtifactManagement.integration.test.ts:408
- showItemQuickPick has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/ui/showItemQuickPick.ts:36
- (top-level) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — api/src/satelliteFabricExtension.ts:4
- getLocalFolder has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/LocalFolderService.ts:111
- normalCallback has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/fabric/MockApiClient.ts:23
- showWorkspaceQuickPick has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/ui/showWorkspaceQuickPick.ts:24
- getFoldersInWorkspace has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/workspace/WorkspaceManager.ts:345
- doFabricActionInternal has cyclomatic complexity 12 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — util/src/FabricError.ts:120
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/artifactManager/commands.export.ts:81
- changeLocalFolderCommand has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/artifactManager/changeLocalFolderCommand.ts:15
- detectNotebookFormatFromDefinition has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:151
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/artifactManager/commands.ts:187
- setContextValue has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/workspace/treeNodes/artifactTreeNodeFactory.ts:61
- buildTreeStructure has cyclomatic complexity 11 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/workspace/treeNodes/childNodeProviders/DefinitionFilesChildNodeProvider.ts:62
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/localProject/importArtifactCommand.ts:102
- recordExpansionChange has cyclomatic complexity 11 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/workspace/viewExpansionState.ts:59
- promptMcpServerInstall has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/extension.ts:474
- getSession has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/authentication/TokenAcquisitionService.ts:76
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/src/artifactManager/createArtifactCommand.ts:101
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extension/test/integration/WorkspaceArtifactManagement.integration.test.ts:71
R3 · Large Files
- extension/src/extension.ts has 571 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extension/src/extension.ts:1
- api/src/fabricExtension.ts has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — api/src/fabricExtension.ts:1
- extension/src/workspace/WorkspaceManager.ts has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extension/src/workspace/WorkspaceManager.ts:1
- extension/src/artifactManager/ArtifactManager.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extension/src/artifactManager/ArtifactManager.ts: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. (×18) — extension/src/extension.ts:1, extension/src/web/extension.ts:1, extension/src/workspace/mockWorkspaceManager.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 3 file(s) (~335 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.
- Nothing imports this binding — it is safe to review for removal. (×3) — extension/src/constants.ts:33, extension/src/fabric/FabricApiClient.ts:21, extension/src/workspace/mockWorkspaceManager.ts:181
- 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. (×2) — extension/src/feedback/FeedbackTreeDataProvider.ts:44, extension/src/internalSatellites/database/commands.ts:15
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×2) — extension/src/workspace/mockTreeView.ts:13, extension/src/workspace/mockTreeView.ts:24
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
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×2) — extension/src/fabric/FabricApiClient.ts:8, extension/src/authentication/AccountProvider.ts:11
- Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — extension/src/authentication/AccountProvider.ts:12
- 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. (×9) — REDACTED:33, REDACTED:64, REDACTED:42, …
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- api/src/fabricExtension.ts → api/src/satelliteFabricExtension.ts → api/src/fabricExtension.ts (one verified cycle inside a mutually-dependent group of 3 files) — api/src/fabricExtension.ts:6
- extension/src/workspace/WorkspaceManager.ts → extension/src/workspace/treeView.ts → extension/src/workspace/treeNodes/RootTreeNode.ts → extension/src/workspace/WorkspaceManager.ts — extension/src/workspace/WorkspaceManager.ts:8
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `FabricEnvironmentProvider` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `onDidEnvironmentChangeEmitter` itself (line 150, `new vscode.EventEmitter`), which makes that instance its own. But `onDidEnvironmentChangeEmitter` is named in none of the methods the disposal search covered: `dispose` (line 143) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `vscode.EventEmitter` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this.onDidEnvironmentChangeEmitter.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree. — util/src/settings/FabricEnvironmentProvider.ts:150
- `WorkspaceManagerBase` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `_onDidChangePropertyValue` itself (line 226, `new vscode.EventEmitter`), which makes that instance its own. But `_onDidChangePropertyValue` is named in none of the methods the disposal search covered: `dispose` (line 245) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `vscode.EventEmitter` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this._onDidChangePropertyValue.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree. — extension/src/workspace/WorkspaceManager.ts:226
- `FabricWorkspaceDataProvider` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `_onDidChangeTreeData` itself (line 101, `new vscode.EventEmitter`), which makes that instance its own. But `_onDidChangeTreeData` is named in none of the methods the disposal search covered: `dispose` (line 94) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `vscode.EventEmitter` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this._onDidChangeTreeData.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree. — extension/src/workspace/treeView.ts:101
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — util/src/fabricUtilities.ts:78, util/src/fabricUtilities.ts:98, extension/src/LocalFolderService.ts:143, …
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — extension/src/itemDefinition/ItemDefinitionConflictDetector.ts:34
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- ~2.6 `!` null assertions per 1k TypeScript source lines — 50 assertion(s) across the 18979 source line(s) of the 168 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: util/src/VSCodeUIBypass.ts (24), extension/src/workspace/mockTreeView.ts (5), extension/src/artifactManager/MockArtifactManager.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71.6 | Strong | Solid. |
| Architecture | 81.4 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 97.1 | Exemplary | Strongest area. |
| Readiness | 51.1 | Adequate — gated by R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 92.1 | Exemplary | Solid. |
| Performance | 85.0 | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not 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
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not included — no test command the analyzer could start
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3279 declarations, no unit with a dominant convention).
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not measured — no test command the analyzer could start
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (4 module(s), 175 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: 170 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Assertions commented out: Does NOT call setLocalFolderForFabricWorkspace when forcePromptForWorkspace is true extension/test/unit/localProject/importArtifactCommand.unit.test.ts:597
- REDACTED
- Unlisted import '@azure/abort-controller' extension/src/fabric/FabricApiClient.ts:8
- Unlisted import '@azure/arm-resources-subscriptions' extension/src/authentication/AccountProvider.ts:11
- Import cycle (2 files) api/src/fabricExtension.ts:6
- Import cycle (3 files) extension/src/workspace/WorkspaceManager.ts:8
Serious — 168 finding(s)
- No test reaches this file extension/src/extension.ts:1
- No test reaches this file extension/src/web/extension.ts:1
- No test reaches this file extension/src/workspace/mockWorkspaceManager.ts:1
- No test reaches this file extension/src/artifactManager/MockArtifactManager.ts:1
- No test reaches this file extension/src/git/GitOperator.ts:1
- No test reaches this file extension/src/workspace/commands.ts:1
- No test reaches this file extension/src/fabric/MockApiClient.ts:1
- No test reaches this file extension/src/commands/FabricCommandManager.ts:1
- No test reaches this file extension/src/workspace/mockTreeView.ts:1
- No test reaches this file extension/src/feedback/FeedbackTreeDataProvider.ts:1
- No test reaches this file extension/src/tenant/commands.ts:1
- No test reaches this file extension/src/shared/initFabricVirtualDocProvider.ts:1
- No test reaches this file extension/src/workspace/DefinitionFileCodeLensProvider.ts:1
- No test reaches this file extension/src/web/WebLocalFolderManager.ts:1
- No test reaches this file extension/src/shared/expansionStateHandler.ts:1
- No test reaches this file extension/src/Lazy.ts:1
- No test reaches this file extension/src/shared/tenantChangeHandler.ts:1
- No test reaches this file extension/src/web/WebGitOperator.ts:1
- TodoComment extension/test/integration/WorkspaceArtifactManagement.integration.test.ts:307
- TodoComment extension/src/ExtensionUriHandler.ts:54
- TodoComment extension/src/extension.ts:183
- TodoComment extension/src/web/extension.ts:167
- TodoComment extension/src/workspace/treeView.ts:264
- TodoComment extension/src/ui/showCreateWorkspaceWizard.ts:49
- TodoComment extension/src/commands/FabricCommandManager.ts:103
- TodoComment extension/src/authentication/AccountProvider.ts:211
- TodoComment extension/src/authentication/AccountProvider.ts:226
- TodoComment extension/src/authentication/AccountProvider.ts:233
- TodoComment extension/src/authentication/AccountProvider.ts:244
- TodoComment extension/src/artifactManager/ArtifactManager.ts:95
- TodoComment extension/src/artifactManager/ArtifactManager.ts:415
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) util/src/fabricUtilities.ts:78
- Swallowed exception (empty catch) util/src/fabricUtilities.ts:98
- Swallowed exception (empty catch) extension/src/LocalFolderService.ts:143
- Swallowed exception (empty catch) extension/src/workspace/treeNodes/artifactTreeNodeFactory.ts:53
- Swallowed exception (empty catch) extension/src/shared/expansionStateHandler.ts:30
- Swallowed exception (empty catch) extension/src/itemDefinition/ItemDefinitionConflictDetector.ts:47
- Swallowed exception (empty catch) extension/src/authentication/AccountProvider.ts:210
- No assertions: should fire onDidEnvironmentChange when environment setting changes util/test/unit/settings/FabricEnvironmentProvider.unit.test.ts:706
- No assertions: fires when ShowFolders configuration changes extension/test/unit/settings/FabricFeatureConfiguration.unit.test.ts:50
- No assertions: fires when EditItemDefinitions configuration changes extension/test/unit/settings/FabricFeatureConfiguration.unit.test.ts:92
- No assertions: Satellite contributions are initially empty extension/test/unit/general/FabricExtensionManager.unit.test.ts:16
- No assertions: microsoft session changes extension/test/unit/authentication/TokenAquisitionService.test.ts:53
- No assertions: microsoft-sovereign-cloud session changes extension/test/unit/authentication/TokenAquisitionService.test.ts:58
- FunctionTooLong: commands.registerArtifactCommands extension/src/artifactManager/commands.ts:43
- FunctionTooLong: importArtifactCommand.importArtifactCommand extension/src/localProject/importArtifactCommand.ts:19
- FunctionTooLong: commands.export.registerArtifactExportCommands extension/src/artifactManager/commands.export.ts:35
- Duplicated block (11 lines × 2 locations) extension/src/DefaultArtifactHandler.ts:17
- Duplicated block (11 lines × 2 locations) extension/src/commands/EditItemDefinitionCommand.ts:19
- Duplicated block (11 lines × 2 locations) extension/src/workspace/treeNodes/DefinitionFolderTreeNode.ts:38
- Boundary violation [package:relative-cross-package] api/.vscode-test.mjs:2
- Boundary violation [package:test-suite-dependency] extension/src/extensionManager/MockFabricExtensionManager.ts:8
- Boundary violation [package:relative-cross-package] util/.vscode-test.mjs:2
- Owned disposable field is never released util/src/settings/FabricEnvironmentProvider.ts:150
- Owned disposable field is never released extension/src/workspace/WorkspaceManager.ts:226
- Owned disposable field is never released extension/src/workspace/treeView.ts:101
- Fake-async — async method never awaits extension/src/extension.ts:437
- Fake-async — async method never awaits extension/src/web/extension.ts:338
- Duplicated block (21 lines × 2 locations) extension/src/artifactManager/commands.export.ts:49
- Duplicated block (21 lines × 2 locations) extension/src/extension.ts:310
- Duplicated block (19 lines × 2 locations) extension/src/commands/folders/DeleteFolderCommand.ts:17
- Duplicated block (19 lines × 2 locations) extension/src/internalSatellites/database/copyConnectionString.ts:15
- Duplicated block (16 lines × 2 locations) extension/src/artifactManager/commands.ts:320
- Duplicated block (16 lines × 2 locations) extension/src/commands/FabricCommand.ts:48
- Duplicated block (13 lines × 2 locations) extension/src/internalSatellites/report/ReportArtifactHandler.ts:78
- Duplicated block (13 lines × 2 locations) util/src/testSupport.ts:15
- Duplicated block (12 lines × 2 locations) extension/src/artifactManager/changeLocalFolderCommand.ts:138
- Duplicated block (12 lines × 2 locations) extension/src/extension.ts:238
- Duplicated block with local edits (11 matched lines × 2 locations) extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:27
- Duplicated block with local edits (11 matched lines × 2 locations) util/src/settings/FabricEnvironmentProvider.ts:53
- Duplicated block (10 lines × 2 locations) extension/src/artifactManager/renameArtifactCommand.ts:34
- Duplicated block (10 lines × 2 locations) extension/src/extension.ts:565
- commands.registerArtifactCommands (cyclomatic 23) extension/src/artifactManager/commands.ts:43
- importArtifactCommand.importArtifactCommand (cyclomatic 22) extension/src/localProject/importArtifactCommand.ts:19
- FabricApiClient.sendRequest (cyclomatic 21) extension/src/fabric/FabricApiClient.ts:69
- utilities.handleLongRunningOperation (cyclomatic 20) extension/src/utilities.ts:191
- createArtifactCommand.promptForArtifactTypeAndName (cyclomatic 20) extension/src/artifactManager/createArtifactCommand.ts:37
- showItemQuickPick.showItemQuickPick (cyclomatic 19) extension/src/ui/showItemQuickPick.ts:36
- LocalFolderService.getLocalFolder (cyclomatic 16) extension/src/LocalFolderService.ts:111
- Deprecated: glob REDACTED:64
- importArtifactCommand.importArtifactCommand (cognitive 37) extension/src/localProject/importArtifactCommand.ts:19
- utilities.handleLongRunningOperation (cognitive 33) extension/src/utilities.ts:191
- DefinitionFilesChildNodeProvider.buildTreeStructure (cognitive 31) extension/src/workspace/treeNodes/childNodeProviders/DefinitionFilesChildNodeProvider.ts:62
- FabricWorkspaceDataProvider.getChildren (cognitive 29) extension/src/workspace/treeView.ts:130
- createArtifactCommand.promptForArtifactTypeAndName (cognitive 27) extension/src/artifactManager/createArtifactCommand.ts:37
- LocalFolderService.getLocalFolder (cognitive 25) extension/src/LocalFolderService.ts:111
- commands.registerArtifactCommands (cognitive 25) extension/src/artifactManager/commands.ts:43
- FabricApiClient.sendRequest (cognitive 25) extension/src/fabric/FabricApiClient.ts:69
- showWorkspaceQuickPick.showWorkspaceQuickPick (cognitive 22) extension/src/ui/showWorkspaceQuickPick.ts:24
- MockApiClient.normalCallback (cognitive 20) extension/src/fabric/MockApiClient.ts:23
- showItemQuickPick.showItemQuickPick (cognitive 20) extension/src/ui/showItemQuickPick.ts:36
- WorkspaceManagerBase.processAutoLogin (cognitive 19) extension/src/workspace/WorkspaceManager.ts:170
- commands.export.registerArtifactExportCommands (cognitive 19) extension/src/artifactManager/commands.export.ts:35
- FabricError.doFabricActionInternal (cognitive 18) util/src/FabricError.ts:120
- WorkspaceManagerBase.getFoldersInWorkspace (cognitive 17) extension/src/workspace/WorkspaceManager.ts:345
- FabricVsCodeExtension.promptMcpServerInstall (cognitive 17) extension/src/extension.ts:474
- MethodTooLong: AppBackendWebviewPanel.getHtmlContent extension/src/internalSatellites/appBackend/AppBackendWebviewPanel.ts:127
- Unfinished stub — throws a "not implemented" error extension/src/authentication/FakeTokenAcquisitionService.ts:9
- Unfinished stub — throws a "not implemented" exception extension/src/authentication/FakeTokenAcquisitionService.ts:9
- Hollow method — returns a constant without doing the work extension/src/ui/showLocalFolderQuickPick.ts:8
- Sync-over-async blocking extension/src/fabric/MockApiClient.ts:72
- Duplication concentrated across 7 sibling directories (11 clone groups) extension/src/artifactManager/commands.ts:320
- Duplicated block with local edits (79 matched lines × 2 locations) extension/src/extension.ts:101
- Duplicated block with local edits (58 matched lines × 2 locations) extension/src/artifactManager/ArtifactManager.ts:188
- Duplicated block with local edits (44 matched lines × 2 locations) extension/src/workspace/treeNodes/RootTreeNode.ts:18
- Duplicated block (39 lines × 2 locations) extension/src/extension.ts:582
- Duplicated block with local edits (38 matched lines × 2 locations) extension/src/commands/folders/CreateFolderCommand.ts:64
- Duplicated block (36 lines × 2 locations) extension/src/extension.ts:343
- Duplicated block (35 lines × 2 locations) extension/src/extension.ts:255
- Duplicated block (34 lines × 2 locations) extension/webpack.config.js:28
- Duplicated block (31 lines × 2 locations) extension/src/extension.ts:437
- Duplicated block (22 lines × 2 locations) extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:10
- Duplicated block (21 lines × 3 locations) extension/src/internalSatellites/database/SqlDatabaseTreeNode.ts:6
- Duplicated block with local edits (19 matched lines × 2 locations) extension/src/extensionManager/FabricExtensionManager.ts:118
- Duplicated block (18 lines × 2 locations) extension/src/workspace/treeNodes/ListViewWorkspaceTreeNode.ts:24
- Duplicated block (16 lines × 3 locations) extension/src/artifactManager/commands.ts:133
- Duplicated block with local edits (16 matched lines × 2 locations) extension/src/localProject/LocalProjectTreeDataProvider.ts:33
- Duplicated block (15 lines × 2 locations) util/src/VSCodeUIBypass.ts:156
- Duplicated block (14 lines × 3 locations) extension/src/artifactManager/commands.export.ts:133
- Duplicated block (14 lines × 2 locations) extension/src/internalSatellites/database/commands.ts:39
- Duplicated block with local edits (12 matched lines × 2 locations) extension/src/fabric/FabricApiClient.ts:103
- Duplicated block (11 lines × 3 locations) extension/src/artifactManager/deleteArtifactCommand.ts:81
- Duplicated block (10 lines × 3 locations) extension/src/commands/folders/CreateFolderCommand.ts:96
- Duplicated block (9 lines × 2 locations) extension/src/artifactManager/ArtifactManager.ts:315
- Complex function handleLongRunningOperation (cyclomatic 26, cognitive 38) extension/src/utilities.ts:191
- Complex function (anonymous) (cyclomatic 26, cognitive 30) extension/src/fabric/FabricApiClient.ts:71
- Complex function (anonymous) (cyclomatic 23, cognitive 23) extension/test/integration/WorkspaceArtifactManagement.integration.test.ts:408
- Complex function showItemQuickPick (cyclomatic 19, cognitive 20) extension/src/ui/showItemQuickPick.ts:36
- Complex function (top-level) (cyclomatic 19, cognitive 18) api/src/satelliteFabricExtension.ts:4
- Complex function getLocalFolder (cyclomatic 18, cognitive 27) extension/src/LocalFolderService.ts:111
- Complex function normalCallback (cyclomatic 18, cognitive 23) extension/src/fabric/MockApiClient.ts:23
- Complex function showWorkspaceQuickPick (cyclomatic 15, cognitive 22) extension/src/ui/showWorkspaceQuickPick.ts:24
- Complex function getFoldersInWorkspace (cyclomatic 14, cognitive 19) extension/src/workspace/WorkspaceManager.ts:345
- Complex function doFabricActionInternal (cyclomatic 12, cognitive 21) util/src/FabricError.ts:120
- Complex function (anonymous) (cyclomatic 12, cognitive 16) extension/src/artifactManager/commands.export.ts:81
- Complex function changeLocalFolderCommand (cyclomatic 12, cognitive 15) extension/src/artifactManager/changeLocalFolderCommand.ts:15
- Complex function detectNotebookFormatFromDefinition (cyclomatic 12, cognitive 14) extension/src/internalSatellites/notebook/NotebookArtifactHandler.ts:151
- Complex function (anonymous) (cyclomatic 12, cognitive 13) extension/src/artifactManager/commands.ts:187
- Complex function setContextValue (cyclomatic 12, cognitive 11) extension/src/workspace/treeNodes/artifactTreeNodeFactory.ts:61
- Complex function buildTreeStructure (cyclomatic 11, cognitive 31) extension/src/workspace/treeNodes/childNodeProviders/DefinitionFilesChildNodeProvider.ts:62
- Complex function (anonymous) (cyclomatic 11, cognitive 20) extension/src/localProject/importArtifactCommand.ts:102
- Complex function recordExpansionChange (cyclomatic 11, cognitive 18) extension/src/workspace/viewExpansionState.ts:59
- Complex function promptMcpServerInstall (cyclomatic 11, cognitive 17) extension/src/extension.ts:474
- Complex function getSession (cyclomatic 11, cognitive 12) extension/src/authentication/TokenAcquisitionService.ts:76
- Complex function (anonymous) (cyclomatic 11, cognitive 11) extension/src/artifactManager/createArtifactCommand.ts:101
- Complex function (anonymous) (cyclomatic 11, cognitive 10) extension/test/integration/WorkspaceArtifactManagement.integration.test.ts:71
- extension/src/extension.ts: 571 lines of code extension/src/extension.ts:1
- api/src/fabricExtension.ts: 531 lines of code api/src/fabricExtension.ts:1
- extension/src/workspace/WorkspaceManager.ts: 508 lines of code extension/src/workspace/WorkspaceManager.ts:1
- extension/src/artifactManager/ArtifactManager.ts: 481 lines of code extension/src/artifactManager/ArtifactManager.ts:1
- Unlisted import '@azure/core-auth' extension/src/authentication/AccountProvider.ts:12
- Unused dependency '@vscode/test-electron' REDACTED:33
- Unused dependency 'glob' REDACTED:64
- Unused dependency 'madge' REDACTED:42
- Unused dependency 'minimatch' REDACTED:43
- Unused dependency 'nerdbank-gitversioning' REDACTED:48
- Unused dependency 'shx' REDACTED:50
- Unused dependency 'ts-patch' REDACTED:54
- Unused dependency 'tsc-watch' REDACTED:55
- Unused dependency 'web-tree-sitter' REDACTED:65
- Swallowed exception (caught, then discarded) extension/src/itemDefinition/ItemDefinitionConflictDetector.ts:34
Minor — 128 finding(s)
- redundant comment extension/src/LocalFolderService.ts:99
- redundant comment extension/src/artifactManager/changeLocalFolderCommand.ts:110
- redundant comment extension/src/artifactManager/createArtifactCommand.ts:68
- redundant comment extension/src/artifactManager/deleteArtifactCommand.ts:109
- redundant comment extension/src/artifactManager/exportArtifactCommand.ts:23
- redundant comment extension/src/artifactManager/localFolderCommandHelpers.ts:374
- redundant comment extension/src/artifactManager/localFolderCommandHelpers.ts:381
- redundant comment extension/src/commands/folders/CreateFolderCommand.ts:61
- redundant comment extension/src/commands/folders/DeleteFolderCommand.ts:42
- redundant comment extension/src/commands/folders/RenameFolderCommand.ts:42
- redundant comment extension/src/extension.ts:206
- redundant comment extension/src/extension.ts:233
- redundant comment extension/src/extension.ts:598
- redundant comment extension/src/extension.ts:619
- redundant comment extension/src/localProject/importArtifactCommand.ts:54
- redundant comment extension/src/web/extension.ts:185
- redundant comment extension/src/web/extension.ts:211
- redundant comment extension/src/web/extension.ts:399
- redundant comment extension/src/web/extension.ts:420
- redundant comment extension/src/workspace/DefinitionFileEditorDecorator.ts:22
- redundant comment extension/src/workspace/DefinitionFileEditorDecorator.ts:29
- redundant comment extension/src/workspace/DefinitionFileEditorDecorator.ts:36
- redundant comment extension/src/workspace/DefinitionFileSystemProvider.ts:196
- redundant comment extension/src/workspace/DefinitionFileSystemProvider.ts:223
- redundant comment extension/src/workspace/WorkspaceFilterManager.ts:232
- Orphaned file extension/src/commands/FabricCommandManager.ts:1
- Orphaned file extension/src/commands/FabricCommand.ts:1
- Orphaned file extension/src/commands/folders/CreateFolderCommand.ts:1
- Orphaned file extension/src/ExtensionUriHandler.ts:1
- Orphaned file extension/src/commands/folders/DeleteFolderCommand.ts:1
- Orphaned file extension/src/commands/folders/RenameFolderCommand.ts:1
- Deprecated: glob REDACTED:2280
- Deprecated: inflight REDACTED:6374
- Deprecated: glob REDACTED:7867
- Deprecated: glob REDACTED:10595
- Silent fallback default in catch extension/src/workspace/treeNodes/TenantTreeNode.ts:71
- Silent fallback default in catch extension/src/workspace/treeNodes/RootTreeNode.ts:88
- Silent fallback default in catch extension/src/internalSatellites/appBackend/AppBackendWebviewPanel.ts:96
- REDACTED
- REDACTED
- Unused private field 'depth' extension/src/workspace/mockTreeView.ts:13
- Unused private field 'depth' extension/src/workspace/mockTreeView.ts:24
- Duplicated predicate extension/src/internalSatellites/database/commands.ts:41
- Duplicated predicate extension/src/artifactManager/ArtifactManager.ts:505
- Outdated (npm): glob REDACTED:64
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example extension/README.md:1
- Projects may be oversized for their cohesion REDACTED:1
- Scattered collaborators
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Blanket warning suppression api/src/FabricApiClient.ts:169
- No SAST .github/workflows/ci.yml:8
- Dependabot does not watch npm .github/dependabot.yml:2
- No release approval gate
- Unused export 'FABRIC_API_VERSION' extension/src/constants.ts:33
- Unused export 'ClusterUrisByTenantLocation' extension/src/fabric/FabricApiClient.ts:21
- Unused export 'MockMemento' extension/src/workspace/mockWorkspaceManager.ts:181
- Unused module-local declaration 'ViewIssuesQuickPickItem' extension/src/feedback/FeedbackTreeDataProvider.ts:44
- Unused module-local declaration 'TelemetryEventNames' extension/src/internalSatellites/database/commands.ts:15
- Null assertions (`!`) override strict null checking
Minor — 8 finding(s)
- Outdated (npm): @azure/core-rest-pipeline
- Outdated (npm): @microsoft/vscode-azext-azureauth
- Outdated (npm): @vscode/extension-telemetry
- Outdated (npm): fs-extra
- Outdated (npm): web-tree-sitter
- doc comments repeat the names api/src/satelliteFabricExtension.ts:348
- doc comments repeat the names util/src/telemetry/TelemetryActivity.ts:23
- doc comments repeat the names extension/src/ILocalFolderManager.ts:26
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e531a9a2ecb5433685ac4647db36e6dc/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e531a9a2ecb5433685ac4647db36e6dc/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 12 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | 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. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |