Executive summary
VictoriaMetrics/VictoriaLogs falls short of our standard for production, in part because it has controls that only work with a mouse. It scores 53.4 out of 100 and is rated Adequate, and 34 of its 90 critical findings are security problems.
Accessibility, at 39.7, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 7.2 points. Making the controls keyboard-usable comes next, worth about 7.0 points. Raising Accessibility to 70 would lift the score to about 63.7.
Forty controls can't be used without a mouse. Twenty-three settings leave the servers or containers unsafe, and nine pipeline steps run downloads nobody checks. Making the controls work with a keyboard, correcting the unsafe settings and checking each download against a checksum would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The eight buttons or links with no name need a name, even when they only show an icon.
The product code is 92,906 lines, about €140,000 to rebuild.
If Accessibility rose from 39.7 to 70, the lowest score rated Strong, the score would rise from 53.4 to about 63.7.
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €48,000 to €240,000, for 793 to 2,515 hours of work, about 1.0 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 92,906 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 components.Chart.BarHitsChart.types | 2 components.ExtraFilters.types | 3 components.Table.TableHeaderCell.TableHeaderMenu.TableHeaderMenu | 4 components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude | 5 components.Views.LiveTailingView.useLiveTailingLogs | 6 pages.QueryPage.HitsPanel.hooks.useHitsChartAlert | 7 state.query.reducer | 8 types | 9 types.uplot | 10 utils.nativeFileSystemAdapter.FileSystemHandle | 11 utils.storage.types | 12 utils.time.vmDate | 13 api.types | 14 components.Chart.BarHitsChart.BarHitsChart | 15 components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot | 16 components.Chart.BarHitsChart.hooks.useBarHitsOptions | 17 components.ExtraFilters.utils | 18 components.Table | 19 hooks.uplot.usePlotScale | 20 hooks.useGroupByFields | 21 pages.OverviewPage.hooks.useFetchFieldNames | 22 pages.QueryPage.hooks.useFetchHits | 23 pages.QueryPage.hooks.useFetchLogs | 24 state.common.reducer | 25 utils.nativeFileSystemAdapter.FileSystemFileHandle | 26 utils.time | 27 components.Chart.BarHitsChart.hooks | 28 components.Table.hooks | 29 components.Views.TableView.hooks | 30 hooks | 31 hooks.uplot | 32 pages.QueryPage.hooks | 33 pages.QueryPage.hooks.useQueryPageController | 34 pages.QueryPage.utils | 35 pages.StreamContext.hooks.useFetchStreamContext | 36 state.overview | 37 utils | 38 utils.nativeFileSystemAdapter | 39 pages.StreamContext | 40 pages.StreamContext.hooks |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 components.Chart.BarHitsChart.types | ||||||||||||||||||||||||||||||||||||||||
| 2 components.ExtraFilters.types | ||||||||||||||||||||||||||||||||||||||||
| 3 components.Table.TableHeaderCell.TableHeaderMenu.TableHeaderMenu | ||||||||||||||||||||||||||||||||||||||||
| 4 components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude | ||||||||||||||||||||||||||||||||||||||||
| 5 components.Views.LiveTailingView.useLiveTailingLogs | ||||||||||||||||||||||||||||||||||||||||
| 6 pages.QueryPage.HitsPanel.hooks.useHitsChartAlert | ||||||||||||||||||||||||||||||||||||||||
| 7 state.query.reducer | ||||||||||||||||||||||||||||||||||||||||
| 8 types | ||||||||||||||||||||||||||||||||||||||||
| 9 types.uplot | ||||||||||||||||||||||||||||||||||||||||
| 10 utils.nativeFileSystemAdapter.FileSystemHandle | ||||||||||||||||||||||||||||||||||||||||
| 11 utils.storage.types | ||||||||||||||||||||||||||||||||||||||||
| 12 utils.time.vmDate | ||||||||||||||||||||||||||||||||||||||||
| 13 api.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 components.Chart.BarHitsChart.BarHitsChart | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 components.Chart.BarHitsChart.hooks.useBarHitsOptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 components.ExtraFilters.utils | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 components.Table | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 hooks.uplot.usePlotScale | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 hooks.useGroupByFields | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 pages.OverviewPage.hooks.useFetchFieldNames | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 pages.QueryPage.hooks.useFetchHits | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 pages.QueryPage.hooks.useFetchLogs | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 state.common.reducer | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 utils.nativeFileSystemAdapter.FileSystemFileHandle | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 utils.time | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 components.Chart.BarHitsChart.hooks | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 components.Table.hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 components.Views.TableView.hooks | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 hooks | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 hooks.uplot | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 pages.QueryPage.hooks | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 pages.QueryPage.hooks.useQueryPageController | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 pages.QueryPage.utils | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 pages.StreamContext.hooks.useFetchStreamContext | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 state.overview | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 utils | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 38 utils.nativeFileSystemAdapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 pages.StreamContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 pages.StreamContext.hooks | 2 |
13→9 api.types uses types.uplot✕
- Connections
- 1 pair of types, where a type in api.types uses a type in types.uplot.
- The types involved
app.vmui.packages.vmui.src.api.types.LegendLogHits→app.vmui.packages.vmui.src.types.uplot.Stroke
- Direction
- api.types uses types.uplot, so a change to types.uplot can break api.types, while a change to api.types can't break types.uplot.
- Position
- Below the diagonal: api.types uses a module listed above it, which is the healthy direction.
14→6 components.Chart.BarHitsChart.BarHitsChart uses pages.QueryPage.HitsPanel.hooks.useHitsChartAlert✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.BarHitsChart uses a type in pages.QueryPage.HitsPanel.hooks.useHitsChartAlert.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.BarHitsChart.Props→app.vmui.packages.vmui.src.pages.QueryPage.HitsPanel.hooks.useHitsChartAlert.HitsChartAlert
- Direction
- components.Chart.BarHitsChart.BarHitsChart uses pages.QueryPage.HitsPanel.hooks.useHitsChartAlert, so a change to pages.QueryPage.HitsPanel.hooks.useHitsChartAlert can break components.Chart.BarHitsChart.BarHitsChart, while a change to components.Chart.BarHitsChart.BarHitsChart can't break pages.QueryPage.HitsPanel.hooks.useHitsChartAlert.
- Position
- Below the diagonal: components.Chart.BarHitsChart.BarHitsChart uses a module listed above it, which is the healthy direction.
14→8 components.Chart.BarHitsChart.BarHitsChart uses types✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.BarHitsChart uses a type in types.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.BarHitsChart.Props→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- components.Chart.BarHitsChart.BarHitsChart uses types, so a change to types can break components.Chart.BarHitsChart.BarHitsChart, while a change to components.Chart.BarHitsChart.BarHitsChart can't break types.
- Position
- Below the diagonal: components.Chart.BarHitsChart.BarHitsChart uses a module listed above it, which is the healthy direction.
15→1 components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses components.Chart.BarHitsChart.types✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses a type in components.Chart.BarHitsChart.types.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot.Props→app.vmui.packages.vmui.src.components.Chart.BarHitsChart.types.GraphOptions
- Direction
- components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses components.Chart.BarHitsChart.types, so a change to components.Chart.BarHitsChart.types can break components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot, while a change to components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot can't break components.Chart.BarHitsChart.types.
- Position
- Below the diagonal: components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses a module listed above it, which is the healthy direction.
15→8 components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses types✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses a type in types.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot.Props→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses types, so a change to types can break components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot, while a change to components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot can't break types.
- Position
- Below the diagonal: components.Chart.BarHitsChart.BarHitsPlot.BarHitsPlot uses a module listed above it, which is the healthy direction.
16→1 components.Chart.BarHitsChart.hooks.useBarHitsOptions uses components.Chart.BarHitsChart.types✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.hooks.useBarHitsOptions uses a type in components.Chart.BarHitsChart.types.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.hooks.useBarHitsOptions.UseGetBarHitsOptionsArgs→app.vmui.packages.vmui.src.components.Chart.BarHitsChart.types.GraphOptions
- Direction
- components.Chart.BarHitsChart.hooks.useBarHitsOptions uses components.Chart.BarHitsChart.types, so a change to components.Chart.BarHitsChart.types can break components.Chart.BarHitsChart.hooks.useBarHitsOptions, while a change to components.Chart.BarHitsChart.hooks.useBarHitsOptions can't break components.Chart.BarHitsChart.types.
- Position
- Below the diagonal: components.Chart.BarHitsChart.hooks.useBarHitsOptions uses a module listed above it, which is the healthy direction.
17→2 components.ExtraFilters.utils uses components.ExtraFilters.types✕
- Connections
- 2 pairs of types, where a type in components.ExtraFilters.utils uses a type in components.ExtraFilters.types.
- The types involved
app.vmui.packages.vmui.src.components.ExtraFilters.utils.buildExprFromExtraFilters→app.vmui.packages.vmui.src.components.ExtraFilters.types.ExtraFilterapp.vmui.packages.vmui.src.components.ExtraFilters.utils.isStreamFilter→app.vmui.packages.vmui.src.components.ExtraFilters.types.ExtraFilter
- Direction
- components.ExtraFilters.utils uses components.ExtraFilters.types, so a change to components.ExtraFilters.types can break components.ExtraFilters.utils, while a change to components.ExtraFilters.utils can't break components.ExtraFilters.types.
- Position
- Below the diagonal: components.ExtraFilters.utils uses a module listed above it, which is the healthy direction.
18→8 components.Table uses types✕
- Connections
- 1 pair of types, where a type in components.Table uses a type in types.
- The types involved
app.vmui.packages.vmui.src.components.Table.helpers→app.vmui.packages.vmui.src.types.OrderDir
- Direction
- components.Table uses types, so a change to types can break components.Table, while a change to components.Table can't break types.
- Position
- Below the diagonal: components.Table uses a module listed above it, which is the healthy direction.
19→8 hooks.uplot.usePlotScale uses types✕
- Connections
- 1 pair of types, where a type in hooks.uplot.usePlotScale uses a type in types.
- The types involved
app.vmui.packages.vmui.src.hooks.uplot.usePlotScale.PlotScaleHook→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- hooks.uplot.usePlotScale uses types, so a change to types can break hooks.uplot.usePlotScale, while a change to hooks.uplot.usePlotScale can't break types.
- Position
- Below the diagonal: hooks.uplot.usePlotScale uses a module listed above it, which is the healthy direction.
20→8 hooks.useGroupByFields uses types✕
- Connections
- 1 pair of types, where a type in hooks.useGroupByFields uses a type in types.
- The types involved
app.vmui.packages.vmui.src.hooks.useGroupByFields.Options→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- hooks.useGroupByFields uses types, so a change to types can break hooks.useGroupByFields, while a change to hooks.useGroupByFields can't break types.
- Position
- Below the diagonal: hooks.useGroupByFields uses a module listed above it, which is the healthy direction.
21→8 pages.OverviewPage.hooks.useFetchFieldNames uses types✕
- Connections
- 1 pair of types, where a type in pages.OverviewPage.hooks.useFetchFieldNames uses a type in types.
- The types involved
app.vmui.packages.vmui.src.pages.OverviewPage.hooks.useFetchFieldNames.FetchOptions→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- pages.OverviewPage.hooks.useFetchFieldNames uses types, so a change to types can break pages.OverviewPage.hooks.useFetchFieldNames, while a change to pages.OverviewPage.hooks.useFetchFieldNames can't break types.
- Position
- Below the diagonal: pages.OverviewPage.hooks.useFetchFieldNames uses a module listed above it, which is the healthy direction.
22→1 pages.QueryPage.hooks.useFetchHits uses components.Chart.BarHitsChart.types✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks.useFetchHits uses a type in components.Chart.BarHitsChart.types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsParams→app.vmui.packages.vmui.src.components.Chart.BarHitsChart.types.GRAPH_QUERY_MODE
- Direction
- pages.QueryPage.hooks.useFetchHits uses components.Chart.BarHitsChart.types, so a change to components.Chart.BarHitsChart.types can break pages.QueryPage.hooks.useFetchHits, while a change to pages.QueryPage.hooks.useFetchHits can't break components.Chart.BarHitsChart.types.
- Position
- Below the diagonal: pages.QueryPage.hooks.useFetchHits uses a module listed above it, which is the healthy direction.
22→8 pages.QueryPage.hooks.useFetchHits uses types✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks.useFetchHits uses a type in types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsParams→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- pages.QueryPage.hooks.useFetchHits uses types, so a change to types can break pages.QueryPage.hooks.useFetchHits, while a change to pages.QueryPage.hooks.useFetchHits can't break types.
- Position
- Below the diagonal: pages.QueryPage.hooks.useFetchHits uses a module listed above it, which is the healthy direction.
23→8 pages.QueryPage.hooks.useFetchLogs uses types✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks.useFetchLogs uses a type in types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchLogs.FetchLogsParams→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- pages.QueryPage.hooks.useFetchLogs uses types, so a change to types can break pages.QueryPage.hooks.useFetchLogs, while a change to pages.QueryPage.hooks.useFetchLogs can't break types.
- Position
- Below the diagonal: pages.QueryPage.hooks.useFetchLogs uses a module listed above it, which is the healthy direction.
24→8 state.common.reducer uses types✕
- Connections
- 2 pairs of types, where a type in state.common.reducer uses a type in types.
- The types involved
app.vmui.packages.vmui.src.state.common.reducer.AppState→app.vmui.packages.vmui.src.types.AppConfigapp.vmui.packages.vmui.src.state.common.reducer.AppState→app.vmui.packages.vmui.src.types.Theme
- Direction
- state.common.reducer uses types, so a change to types can break state.common.reducer, while a change to state.common.reducer can't break types.
- Position
- Below the diagonal: state.common.reducer uses a module listed above it, which is the healthy direction.
25→10 utils.nativeFileSystemAdapter.FileSystemFileHandle uses utils.nativeFileSystemAdapter.FileSystemHandle✕
- Connections
- 1 pair of types, where a type in utils.nativeFileSystemAdapter.FileSystemFileHandle uses a type in utils.nativeFileSystemAdapter.FileSystemHandle.
- The types involved
app.vmui.packages.vmui.src.utils.nativeFileSystemAdapter.FileSystemFileHandle.FileSystemFileHandle→app.vmui.packages.vmui.src.utils.nativeFileSystemAdapter.FileSystemHandle.FileSystemHandle
- Direction
- utils.nativeFileSystemAdapter.FileSystemFileHandle uses utils.nativeFileSystemAdapter.FileSystemHandle, so a change to utils.nativeFileSystemAdapter.FileSystemHandle can break utils.nativeFileSystemAdapter.FileSystemFileHandle, while a change to utils.nativeFileSystemAdapter.FileSystemFileHandle can't break utils.nativeFileSystemAdapter.FileSystemHandle.
- Position
- Below the diagonal: utils.nativeFileSystemAdapter.FileSystemFileHandle uses a module listed above it, which is the healthy direction.
26→8 utils.time uses types✕
- Connections
- 4 pairs of types, where a type in utils.time uses a type in types.
- The types involved
app.vmui.packages.vmui.src.utils.time.convert→app.vmui.packages.vmui.src.types.TimeParamsapp.vmui.packages.vmui.src.utils.time.convert→app.vmui.packages.vmui.src.types.TimePeriodapp.vmui.packages.vmui.src.utils.time.duration→app.vmui.packages.vmui.src.types.TimePeriodapp.vmui.packages.vmui.src.utils.time.relative→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- utils.time uses types, so a change to types can break utils.time, while a change to utils.time can't break types.
- Position
- Below the diagonal: utils.time uses a module listed above it, which is the healthy direction.
26→12 utils.time uses utils.time.vmDate✕
- Connections
- 1 pair of types, where a type in utils.time uses a type in utils.time.vmDate.
- The types involved
app.vmui.packages.vmui.src.utils.time.vmDate→app.vmui.packages.vmui.src.utils.time.vmDate.VmDateInput
- Direction
- utils.time uses utils.time.vmDate, so a change to utils.time.vmDate can break utils.time, while a change to utils.time can't break utils.time.vmDate.
- Position
- Below the diagonal: utils.time uses a module listed above it, which is the healthy direction.
27→13 components.Chart.BarHitsChart.hooks uses api.types✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.hooks uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.hooks.useBarHitsOptions→app.vmui.packages.vmui.src.api.types.LogHits
- Direction
- components.Chart.BarHitsChart.hooks uses api.types, so a change to api.types can break components.Chart.BarHitsChart.hooks, while a change to components.Chart.BarHitsChart.hooks can't break api.types.
- Position
- Below the diagonal: components.Chart.BarHitsChart.hooks uses a module listed above it, which is the healthy direction.
27→16 components.Chart.BarHitsChart.hooks uses components.Chart.BarHitsChart.hooks.useBarHitsOptions✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.hooks uses a type in components.Chart.BarHitsChart.hooks.useBarHitsOptions.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.hooks.useBarHitsOptions→app.vmui.packages.vmui.src.components.Chart.BarHitsChart.hooks.useBarHitsOptions.UseGetBarHitsOptionsArgs
- Direction
- components.Chart.BarHitsChart.hooks uses components.Chart.BarHitsChart.hooks.useBarHitsOptions, so a change to components.Chart.BarHitsChart.hooks.useBarHitsOptions can break components.Chart.BarHitsChart.hooks, while a change to components.Chart.BarHitsChart.hooks can't break components.Chart.BarHitsChart.hooks.useBarHitsOptions.
- Position
- Below the diagonal: components.Chart.BarHitsChart.hooks uses a module listed above it, which is the healthy direction.
27→20 components.Chart.BarHitsChart.hooks uses hooks.useGroupByFields✕
- Connections
- 1 pair of types, where a type in components.Chart.BarHitsChart.hooks uses a type in hooks.useGroupByFields.
- The types involved
app.vmui.packages.vmui.src.components.Chart.BarHitsChart.hooks.useBarClickHooks→app.vmui.packages.vmui.src.hooks.useGroupByFields.Options
- Direction
- components.Chart.BarHitsChart.hooks uses hooks.useGroupByFields, so a change to hooks.useGroupByFields can break components.Chart.BarHitsChart.hooks, while a change to components.Chart.BarHitsChart.hooks can't break hooks.useGroupByFields.
- Position
- Below the diagonal: components.Chart.BarHitsChart.hooks uses a module listed above it, which is the healthy direction.
28→20 components.Table.hooks uses hooks.useGroupByFields✕
- Connections
- 1 pair of types, where a type in components.Table.hooks uses a type in hooks.useGroupByFields.
- The types involved
app.vmui.packages.vmui.src.components.Table.hooks.useDragColumn→app.vmui.packages.vmui.src.hooks.useGroupByFields.Options
- Direction
- components.Table.hooks uses hooks.useGroupByFields, so a change to hooks.useGroupByFields can break components.Table.hooks, while a change to components.Table.hooks can't break hooks.useGroupByFields.
- Position
- Below the diagonal: components.Table.hooks uses a module listed above it, which is the healthy direction.
29→13 components.Views.TableView.hooks uses api.types✕
- Connections
- 1 pair of types, where a type in components.Views.TableView.hooks uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.components.Views.TableView.hooks.useTableLogsColumns→app.vmui.packages.vmui.src.api.types.Logs
- Direction
- components.Views.TableView.hooks uses api.types, so a change to api.types can break components.Views.TableView.hooks, while a change to components.Views.TableView.hooks can't break api.types.
- Position
- Below the diagonal: components.Views.TableView.hooks uses a module listed above it, which is the healthy direction.
29→20 components.Views.TableView.hooks uses hooks.useGroupByFields✕
- Connections
- 2 pairs of types, where a type in components.Views.TableView.hooks uses a type in hooks.useGroupByFields.
- The types involved
app.vmui.packages.vmui.src.components.Views.TableView.hooks.useTableLogsColumns→app.vmui.packages.vmui.src.hooks.useGroupByFields.Optionsapp.vmui.packages.vmui.src.components.Views.TableView.hooks.useTableLogsPaginate→app.vmui.packages.vmui.src.hooks.useGroupByFields.Options
- Direction
- components.Views.TableView.hooks uses hooks.useGroupByFields, so a change to hooks.useGroupByFields can break components.Views.TableView.hooks, while a change to components.Views.TableView.hooks can't break hooks.useGroupByFields.
- Position
- Below the diagonal: components.Views.TableView.hooks uses a module listed above it, which is the healthy direction.
30→11 hooks uses utils.storage.types✕
- Connections
- 1 pair of types, where a type in hooks uses a type in utils.storage.types.
- The types involved
app.vmui.packages.vmui.src.hooks.useLocalStorageBoolean→app.vmui.packages.vmui.src.utils.storage.types.StorageKeys
- Direction
- hooks uses utils.storage.types, so a change to utils.storage.types can break hooks, while a change to hooks can't break utils.storage.types.
- Position
- Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
30→20 hooks uses hooks.useGroupByFields✕
- Connections
- 2 pairs of types, where a type in hooks uses a type in hooks.useGroupByFields.
- The types involved
app.vmui.packages.vmui.src.hooks.useDragResize→app.vmui.packages.vmui.src.hooks.useGroupByFields.Optionsapp.vmui.packages.vmui.src.hooks.useGroupByFields→app.vmui.packages.vmui.src.hooks.useGroupByFields.Options
- Direction
- hooks uses hooks.useGroupByFields, so a change to hooks.useGroupByFields can break hooks, while a change to hooks can't break hooks.useGroupByFields.
- Position
- Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
31→19 hooks.uplot uses hooks.uplot.usePlotScale✕
- Connections
- 1 pair of types, where a type in hooks.uplot uses a type in hooks.uplot.usePlotScale.
- The types involved
app.vmui.packages.vmui.src.hooks.uplot.usePlotScale→app.vmui.packages.vmui.src.hooks.uplot.usePlotScale.PlotScaleHook
- Direction
- hooks.uplot uses hooks.uplot.usePlotScale, so a change to hooks.uplot.usePlotScale can break hooks.uplot, while a change to hooks.uplot can't break hooks.uplot.usePlotScale.
- Position
- Below the diagonal: hooks.uplot uses a module listed above it, which is the healthy direction.
32→8 pages.QueryPage.hooks uses types✕
- Connections
- 2 pairs of types, where a type in pages.QueryPage.hooks uses a type in types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useTimePeriod→app.vmui.packages.vmui.src.types.NavigateOptionsapp.vmui.packages.vmui.src.pages.QueryPage.hooks.useTimePeriod→app.vmui.packages.vmui.src.types.TimePeriod
- Direction
- pages.QueryPage.hooks uses types, so a change to types can break pages.QueryPage.hooks, while a change to pages.QueryPage.hooks can't break types.
- Position
- Below the diagonal: pages.QueryPage.hooks uses a module listed above it, which is the healthy direction.
32→13 pages.QueryPage.hooks uses api.types✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits→app.vmui.packages.vmui.src.api.types.LogHits
- Direction
- pages.QueryPage.hooks uses api.types, so a change to api.types can break pages.QueryPage.hooks, while a change to pages.QueryPage.hooks can't break api.types.
- Position
- Below the diagonal: pages.QueryPage.hooks uses a module listed above it, which is the healthy direction.
32→22 pages.QueryPage.hooks uses pages.QueryPage.hooks.useFetchHits✕
- Connections
- 3 pairs of types, where a type in pages.QueryPage.hooks uses a type in pages.QueryPage.hooks.useFetchHits.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsParamsapp.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsResultapp.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.OptionsParams
- Direction
- pages.QueryPage.hooks uses pages.QueryPage.hooks.useFetchHits, so a change to pages.QueryPage.hooks.useFetchHits can break pages.QueryPage.hooks, while a change to pages.QueryPage.hooks can't break pages.QueryPage.hooks.useFetchHits.
- Position
- Below the diagonal: pages.QueryPage.hooks uses a module listed above it, which is the healthy direction.
32→23 pages.QueryPage.hooks uses pages.QueryPage.hooks.useFetchLogs✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks uses a type in pages.QueryPage.hooks.useFetchLogs.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchLogs→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchLogs.FetchLogsParams
- Direction
- pages.QueryPage.hooks uses pages.QueryPage.hooks.useFetchLogs, so a change to pages.QueryPage.hooks.useFetchLogs can break pages.QueryPage.hooks, while a change to pages.QueryPage.hooks can't break pages.QueryPage.hooks.useFetchLogs.
- Position
- Below the diagonal: pages.QueryPage.hooks uses a module listed above it, which is the healthy direction.
33→8 pages.QueryPage.hooks.useQueryPageController uses types✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks.useQueryPageController uses a type in types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useQueryPageController.utils→app.vmui.packages.vmui.src.types.TimeParams
- Direction
- pages.QueryPage.hooks.useQueryPageController uses types, so a change to types can break pages.QueryPage.hooks.useQueryPageController, while a change to pages.QueryPage.hooks.useQueryPageController can't break types.
- Position
- Below the diagonal: pages.QueryPage.hooks.useQueryPageController uses a module listed above it, which is the healthy direction.
33→22 pages.QueryPage.hooks.useQueryPageController uses pages.QueryPage.hooks.useFetchHits✕
- Connections
- 3 pairs of types, where a type in pages.QueryPage.hooks.useQueryPageController uses a type in pages.QueryPage.hooks.useFetchHits.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useQueryPageController.useQueryPageController→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsResultapp.vmui.packages.vmui.src.pages.QueryPage.hooks.useQueryPageController.utils→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsParamsapp.vmui.packages.vmui.src.pages.QueryPage.hooks.useQueryPageController.utils→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsResult
- Direction
- pages.QueryPage.hooks.useQueryPageController uses pages.QueryPage.hooks.useFetchHits, so a change to pages.QueryPage.hooks.useFetchHits can break pages.QueryPage.hooks.useQueryPageController, while a change to pages.QueryPage.hooks.useQueryPageController can't break pages.QueryPage.hooks.useFetchHits.
- Position
- Below the diagonal: pages.QueryPage.hooks.useQueryPageController uses a module listed above it, which is the healthy direction.
33→23 pages.QueryPage.hooks.useQueryPageController uses pages.QueryPage.hooks.useFetchLogs✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.hooks.useQueryPageController uses a type in pages.QueryPage.hooks.useFetchLogs.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.hooks.useQueryPageController.utils→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchLogs.FetchLogsParams
- Direction
- pages.QueryPage.hooks.useQueryPageController uses pages.QueryPage.hooks.useFetchLogs, so a change to pages.QueryPage.hooks.useFetchLogs can break pages.QueryPage.hooks.useQueryPageController, while a change to pages.QueryPage.hooks.useQueryPageController can't break pages.QueryPage.hooks.useFetchLogs.
- Position
- Below the diagonal: pages.QueryPage.hooks.useQueryPageController uses a module listed above it, which is the healthy direction.
34→13 pages.QueryPage.utils uses api.types✕
- Connections
- 2 pairs of types, where a type in pages.QueryPage.utils uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.utils.fetchHitsIterative→app.vmui.packages.vmui.src.api.types.LogHitsapp.vmui.packages.vmui.src.pages.QueryPage.utils.processHits→app.vmui.packages.vmui.src.api.types.LogHits
- Direction
- pages.QueryPage.utils uses api.types, so a change to api.types can break pages.QueryPage.utils, while a change to pages.QueryPage.utils can't break api.types.
- Position
- Below the diagonal: pages.QueryPage.utils uses a module listed above it, which is the healthy direction.
34→22 pages.QueryPage.utils uses pages.QueryPage.hooks.useFetchHits✕
- Connections
- 1 pair of types, where a type in pages.QueryPage.utils uses a type in pages.QueryPage.hooks.useFetchHits.
- The types involved
app.vmui.packages.vmui.src.pages.QueryPage.utils.buildHitsRequest→app.vmui.packages.vmui.src.pages.QueryPage.hooks.useFetchHits.FetchHitsParams
- Direction
- pages.QueryPage.utils uses pages.QueryPage.hooks.useFetchHits, so a change to pages.QueryPage.hooks.useFetchHits can break pages.QueryPage.utils, while a change to pages.QueryPage.utils can't break pages.QueryPage.hooks.useFetchHits.
- Position
- Below the diagonal: pages.QueryPage.utils uses a module listed above it, which is the healthy direction.
35→13 pages.StreamContext.hooks.useFetchStreamContext uses api.types✕
- Connections
- 2 pairs of types, where a type in pages.StreamContext.hooks.useFetchStreamContext uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext.FetchParams→app.vmui.packages.vmui.src.api.types.Logsapp.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext.FetchSideParams→app.vmui.packages.vmui.src.api.types.Logs
- Direction
- pages.StreamContext.hooks.useFetchStreamContext uses api.types, so a change to api.types can break pages.StreamContext.hooks.useFetchStreamContext, while a change to pages.StreamContext.hooks.useFetchStreamContext can't break api.types.
- Position
- Below the diagonal: pages.StreamContext.hooks.useFetchStreamContext uses a module listed above it, which is the healthy direction.
36→24 state.overview uses state.common.reducer✕
- Connections
- 2 pairs of types, where a type in state.overview uses a type in state.common.reducer.
- The types involved
app.vmui.packages.vmui.src.state.overview.OverviewStateContext→app.vmui.packages.vmui.src.state.common.reducer.Actionapp.vmui.packages.vmui.src.state.overview.reducer→app.vmui.packages.vmui.src.state.common.reducer.Action
- Direction
- state.overview uses state.common.reducer, so a change to state.common.reducer can break state.overview, while a change to state.overview can't break state.common.reducer.
- Position
- Below the diagonal: state.overview uses a module listed above it, which is the healthy direction.
37→4 utils uses components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude✕
- Connections
- 1 pair of types, where a type in utils uses a type in components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude.
- The types involved
app.vmui.packages.vmui.src.utils.combine-components→app.vmui.packages.vmui.src.components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude.Props
- Direction
- utils uses components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude, so a change to components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude can break utils, while a change to utils can't break components.Views.GroupView.GroupLogsFieldRowMenu.FieldFilterExclude.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
37→8 utils uses types✕
- Connections
- 3 pairs of types, where a type in utils uses a type in types.
- The types involved
app.vmui.packages.vmui.src.utils.intervals→app.vmui.packages.vmui.src.types.TimeParamsapp.vmui.packages.vmui.src.utils.logs→app.vmui.packages.vmui.src.types.TimeParamsapp.vmui.packages.vmui.src.utils.theme→app.vmui.packages.vmui.src.types.Theme
- Direction
- utils uses types, so a change to types can break utils, while a change to utils can't break types.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
37→13 utils uses api.types✕
- Connections
- 3 pairs of types, where a type in utils uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.utils.logLevel→app.vmui.packages.vmui.src.api.types.Logsapp.vmui.packages.vmui.src.utils.logs→app.vmui.packages.vmui.src.api.types.Logsapp.vmui.packages.vmui.src.utils.metric→app.vmui.packages.vmui.src.api.types.MetricBase
- Direction
- utils uses api.types, so a change to api.types can break utils, while a change to utils can't break api.types.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→25 utils.nativeFileSystemAdapter uses utils.nativeFileSystemAdapter.FileSystemFileHandle✕
- Connections
- 1 pair of types, where a type in utils.nativeFileSystemAdapter uses a type in utils.nativeFileSystemAdapter.FileSystemFileHandle.
- The types involved
app.vmui.packages.vmui.src.utils.nativeFileSystemAdapter.showSaveFilePicker→app.vmui.packages.vmui.src.utils.nativeFileSystemAdapter.FileSystemFileHandle.FileSystemFileHandle
- Direction
- utils.nativeFileSystemAdapter uses utils.nativeFileSystemAdapter.FileSystemFileHandle, so a change to utils.nativeFileSystemAdapter.FileSystemFileHandle can break utils.nativeFileSystemAdapter, while a change to utils.nativeFileSystemAdapter can't break utils.nativeFileSystemAdapter.FileSystemFileHandle.
- Position
- Below the diagonal: utils.nativeFileSystemAdapter uses a module listed above it, which is the healthy direction.
39→13 pages.StreamContext uses api.types✕
- Connections
- 1 pair of types, where a type in pages.StreamContext uses a type in api.types.
- The types involved
app.vmui.packages.vmui.src.pages.StreamContext.helpers→app.vmui.packages.vmui.src.api.types.Logs
- Direction
- pages.StreamContext uses api.types, so a change to api.types can break pages.StreamContext, while a change to pages.StreamContext can't break api.types.
- Position
- Below the diagonal: pages.StreamContext uses a module listed above it, which is the healthy direction.
39→35 pages.StreamContext uses pages.StreamContext.hooks.useFetchStreamContext✕
- Connections
- 1 pair of types, where a type in pages.StreamContext uses a type in pages.StreamContext.hooks.useFetchStreamContext.
- The types involved
app.vmui.packages.vmui.src.pages.StreamContext.helpers→app.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext.Direction
- Direction
- pages.StreamContext uses pages.StreamContext.hooks.useFetchStreamContext, so a change to pages.StreamContext.hooks.useFetchStreamContext can break pages.StreamContext, while a change to pages.StreamContext can't break pages.StreamContext.hooks.useFetchStreamContext.
- Position
- Below the diagonal: pages.StreamContext uses a module listed above it, which is the healthy direction.
40→35 pages.StreamContext.hooks uses pages.StreamContext.hooks.useFetchStreamContext✕
- Connections
- 2 pairs of types, where a type in pages.StreamContext.hooks uses a type in pages.StreamContext.hooks.useFetchStreamContext.
- The types involved
app.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext→app.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext.FetchParamsapp.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext→app.vmui.packages.vmui.src.pages.StreamContext.hooks.useFetchStreamContext.FetchSideParams
- Direction
- pages.StreamContext.hooks uses pages.StreamContext.hooks.useFetchStreamContext, so a change to pages.StreamContext.hooks.useFetchStreamContext can break pages.StreamContext.hooks, while a change to pages.StreamContext.hooks can't break pages.StreamContext.hooks.useFetchStreamContext.
- Position
- Below the diagonal: pages.StreamContext.hooks uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 111 | High / Critical |
| A02:2025 — Security Misconfiguration | 96 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +7.2 pts | Medium | Visual & motion safety |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +7.0 pts | Medium | Keyboard semantics |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +3.2 pts | Medium | Forms & labels |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.2 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +1.0 pts | Low | ADR Quality |
| Resolve the 5 redundant comment finding(s) in Comment Value — start with useDropzone.ts, useFieldFilter.ts, ansiParser.test.ts. | +0.7 pts | Low | Comment Value |
| Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). | +0.7 pts | Low | Documentation Quality |
| Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail. | +1.4 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 64 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, 611 of 622 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
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.go) had no cyclomatic complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.go) had no cognitive complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.go) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load. Duplication in .ts, .tsx is measured by R10 Code Duplication and is not part of this gap.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 432 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 211 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability not scored — the JavaScript/TypeScript suite (vitest via `npm ci --ignore-scripts` in app/vmui/packages/vmui/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D14 License Compliance — 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 repository declares a Go module (go.mod/go.sum), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (14870 line(s) across the 90-day window), but no complexity could be computed for .go, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (go.mod), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/vlselect/vmui/assets/index-DNKuoEMC.js`, `app/vlselect/vmui/assets/vendor-CgUtxMLZ.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC4 Keyboard semantics — 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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
- AC6 Visual & motion safety — 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. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
- 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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — vlogs Pulling vmsingle Pulling du-exporter Pulling cadvisor Pulling grafana Pulling node-exporter Pulling cadvisor Error Get "https://gcr.io/v2/": Forbidden grafana Error context canceled vlogs Error context canceled node-exporter Error context canceled du-exporter Error context canceled vmsingle Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the earlier `compose pull` step reported: du-exporter Pulling cadvisor Pulling grafana Pulling node-exporter Pulling vmsingle Pulling vlogs Pulling cadvisor Error Get "https://gcr.io/v2/": Forbidden du-exporter Error context canceled vmsingle Error context canceled vlogs Error context canceled node-exporter Error context canceled grafana Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — 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, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Go, Python is most of its product and is not read 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.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Go, Python is most of its product and is not read 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.
- 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.
- R4 Test Coverage — 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. 177 further occurrence(s) are not listed individually; the score already reflects all 217.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X26 Unsynchronised callback handoff — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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
- 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.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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.
- 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.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
D5 · Coupling
3 production modules (npm+Go), 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 5 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 432 tests. Measured on the JavaScript/TypeScript suite only — at least 211 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
0 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org 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, not a registry one. Known CVEs in this module graph are D30's question, read from go.mod and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 160 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 160 package(s) this repository's committed lockfile installs for a consumer — its 13 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 24 `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. Third-party code that ships WITHOUT a manifest entry was read too: 1 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 2 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Go module (go.mod/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D16 · Bus Factor
44 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 315 of the 655 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
D17 · Explicit Debt
6 deducted task-comment markers across 92906 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with REDACTED, pipe_unpack.go, pipe_unpack_syslog.go. — One of this dimension's main actionable groups (6 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 74 document(s) read across 9 unit(s).
What to do
- Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
10 of 254 judged comments only repeat the code they sit on (3.9 %). 16 comment(s) in another language or script were not judged.
What to do
- Resolve the 5 redundant comment finding(s) in Comment Value — start with useDropzone.ts, useFieldFilter.ts, ansiParser.test.ts. — One of this dimension's main actionable groups (5 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Go, 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 package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
141 finding(s): 0 critical, 11 high, 13 medium, 117 low. semgrep hit a parse error in 3 file(s) — `app/vlselect/vmui/assets/index-DNKuoEMC.js`, `app/vlselect/vmui/assets/vendor-CgUtxMLZ.js`, `app/vmui/packages/vmui/src/components/ExtraFilters/hooks/useExtraFilters.test.tsx` (line 16, line 26, line 36, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
96 finding(s): 0 critical, 23 high, 66 medium, 7 low.
What to do
- Resolve the 66 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (21), REDACTED (12), REDACTED (11). — One of this dimension's main actionable groups (66 warning-level).
- Resolve the 23 High IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (7), REDACTED (3). — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 recommendation-level).
D34 · Knowledge Freshness
86 of 315 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/logstorage/block_header.go. Counted over 315 of the 655 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 85 Orphaned file finding(s) in Knowledge Freshness — start with block_stream_reader.go, block_data.go, filter_range.go. — One of this dimension's main actionable groups (85 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with block_header.go. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: BarHitsChart.tsx↔QueryPage.tsx 62%; GroupLogs.tsx↔QueryPageBody.tsx 61%; HitsPanel.tsx↔useFetchHits.ts 60%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with BarHitsChart.tsx, GroupLogs.tsx, QueryPage.tsx. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with useFetchHits.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/ServerConfigurator/ServerConfigurator.tsx:78, app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/LogsQueryEditorAutocomplete.tsx:41
- This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×5) — app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryExamples/QueryExamplesModal.tsx:70, app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:181, app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:292, …
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×6) — app/vmui/packages/vmui/src/components/ExtraFilters/ExtraFiltersPanel/ExtraFiltersPanelItem.tsx:54, app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:38, app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:44, …
- This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — app/vmui/packages/vmui/src/components/Main/DatePicker/DateTimeInput/DateTimeInput.tsx:66, app/vmui/packages/vmui/src/components/Main/Toggle/Toggle.tsx:50
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — app/vmui/packages/vmui/src/components/Main/Pagination/Pagination.tsx:72, app/vmui/packages/vmui/src/components/Main/Pagination/Pagination.tsx:93
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioGroup.tsx:26
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. — app/vmui/packages/vmui/src/components/Main/Select/Select.tsx:151
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — app/vlselect/vmui/index.html:2, app/vmui/packages/vmui/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×38) — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/BarHitsLegendItem.tsx:79, app/vmui/packages/vmui/src/components/Chart/BarHitsChart/LegendHitsMenu/LegendHitsMenuRow.tsx:71, app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/GlobalSettings.tsx:75, …
- The repo's own CSS styles .vm-link with `cursor: pointer`, so this <p> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — app/vmui/packages/vmui/src/components/Configurators/LogsLimitController/LimitConfirmModal.tsx:63
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:221
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `*` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — app/vmui/packages/vmui/src/styles/reset.scss:42, app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- `.vm-menu-burger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:12, app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- `.vm-snackbar` moves (`animation: vm-slide-snackbar 150ms cubic-bezier(0.280, 0.840, 0.420, 1.1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/styles/core.scss:59
- `.vm-list-item_multiselect svg` moves (`animation: vm-scale 150ms cubic-bezier(0.280, 0.840, 0.420, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/styles/components/list.scss:41
- `.vm-header-sidebar-button` moves (`transition: left 350ms $sidebar-transition`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/layouts/Header/SidebarNav/style.scss:20
- `.vm-header-sidebar-menu` moves (`transition: transform 300ms $sidebar-transition`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/layouts/Header/SidebarNav/style.scss:43
- `.vm-header-nav-item svg` moves (`transition: transform 200ms ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/layouts/Header/HeaderNav/style.scss:52
- `.vm-group-logs-section-keys__pair` moves (`transition: background-color 0.3s ease-in, transform 0.1s ease-in, opacity 0.3s ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Views/GroupView/style.scss:114
- `.vm-group-logs-row-content__arrow` moves (`transition: transform 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Views/GroupView/style.scss:220
- `.vm-table__expand-btn` moves (`transition: transform 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Table/style.scss:26
- `.vm-table-settings-section-list-row` moves (`transition: transform 50ms linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Table/TableSettings/style.scss:152
- `.vm-table-sort-button` moves (`transition: transform .2s ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableSortButton/style.scss:9
- `.vm-tooltip` moves (`animation: vm-scale 150ms cubic-bezier(0.280, 0.840, 0.420, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Tooltip/style.scss:16
- `.vm-toggles-group__highlight` moves (`transition: left 200ms cubic-bezier(0.280, 0.840, 0.420, 1), border-radius 200ms linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Toggle/style.scss:65
- `.vm-tabs__indicator` moves (`transition: width 200ms ease, left 300ms cubic-bezier(0.280, 0.840, 0.420, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Tabs/style.scss:52
- `.vm-switch-track__thumb` moves (`transition: right 200ms ease-out, left 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Switch/style.scss:73
- `.vm-select-input__icon` moves (`transition: transform 200ms ease-in, opacity 200ms ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Select/style.scss:92
- `.vm-radio-group-option__input:after` moves (`transition: transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/RadioGroup/style.scss:50
- `.vm-popper_open` moves (`animation: vm-slider 100ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Popper/style.scss:19
- `.vm-menu-burger:after` moves (`transition: transform 140ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:26
- `.vm-menu-burger span:before` moves (`animation-name: topLineBurger`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:63
- `.vm-menu-burger span:after` moves (`animation-name: bottomLineBurger`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:67
- `.vm-menu-burger span` moves (`transition: transform 0.3s ease, border-color 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:40
- `.vm-menu-burger_opened span:before` moves (`animation-name: topLineCross`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:77
- `.vm-menu-burger_opened span:after` moves (`animation-name: bottomLineCross`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:81
- `.vm-line-loader__line` moves (`animation: slide 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/LineLoader/style.scss:27
- `.vm-preview-icons-item__svg` moves (`transition: transform 100ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Icons/style.scss:45
- `.vm-checkbox-track__thumb` moves (`transition: transform 100ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Checkbox/style.scss:133
- `.vm-button` moves (`transition: transform 0.2s, opacity 0.2s, background-color 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Button/style.scss:20
- `.vm-accordion-header__arrow` moves (`transition: transform 200ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Main/Accordion/style.scss:18
- `.vm-filter-sidebar-field__arrow` moves (`transition: transform 200ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/style.scss:72
- `.vm-timezones-item__icon` moves (`transition: transform 200ms ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/Timezones/style.scss:46
- `.vm-browser-tab-controller-palette-list__item` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/BrowserTabController/style.scss:33
- `.vm-auto-refresh-control-button__arrow` moves (`transition: transform 200ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/style.scss:15
- `.vm-bar-hits-legend-item__actions` moves (`transition: transform 200ms ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/style.scss:55
- `.vm-snackbar` moves (`animation: .15s cubic-bezier(.28,.84,.42,1.1) vm-slide-snackbar`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- `.vm-list-item_multiselect svg` moves (`animation: .15s cubic-bezier(.28,.84,.42,1) vm-scale`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- `.vm-switch-track__thumb` moves (`transition: right .2s ease-out,left .2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/vlselect/vmui/assets/index-rJc3FX5d.css:1
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `http.DefaultClient` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:203
What to do
- Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:67 · app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:70 — the two spans are one implementation copied and then locally edited — 681 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. — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:67
- app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldNames.tsx:17 · app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopStreamNames.tsx:17 — 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. — app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldNames.tsx:17
- app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/MonthsList/MonthsList.tsx:15 · app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/YearsList/YearsList.tsx:13 — 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. — app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/MonthsList/MonthsList.tsx:15
- app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:35 · app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamValues.ts:21 — the two spans are one implementation copied and then locally edited — 325 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. — app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:35
- app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldFilterExclude.tsx:14 · app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldFilterInclude.tsx:14 — 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. — app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldFilterExclude.tsx:14
- app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:497 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:576 — 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. — app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:497
- app/vmui/packages/vmui/src/state/common/StateContext.tsx:5 · app/vmui/packages/vmui/src/state/overview/OverviewStateContext.tsx:5 — 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. — app/vmui/packages/vmui/src/state/common/StateContext.tsx:5
- app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:60 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:98 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:420 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:60
- app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:34 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:56 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:74 · app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:94 · +10 more site(s) not listed — all 14 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. — app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:34
- app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderMenu/TableHeaderMenu.tsx:44 · app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldRowActions.tsx:51 — the two spans are one implementation copied and then locally edited — 63 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. — app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderMenu/TableHeaderMenu.tsx:44
- app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/AutoRefreshControl.tsx:81 · app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/TenantsSelect.tsx:51 — 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. — app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/AutoRefreshControl.tsx:81
- app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderCell.tsx:80 · app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsItem.tsx:45 — 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. — app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderCell.tsx:80
- app/vmui/packages/vmui/src/pages/OverviewPage/FiltersBar/FiltersBarPreview.tsx:62 · app/vmui/packages/vmui/src/pages/OverviewPage/FiltersBar/FiltersBarPreview.tsx:76 — 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. — app/vmui/packages/vmui/src/pages/OverviewPage/FiltersBar/FiltersBarPreview.tsx:62
- app/vmui/packages/vmui/src/utils/ansiParser.tsx:140 · app/vmui/packages/vmui/src/utils/ansiParser.tsx:167 — 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. — app/vmui/packages/vmui/src/utils/ansiParser.tsx:140
- app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemHandle.ts:41 · app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemHandle.ts:57 — 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. — app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemHandle.ts:41
- app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:274 · app/vmui/packages/vmui/src/pages/QueryPage/QueryPageBody/QueryPageBody.tsx:125 — 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. — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:274
- app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:210 · app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:234 — 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. — app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:210
- app/vmui/packages/vmui/src/state/logsPanel/LogsStateContext.tsx:11 · app/vmui/packages/vmui/src/state/query/QueryStateContext.tsx:11 · app/vmui/packages/vmui/src/state/time/TimeStateContext.tsx:11 — the 3 copies are spread across 3 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. 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. — app/vmui/packages/vmui/src/state/logsPanel/LogsStateContext.tsx:11
- app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/Tenants.tsx:63 · app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TimeZonePreview/TimeZonePreview.tsx:31 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/Tenants.tsx:63
- app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:66 · app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:98 — the two spans are one implementation copied and then locally edited — 94 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. — app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:66
- app/vmui/packages/vmui/src/layouts/Header/HeaderNav/HeaderNav.tsx:45 · app/vmui/packages/vmui/src/layouts/Header/HeaderNav/NavSubItem.tsx:102 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/vmui/packages/vmui/src/layouts/Header/HeaderNav/HeaderNav.tsx:45
- app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:218 · app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:233 — 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. — app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:218
- app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:153 · app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:195 — 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. — app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:153
- app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:144 · app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:102 — 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. — app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:144
- app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:101 · app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamValues.ts:74 — 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. — app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:101
- app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsHotKeys.tsx:7 · app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsHotKeys.tsx:16 — 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. — app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsHotKeys.tsx:7
- app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldGroupingToggle.tsx:6 · app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldMessageToggle.tsx:6 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldGroupingToggle.tsx:6
- app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:51 · app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:59 — 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. — app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:51
- app/vmui/packages/vmui/src/pages/QueryPage/utils/fetchHitsOnce.ts:14 · app/vmui/packages/vmui/src/pages/QueryPage/utils/fetchHitsStats.ts:8 — 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. — app/vmui/packages/vmui/src/pages/QueryPage/utils/fetchHitsOnce.ts:14
- app/vmui/packages/vmui/src/layouts/Header/HeaderControls/HeaderControls.tsx:17 · app/vmui/packages/vmui/src/layouts/LogsLayout/LogsLayout.tsx:21 — the two spans are one implementation copied and then locally edited — 54 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. — app/vmui/packages/vmui/src/layouts/Header/HeaderControls/HeaderControls.tsx:17
- app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:38 · app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:37 · app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamValues.ts:23 — 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. — app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:38
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.
R2 · Cyclomatic Complexity
- syncQueries has cyclomatic complexity 45 and cognitive complexity 53; 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. — app/vmui/packages/vmui/src/pages/QueryPage/hooks/useQueryPageController/useQueryPageController.ts:115
- (anonymous) has cyclomatic complexity 25 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 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. — app/vmui/packages/vmui/src/components/Main/Autocomplete/hooks/useAutocompleteKeyboard.ts:20
- splitLogicalParts has cyclomatic complexity 23 and cognitive complexity 33; 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. — app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:13
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 25; 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. — app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchLogs.ts:107
- (anonymous) has cyclomatic complexity 19 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. — app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:82
- (anonymous) has cyclomatic complexity 19 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 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. — app/vmui/packages/vmui/src/components/Main/Popper/PopperContent.tsx:44
- FilterSidebarField has cyclomatic complexity 18 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 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. — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:40
- (anonymous) has cyclomatic complexity 17 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 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. — app/vmui/packages/vmui/src/components/Main/Pagination/SelectLimit/SelectLimit.tsx:30
- (anonymous) has cyclomatic complexity 16 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 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. — app/vmui/packages/vmui/src/components/Main/Tooltip/Tooltip.tsx:45
- BarHitsOptions has cyclomatic complexity 16 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 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. — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:46
- handleKeyDown has cyclomatic complexity 16 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 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. — app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryEditor.tsx:109
- (anonymous) has cyclomatic complexity 15 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. — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarPaths.ts:87
- (anonymous) has cyclomatic complexity 15 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. — app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchHits.ts:78
- (anonymous) has cyclomatic complexity 15 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. — app/vmui/packages/vmui/src/utils/ansiParser.tsx:123
- QueryPageBody has cyclomatic complexity 14 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. — app/vmui/packages/vmui/src/pages/QueryPage/QueryPageBody/QueryPageBody.tsx:52
- buildFilterExpr has cyclomatic complexity 13 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. — app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:21
- (anonymous) has cyclomatic complexity 13 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. (×2) — app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:61, app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamValues.ts:29
- (anonymous) has cyclomatic complexity 13 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 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. — app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:67
- FilterSidebar has cyclomatic complexity 13 and cognitive complexity 9; 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. — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:41
- (anonymous) has cyclomatic complexity 12 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. — app/vmui/packages/vmui/src/utils/logs.ts:8
- (anonymous) 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. (×3) — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarPaths.ts:131, app/vmui/packages/vmui/src/components/DownloadLogs/useDownloadLogs.ts:23, app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:43
- processStatsQueryRange 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. — app/vmui/packages/vmui/src/pages/QueryPage/utils/processStatsQueryRange.ts:14
- fetchData 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. — app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/hooks/useLogsQLFetchOptions.tsx:71
- descendingComparator 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. — app/vmui/packages/vmui/src/components/Table/helpers.ts:6
- onDragOverKeyLive 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. — app/vmui/packages/vmui/src/components/Table/hooks/useDragColumn.ts:58
- GroupLogs 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. — app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:30
- (anonymous) 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. — app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchQueryTime.ts:41
- TopFieldValues has cyclomatic complexity 11 and cognitive complexity 9; 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. — app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldValues.tsx:44
R3 · Large Files
- app/vmui/packages/vmui/src/components/Main/Icons/index.tsx has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:1, app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:1, app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- The package in `app/vmui/packages/vmui` declares the lint script `lint` (`eslint --format stylish 'src/**/*.{ts,tsx}'`), but no step of this repository's CI runs it, by name, through another script, a REDACTED target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `app/vmui/packages/vmui` (or the workspace's task runner). — app/vmui/packages/vmui/package.json:12
R7 · Dead Code
- Unreachable from the 4 application, 6 tooling and 46 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (4 application, 6 tooling, 46 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×12) — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/ServerConfigurator/ServerConfigurator.tsx, app/vmui/packages/vmui/src/hooks/useDropzone.ts, app/vmui/packages/vmui/src/utils/math.ts, …
- no import path from any entry point (4 application, 6 tooling, 46 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioGroup.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioOption.tsx
- Nothing imports this binding — it is safe to review for removal. (×9) — app/vmui/packages/vmui/src/api/types.ts:14, app/vmui/packages/vmui/src/utils/color.ts:3, app/vmui/packages/vmui/src/utils/color.ts:72, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in app/vmui/packages/vmui/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in app/vmui/packages/vmui/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — app/vmui/packages/vmui/src/types/uplot.ts:29, app/vmui/packages/vmui/src/types/uplot.ts:52
- 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. — app/vmui/packages/vmui/src/components/Main/Button/Button.tsx:17
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 package.json — installs work only by hoisting accident. (×2) — app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/BarHitsLegendItem.tsx:10, app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/hooks/useAutoRefreshInterval.ts:3
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- app/vmui/packages/vmui/src/components/Main/Autocomplete/Autocomplete.tsx → app/vmui/packages/vmui/src/components/Main/Autocomplete/AutocompleteList/AutocompleteList.tsx → app/vmui/packages/vmui/src/components/Main/Autocomplete/Autocomplete.tsx (one verified cycle inside a mutually-dependent group of 3 files) — app/vmui/packages/vmui/src/components/Main/Autocomplete/Autocomplete.tsx:7
- app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx → app/vmui/packages/vmui/src/pages/StreamContext/StreamContextButton.tsx → app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx → app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx — app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:18
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X14 · Bypassable address classification
X2 · Cancellation propagation
- Only 6/10 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchAppConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — app/vmui/packages/vmui/src/hooks/useFetchAppConfig.ts:12
- `fetchVersion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — app/vmui/packages/vmui/src/hooks/useGetVersion.ts:11
- `fetchData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/hooks/useFetchAccountIds.ts:21
- `generateAndPushLogs` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:173
What to do
- Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
X26 · Unsynchronised callback handoff
- `readWithLess` hands values from a goroutine to the body waiting on it through `_`, a variable — the goroutine writes it with `_ = …` on line 75, and the body touches it at line 80. Those two spans provably run concurrently: this body waits on `waitch`, which nothing but the goroutine raises, so the goroutine cannot be the flow that is waiting for it. The touch comes after the goroutine is started and BEFORE the body waits on `waitch`, so the Go memory model orders nothing between it and the goroutine's write. A goroutine's closure captures `_` by reference, so every goroutine and the body use ONE variable, and a plain variable has no synchronisation of its own: by the Go memory model a write concurrent with any other access to it is a data race (the race detector reports it), a racing `++` loses updates, and a racing read sees a stale or torn value. `waitch` is a channel, which orders the handoff's signal and takes no exclusion over the variable's own state. Hand the values over the channel itself instead of beside it, or guard every access to `_` on both sides with one `sync.Mutex`. — app/vlogscli/less_wrapper.go:75
What to do
- In Go, hand values from a goroutine to the body waiting on it over a channel the body receives from, rather than through a map or slice beside a `sync.WaitGroup` or a signal channel — or hold one `sync.Mutex` over every access to the shared map or slice on both sides. The wait orders the signal; it takes no exclusion over the map's or slice's own state.
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if err != nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×24) — lib/logstorage/filter_json_array_contains_any.go:192, lib/logstorage/parser.go:2855, lib/logstorage/parser.go:2868, …
- `if _, err := lex.nextCompoundTokenExt(stopTokens); err != nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — lib/logstorage/pipe.go:193
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/adapters/downloader.ts:83, app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/adapters/downloader.ts:239
- `catch (e)` 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. — app/vmui/packages/vmui/src/components/Table/hooks/useTableColumnView.ts:62
- 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. — app/vmui/packages/vmui/src/components/Main/TextField/TextField.tsx:158
- `if firstErr != nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — app/vlinsert/datadog/datadog.go:130, app/vlinsert/datadog/datadog.go:154
- `ok, _ := doublestar.PathMatch(excludePattern, filePath)` writes the call's error to `_` and then uses `ok` as if the call succeeded. When `doublestar.PathMatch` fails, `ok` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `ok` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — app/vlagent/filecollector/file_collector.go:125
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~0.4 `!` null assertions per 1k TypeScript source lines — 13 assertion(s) across the 31070 source line(s) of the 414 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: app/vmui/packages/vmui/src/pages/QueryPage/utils/fetchHitsIterative.ts (4), app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/adapters/downloader.ts (4), app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts (2). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82.5 | Strong | Solid. |
| Architecture | 85.1 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 74.8 | Strong | Solid. |
| Readiness | 59.1 | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58.6 | Adequate — gated by D29, D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 39.7 | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 58 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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 — compose up failed (exit 18 — an image could not be pulled) — vlogs Pulling vmsingle Pulling du-exporter Pulling cadvisor Pulling grafana Pulling node-exporter Pulling cadvisor Error Get "https://gcr.io/v2/": Forbidden grafana Error context canceled vlogs Error context canceled node-exporter Error context canceled du-exporter Error context canceled vmsingle Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the earlier `compose pull` step reported: du-exporter Pulling cadvisor Pulling grafana Pulling node-exporter Pulling vmsingle Pulling vlogs Pulling cadvisor Error Get "https://gcr.io/v2/": Forbidden du-exporter Error context canceled vmsingle Error context canceled vlogs Error context canceled node-exporter Error context canceled grafana Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .go exposed no member bodies
- D11 Test Reliability — No tests discovered
- D15 Churn × Complexity Hotspots — complexity unreadable for .go — churn × complexity hotspots could not be measured
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .go exposed no member bodies
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .go, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D3 God Classes — Most of this repository's production source (.go) was not read by god-class detection, so type and module size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's type and module size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D4 Code Duplication — Duplication not measured — .go not exposed to the token comparison
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — app/vmui/packages/vmui/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 29% of this repository's production lines — go (66,083 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 29% of this repository's production lines — go (66,083 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — X16 reached only 29% of this repository's production lines — go (66,083 lines), python (28 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X18 Disposal-pattern correctness — 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
- 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.
- X21 Side-effecting pattern guard — X21 reached only 29% of this repository's production lines — go (66,083 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 29% of this repository's production lines — go (66,083 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — X25 reached only 29% of this repository's production lines — go (66,083 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — X29 reached only 29% of this repository's production lines — go (66,083 lines), python (28 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
- 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 — 90 finding(s)
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/BarHitsLegendItem.tsx:79
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Chart/BarHitsChart/LegendHitsMenu/LegendHitsMenuRow.tsx:71
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/GlobalSettings.tsx:75
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/Tenants.tsx:61
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/TenantsSelect.tsx:53
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/Timezones/TimezonesList.tsx:92
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/Timezones/TimezonesList.tsx:112
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/Timezones/TimezonesPicker.tsx:46
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Configurators/TimeRangeSettings/TimeDurationSelector/TimeDurationSelector.tsx:29
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/DownloadLogs/DownloadLogsModal.tsx:64
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/ExtraFilters/ExtraFiltersPanel/ExtraFiltersPanelItem.tsx:54
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:221
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarValue/FilterSidebarValue.tsx:61
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Autocomplete/AutocompleteList/AutocompleteList.tsx:69
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Checkbox/Checkbox.tsx:40
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarBody/CalendarBody.tsx:56
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:25
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:38
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:44
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/MonthsList/MonthsList.tsx:41
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/YearsList/YearsList.tsx:39
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Icons/PreviewIcons.tsx:16
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Pagination/SelectLimit/SelectLimit.tsx:86
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Pagination/SelectLimit/SelectLimit.tsx:134
- Click handler on a non-interactive <div> app/vmui/packages/vmui/src/components/Main/Select/MultipleSelectedValue/MultipleSelectedValue.tsx:33
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/components/ExtraFilters/ExtraFiltersPanel/ExtraFiltersPanelItem.tsx:54
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:38
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/CalendarHeader/CalendarHeader.tsx:44
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/components/Main/Select/MultipleSelectedValue/MultipleSelectedValue.tsx:33
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/components/Main/Select/Select.tsx:166
- Custom control with no accessible name on <div> app/vmui/packages/vmui/src/contexts/Snackbar.tsx:65
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control app/vmui/packages/vmui/src/components/Main/DatePicker/DateTimeInput/DateTimeInput.tsx:66
- <label> that labels no control app/vmui/packages/vmui/src/components/Main/Toggle/Toggle.tsx:50
- <button> with no accessible text app/vmui/packages/vmui/src/components/Main/Pagination/Pagination.tsx:72
- <button> with no accessible text app/vmui/packages/vmui/src/components/Main/Pagination/Pagination.tsx:93
- Click handler on a non-interactive <p> app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryExamples/QueryExamplesSidebar.tsx:21
- Click handler on a non-interactive <p> app/vmui/packages/vmui/src/components/Configurators/TimeRangeSettings/TimeSelector/TimeSelector.tsx:175
- Click handler on a non-interactive <tr> app/vmui/packages/vmui/src/components/Table/TableRow/TableRow.tsx:28
- Click handler on a non-interactive <tr> app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsItem.tsx:74
- <input> without a programmatic label app/vmui/packages/vmui/src/components/Main/Select/Select.tsx:151
- Clickable element isn't keyboard-operable app/vmui/packages/vmui/src/components/Configurators/LogsLimitController/LimitConfirmModal.tsx:63
- Click handler on a non-interactive <header> app/vmui/packages/vmui/src/components/Main/Accordion/Accordion.tsx:39
- Click handler on a non-interactive <span> app/vmui/packages/vmui/src/components/Main/TextField/TextFieldMessage.tsx:53
- Click handler on a non-interactive <th> app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderCell.tsx:126
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge lib/logstorage/block_header.go:1
- Unlisted import 'react' app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/BarHitsLegendItem.tsx:10
- Unlisted import 'react-router' app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/hooks/useAutoRefreshInterval.ts:3
- Import cycle (2 files) app/vmui/packages/vmui/src/components/Main/Autocomplete/Autocomplete.tsx:7
- Import cycle (3 files) app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:18
Serious — 297 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Configurators/TimeRangeSettings/TimeSelector/TimeSelector.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsConfigurators/GroupLogsConfigurators.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsPlot/BarHitsPlot.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarPaths.ts:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarHitsOptions.ts:1
- No test reaches this file app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldValues.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/hooks/useLogsQLFetchOptions.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/QueryPage/HitsPanel/HitsPanel.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/QueryPage/QueryPageBody/QueryPageBody.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsTooltip/BarHitsTooltip.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Views/LiveTailingView/LiveTailingView.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Main/Pagination/SelectLimit/SelectLimit.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/QueryPage/QueryPage.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Main/Button/AllButtonsPreview.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsChart.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsItem.tsx:1
- No test reaches this file app/vmui/packages/vmui/src/pages/QueryPage/QueryPageHeader/QueryPageHeader.tsx:1
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/styles/core.scss:59
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/styles/components/list.scss:41
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/layouts/Header/SidebarNav/style.scss:20
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/layouts/Header/SidebarNav/style.scss:43
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/layouts/Header/HeaderNav/style.scss:52
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Views/GroupView/style.scss:114
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Views/GroupView/style.scss:220
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Table/style.scss:26
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Table/TableSettings/style.scss:152
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableSortButton/style.scss:9
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Tooltip/style.scss:16
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Toggle/style.scss:65
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Tabs/style.scss:52
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Switch/style.scss:73
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Select/style.scss:92
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/RadioGroup/style.scss:50
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Popper/style.scss:19
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:26
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:63
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:67
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:40
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:77
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:81
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/LineLoader/style.scss:27
- Animation without a prefers-reduced-motion guard app/vmui/packages/vmui/src/components/Main/Icons/style.scss:45
- Swallowed exception (caught, then discarded) lib/logstorage/filter_json_array_contains_any.go:192
- Swallowed exception (caught, then discarded) lib/logstorage/parser.go:2855
- Swallowed exception (caught, then discarded) lib/logstorage/parser.go:2868
- Swallowed exception (caught, then discarded) lib/logstorage/pattern.go:169
- Swallowed exception (caught, then discarded) lib/logstorage/pattern.go:173
- Swallowed exception (caught, then discarded) lib/logstorage/pattern.go:183
- Swallowed exception (caught, then discarded) lib/logstorage/pattern_matcher.go:372
- Swallowed exception (caught, then discarded) lib/logstorage/pattern_matcher.go:380
- Swallowed exception (caught, then discarded) lib/logstorage/pipe.go:193
- Swallowed exception (caught, then discarded) lib/logstorage/pipe_format.go:463
- Swallowed exception (caught, then discarded) lib/logstorage/pipe_unroll.go:268
- Swallowed exception (caught, then discarded) lib/logstorage/pipe_unroll.go:272
- Swallowed exception (caught, then discarded) REDACTED:1875
- Swallowed exception (caught, then discarded) lib/logstorage/stream_filter.go:269
- Swallowed exception (caught, then discarded) lib/logstorage/stream_filter.go:274
- Swallowed exception (caught, then discarded) lib/logstorage/stream_id.go:38
- Swallowed exception (caught, then discarded) lib/logstorage/syslog_parser.go:128
- Swallowed exception (caught, then discarded) lib/logstorage/syslog_parser.go:665
- Swallowed exception (caught, then discarded) app/vmui/packages/vmui/src/components/Table/hooks/useTableColumnView.ts:62
- Swallowed exception (caught, then discarded) app/vlinsert/datadog/datadog.go:130
- Swallowed exception (caught, then discarded) app/vlinsert/datadog/datadog.go:154
- Swallowed exception (caught, then discarded) app/vlagent/tail/tailer.go:403
- Swallowed exception (caught, then discarded) app/vlagent/kubernetescollector/processor.go:284
- Swallowed exception (caught, then discarded) app/vlagent/kubernetescollector/processor.go:333
- Swallowed exception (caught, then discarded) app/vlagent/kubernetescollector/processor.go:387
- <TextField> field component without a label app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/ServerConfigurator/ServerConfigurator.tsx:78
- <TextField> field component without a label app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryExamples/QueryExamplesModal.tsx:70
- <TextField> field component without a label app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:181
- <TextField> field component without a label app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:292
- <TextField> field component without a label app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsSearch.tsx:20
- <TextField> field component without a label app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFields.tsx:47
- TodoComment REDACTED:494
- TodoComment lib/logstorage/pipe_unpack.go:28
- TodoComment lib/logstorage/pipe_unpack_syslog.go:61
- TodoComment REDACTED:450
- TodoComment lib/logstorage/stream_tags.go:339
- TodoComment app/vmui/packages/vmui/src/constants/markedPlugins.ts:8
- Focus outline removed in CSS without a :focus replacement app/vmui/packages/vmui/src/styles/reset.scss:42
- Focus outline removed in CSS without a :focus replacement app/vmui/packages/vmui/src/components/Main/MenuBurger/style.scss:12
- Focus outline removed in CSS without a :focus replacement app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- Focus outline removed in CSS without a :focus replacement app/vlselect/vmui/assets/index-rJc3FX5d.css:1
- Change coupling: BarHitsChart.tsx ↔ QueryPage.tsx app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsChart.tsx:1
- Change coupling: GroupLogs.tsx ↔ QueryPageBody.tsx app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:1
- Change coupling: QueryPage.tsx ↔ useFetchLogs.ts app/vmui/packages/vmui/src/pages/QueryPage/QueryPage.tsx:1
- Change coupling: QueryEditor.tsx ↔ Autocomplete.tsx app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryEditor.tsx:1
- Duplicated block (7 lines × 2 locations) app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsHotKeys.tsx:7
- Duplicated block (7 lines × 2 locations) app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldGroupingToggle.tsx:6
- Duplicated block (7 lines × 2 locations) app/vmui/packages/vmui/src/pages/OverviewPage/OverviewLogs/OverviewLogs.tsx:51
- Duplicated block (7 lines × 2 locations) app/vmui/packages/vmui/src/pages/QueryPage/utils/fetchHitsOnce.ts:14
- REDACTED
- REDACTED
- REDACTED
- Complex function (anonymous) (cyclomatic 12, cognitive 14) app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarPaths.ts:131
- Complex function (anonymous) (cyclomatic 12, cognitive 14) app/vmui/packages/vmui/src/components/DownloadLogs/useDownloadLogs.ts:23
- Complex function (anonymous) (cyclomatic 12, cognitive 14) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:43
- Async function without AbortSignal: fetchAppConfig app/vmui/packages/vmui/src/hooks/useFetchAppConfig.ts:12
- Async function without AbortSignal: fetchVersion app/vmui/packages/vmui/src/hooks/useGetVersion.ts:11
- Async function without AbortSignal: fetchData app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/hooks/useFetchAccountIds.ts:21
- Swallowed exception (empty catch) app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/adapters/downloader.ts:83
- Swallowed exception (empty catch) app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/adapters/downloader.ts:239
- Swallowed exception (empty catch) app/vmui/packages/vmui/src/components/Main/TextField/TextField.tsx:158
- Page without a main landmark app/vlselect/vmui/index.html:2
- Page without a main landmark app/vmui/packages/vmui/index.html:2
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2 locations) app/vmui/packages/vmui/src/pages/OverviewPage/FiltersBar/FiltersBarPreview.tsx:62
- Duplicated block (13 lines × 2 locations) app/vmui/packages/vmui/src/utils/ansiParser.tsx:140
- Duplicated block (11 lines × 2 locations) app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:274
- Duplicated block (11 lines × 2 locations) app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:210
- Duplicated block (10 lines × 2 locations) app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/Tenants.tsx:63
- Duplicated block (10 lines × 2 locations) app/vmui/packages/vmui/src/layouts/Header/HeaderNav/HeaderNav.tsx:45
- Duplicated block (9 lines × 2 locations) app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:218
- Duplicated block (9 lines × 2 locations) app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:153
- Duplicated block (8 lines × 2 locations) app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsItem.tsx:144
- Duplicated block (8 lines × 2 locations) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:101
- Complex function (anonymous) (cyclomatic 13, cognitive 15) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:61
- Complex function (anonymous) (cyclomatic 13, cognitive 15) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamValues.ts:29
- <Autocomplete> field component without a label app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/LogsQueryEditorAutocomplete.tsx:41
- <fieldset> without a <legend> app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioGroup.tsx:26
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change-coupling hub: useFetchHits.ts → HitsPanel.tsx, useFetchLogs.ts, logs.ts app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchHits.ts
- Coverage not measured — JavaScript/TypeScript suite
- Outbound HTTP without resilience REDACTED:203
- Duplicated block with local edits (108 matched lines × 2 locations) app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:67
- Duplicated block (104 lines × 2 locations) app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldNames.tsx:17
- Duplicated block (43 lines × 2 locations) app/vmui/packages/vmui/src/components/Main/DatePicker/Calendar/MonthsList/MonthsList.tsx:15
- Duplicated block with local edits (38 matched lines × 2 locations) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:35
- Duplicated block (28 lines × 2 locations) app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogsFieldRowMenu/FieldFilterExclude.tsx:14
- Duplicated block (21 lines × 2 locations) app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:497
- Duplicated block (18 lines × 2 locations) app/vmui/packages/vmui/src/state/common/StateContext.tsx:5
- Duplicated block (17 lines × 3 locations) app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:60
- Duplicated block (16 lines × 14 locations) app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:34
- Duplicated block with local edits (16 matched lines × 2 locations) app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderMenu/TableHeaderMenu.tsx:44
- Duplicated block (15 lines × 2 locations) app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/AutoRefreshControl.tsx:81
- Duplicated block with local edits (13 matched lines × 2 locations) app/vmui/packages/vmui/src/components/Table/TableHeaderCell/TableHeaderCell.tsx:80
- Duplicated block (12 lines × 2 locations) app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemHandle.ts:41
- Duplicated block (11 lines × 3 locations) app/vmui/packages/vmui/src/state/logsPanel/LogsStateContext.tsx:11
- Duplicated block with local edits (10 matched lines × 2 locations) app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:66
- Duplicated block with local edits (6 matched lines × 2 locations) app/vmui/packages/vmui/src/layouts/Header/HeaderControls/HeaderControls.tsx:17
- Duplicated block (5 lines × 3 locations) app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchFieldNames.ts:38
- Complex function syncQueries (cyclomatic 45, cognitive 53) app/vmui/packages/vmui/src/pages/QueryPage/hooks/useQueryPageController/useQueryPageController.ts:115
- Complex function (anonymous) (cyclomatic 25, cognitive 20) app/vmui/packages/vmui/src/components/Main/Autocomplete/hooks/useAutocompleteKeyboard.ts:20
- Complex function splitLogicalParts (cyclomatic 23, cognitive 33) app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/helpers/parser.ts:13
- Complex function (anonymous) (cyclomatic 21, cognitive 25) app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchLogs.ts:107
- Complex function (anonymous) (cyclomatic 19, cognitive 22) app/vmui/packages/vmui/src/components/Table/TableSettings/TableSettingsColumns.tsx:82
- Complex function (anonymous) (cyclomatic 19, cognitive 16) app/vmui/packages/vmui/src/components/Main/Popper/PopperContent.tsx:44
- Complex function FilterSidebarField (cyclomatic 18, cognitive 12) app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebarField/FilterSidebarField.tsx:40
- Complex function (anonymous) (cyclomatic 17, cognitive 13) app/vmui/packages/vmui/src/components/Main/Pagination/SelectLimit/SelectLimit.tsx:30
- Complex function (anonymous) (cyclomatic 16, cognitive 15) app/vmui/packages/vmui/src/components/Main/Tooltip/Tooltip.tsx:45
- Complex function BarHitsOptions (cyclomatic 16, cognitive 14) app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsOptions/BarHitsOptions.tsx:46
- Complex function handleKeyDown (cyclomatic 16, cognitive 14) app/vmui/packages/vmui/src/components/Configurators/QueryEditor/QueryEditor.tsx:109
- Complex function (anonymous) (cyclomatic 15, cognitive 23) app/vmui/packages/vmui/src/components/Chart/BarHitsChart/hooks/useBarPaths.ts:87
- Complex function (anonymous) (cyclomatic 15, cognitive 21) app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchHits.ts:78
- Complex function (anonymous) (cyclomatic 15, cognitive 15) app/vmui/packages/vmui/src/utils/ansiParser.tsx:123
- Complex function QueryPageBody (cyclomatic 14, cognitive 11) app/vmui/packages/vmui/src/pages/QueryPage/QueryPageBody/QueryPageBody.tsx:52
- Complex function buildFilterExpr (cyclomatic 13, cognitive 18) app/vmui/packages/vmui/src/components/ExtraFilters/utils/buildExprFromExtraFilters.ts:21
- Complex function (anonymous) (cyclomatic 13, cognitive 12) app/vmui/packages/vmui/src/pages/StreamContext/StreamContextList.tsx:67
- Complex function FilterSidebar (cyclomatic 13, cognitive 9) app/vmui/packages/vmui/src/components/FilterSidebar/FilterSidebar.tsx:41
- Complex function (anonymous) (cyclomatic 12, cognitive 17) app/vmui/packages/vmui/src/utils/logs.ts:8
- Complex function processStatsQueryRange (cyclomatic 12, cognitive 14) app/vmui/packages/vmui/src/pages/QueryPage/utils/processStatsQueryRange.ts:14
- Complex function fetchData (cyclomatic 12, cognitive 13) app/vmui/packages/vmui/src/components/Configurators/QueryEditor/LogsQL/hooks/useLogsQLFetchOptions.tsx:71
- Complex function descendingComparator (cyclomatic 12, cognitive 13) app/vmui/packages/vmui/src/components/Table/helpers.ts:6
- Complex function onDragOverKeyLive (cyclomatic 12, cognitive 11) app/vmui/packages/vmui/src/components/Table/hooks/useDragColumn.ts:58
- Complex function GroupLogs (cyclomatic 12, cognitive 11) app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:30
- Complex function (anonymous) (cyclomatic 12, cognitive 11) app/vmui/packages/vmui/src/pages/QueryPage/hooks/useFetchQueryTime.ts:41
- Complex function TopFieldValues (cyclomatic 11, cognitive 9) app/vmui/packages/vmui/src/pages/OverviewPage/OverviewFields/OverviewFieldsTables/TopFieldValues.tsx:44
- app/vmui/packages/vmui/src/components/Main/Icons/index.tsx: 701 lines of code app/vmui/packages/vmui/src/components/Main/Icons/index.tsx:1
- This package's lint script runs in no CI job app/vmui/packages/vmui/package.json:12
- Dead file (~100 LoC) app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/ServerConfigurator/ServerConfigurator.tsx
- Dead file (~60 LoC) app/vmui/packages/vmui/src/hooks/useDropzone.ts
- Dead file (~59 LoC) app/vmui/packages/vmui/src/utils/math.ts
- Dead file (~55 LoC) app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioOption.tsx
- Dead file (~53 LoC) app/vmui/packages/vmui/src/utils/file.ts
- Dead file (~46 LoC) app/vmui/packages/vmui/src/components/Main/RadioGroup/RadioGroup.tsx
- Dead file (~36 LoC) app/vmui/packages/vmui/src/components/Main/Hyperlink/Hyperlink.tsx
- Dead file (~35 LoC) app/vmui/packages/vmui/src/hooks/useElementSize.ts
- Dead file (~32 LoC) app/vmui/packages/vmui/src/hooks/useFetchAppConfig.ts
- Dead file (~29 LoC) app/vmui/packages/vmui/src/hooks/useSortedCategories.ts
- Dead file (~22 LoC) app/vmui/packages/vmui/src/components/Main/LineProgress/LineProgress.tsx
- Dead file (~10 LoC) app/vmui/packages/vmui/src/utils/uplot/types.ts
- Dead file (~7 LoC) app/vmui/packages/vmui/src/utils/json.ts
- Function without context.Context: generateAndPushLogs REDACTED:173
- Collection crosses a callback boundary unsynchronised app/vlogscli/less_wrapper.go:75
- Discarded error (assigned to `_`, then its result used) app/vlagent/filecollector/file_collector.go:125
Minor — 234 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file lib/logstorage/block_stream_reader.go:1
- Orphaned file lib/logstorage/block_data.go:1
- Orphaned file lib/logstorage/filter_range.go:1
- Orphaned file lib/logstorage/filter_substring.go:1
- Orphaned file lib/logstorage/filter_exact.go:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file lib/logstorage/filter_contains_all.go:1
- Orphaned file lib/prefixfilter/filter.go:1
- Orphaned file lib/logstorage/filter_len_range.go:1
- Orphaned file lib/logstorage/filter_pattern_match.go:1
- Orphaned file lib/logstorage/filter_contains_any.go:1
- Orphaned file apptest/app.go:1
- Orphaned file lib/logstorage/filter_sequence.go:1
- Orphaned file lib/logstorage/filter_exact_prefix.go:1
- Orphaned file lib/logstorage/part.go:1
- Orphaned file REDACTED:1
- Orphaned file lib/logstorage/stream_filter.go:1
- Orphaned file lib/logstorage/stats_row_max.go:1
- Orphaned file lib/logstorage/stats_row_min.go:1
- Orphaned file lib/logstorage/filter_regexp.go:1
- Orphaned file lib/logstorage/filter_string_range.go:1
- Orphaned file lib/logstorage/filter_generic.go:1
- Orphaned file lib/logstorage/stats_field_min.go:1
- Orphaned file lib/logstorage/filter_json_array_contains_any.go:1
- Duplicated predicate lib/logstorage/parser.go:2275
- Duplicated predicate lib/logstorage/stats_field_max.go:74
- Duplicated predicate lib/logstorage/filter_exact.go:243
- Duplicated predicate app/vlinsert/internalinsert/internalinsert.go:48
- Duplicated predicate app/vlinsert/journald/journald.go:82
- Duplicated predicate REDACTED:906
- Duplicated predicate lib/logstorage/pipe_math.go:488
- Duplicated predicate lib/logstorage/pipe_hash.go:112
- Duplicated predicate app/vlagent/remotewrite/client.go:180
- Duplicated predicate lib/logstorage/pipe_extract.go:189
- Duplicated predicate app/vmui/packages/vmui/src/components/DownloadLogs/useDownloadLogs.ts:64
- Duplicated predicate app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFetchStreamNames.ts:103
- Duplicated predicate app/vmui/packages/vmui/src/components/Main/Popper/PopperContent.tsx:57
- Duplicated predicate app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:37
- Duplicated predicate app/vmui/packages/vmui/src/components/Views/GroupView/GroupLogs.tsx:36
- Duplicated predicate app/vmui/packages/vmui/src/utils/marked/markedLinks.ts:35
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- redundant comment app/vmui/packages/vmui/src/hooks/useDropzone.ts:14
- redundant comment app/vmui/packages/vmui/src/pages/OverviewPage/hooks/useFieldFilter.ts:101
- redundant comment app/vmui/packages/vmui/src/utils/ansiParser.test.ts:5
- redundant comment app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemFileHandle.ts:31
- redundant comment app/vmui/packages/vmui/src/utils/nativeFileSystemAdapter/FileSystemWritableFileStream.ts:20
- Silent fallback default in catch app/vmui/packages/vmui/src/components/ExtraFilters/utils/parseExtraFiltersFromSearchParams.ts:24
- Silent fallback default in catch app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/TenantsConfiguration/TenantsSelect.tsx:26
- Silent fallback default in catch app/vmui/packages/vmui/src/components/QueryHistory/utils.ts:15
- Silent fallback default in catch app/vmui/packages/vmui/src/components/Configurators/ExecutionControls/AutoRefreshControl/utils.ts:9
- Silent fallback default in catch app/vmui/packages/vmui/src/components/Configurators/GlobalSettings/Timezones/TimezonesList.tsx:54
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Documentation: no build, run or usage example README.md:1
- Documentation: no build, run or usage example app/vlagent/README.md:1
- Documentation: no build, run or usage example app/vlogscli/README.md:1
- Mock-dominated test: offers persistent warning dismissal app/vmui/packages/vmui/src/components/Configurators/LogsLimitController/LimitConfirmModal.test.tsx:19
- No ADRs found REDACTED:1
- Projects may be oversized for their cohesion app/vmui/packages/vmui/package.json:1
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- Unused export 'InstantMetricResult' app/vmui/packages/vmui/src/api/types.ts:14
- Unused export 'HideSeriesArgs' app/vmui/packages/vmui/src/types/uplot.ts:29
- Unused export 'BarSeriesItem' app/vmui/packages/vmui/src/types/uplot.ts:52
- Unused export 'baseContrastColors' app/vmui/packages/vmui/src/utils/color.ts:3
- Unused export 'generateGradient' app/vmui/packages/vmui/src/utils/color.ts:72
- Unused export 'getNameForMetric' app/vmui/packages/vmui/src/utils/metric.ts:3
- Unused export 'compactObject' app/vmui/packages/vmui/src/utils/object.ts:14
- Unused export 'getQueryArray' app/vmui/packages/vmui/src/utils/query-string.ts:13
- Unused export 'hasUnclosedQuotes' app/vmui/packages/vmui/src/utils/regexp.ts:10
- Unused export 'isEqualURLSearchParams' app/vmui/packages/vmui/src/utils/url.ts:15
- Unused export 'getApiEndpoint' app/vmui/packages/vmui/src/utils/url.ts:29
- Unused module-local declaration 'ButtonProps' app/vmui/packages/vmui/src/components/Main/Button/Button.tsx:17
- Not all functions that make a request accept a context.Context or an AbortSignal
- Null assertions (`!`) override strict null checking
- Hand-rolled JSON/XML parsing via regex app/vlselect/vmui/assets/vendor-CgUtxMLZ.js:8
Minor — 1 finding(s)
- doc comments repeat the names app/vmui/packages/vmui/src/utils/ansiParser.tsx:55
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-46b314d5a48e4456a33a2ddc36115afb/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-46b314d5a48e4456a33a2ddc36115afb/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-46b314d5a48e4456a33a2ddc36115afb/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=8439" --report-format json --report-path /tmp/watchdog-gitleaks-46b314d5a48e4456a33a2ddc36115afb/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.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-46b314d5a48e4456a33a2ddc36115afb/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude app/vmui/packages/vmui/src/generated . | 141 | 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/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 96 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `app/vlselect/vmui/assets/index-DNKuoEMC.js`, `app/vlselect/vmui/assets/vendor-CgUtxMLZ.js` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |