Public report of apache/echarts, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 14:24 UTC · Survey ID cd_9b33b357cf2e4bc7a11cbce5ddda2a67
apache/echarts
Measured 26 October 2026, 14:04 UTC, at code version 34f4d92
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 132,203 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Architecture, 40
Findings by how serious they are
52 critical988 serious397 minor
17 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 14:04 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
68of 68 dimensions measured by tools.
1413of 1437 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
68dimensions across 6 lenses, read from 132,203 lines of product code in 2 projects.
apache/echarts is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 45 out of 100, which the At risk rating leaves unchanged.
Architecture, at 40, is the weakest lens and counts most in the score. The best first step is checking whether the largest projects should be split, worth about 4 points. Making the tests check their results comes next, worth about 2 points. Raising Architecture to 70 would lift the score to about 49.
Twenty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen known security holes in the packages the code depends on can be used by attackers, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing the exposed password or key would close these risks. The place where the code runs text as code or as a command needs a direct call instead. The nine loops of files that import each other need breaking.
The product code is 132,203 lines, about €120,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1281 findings
These 1281 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
Explicit Debt · TodoComment repeated across 23 files src/chart/boxplot/BoxplotSeries.ts
Explicit Debt · FixmeComment repeated across 32 files src/chart/line/LineView.ts
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
€39,000 to €200,000, for 649 to 2,058 hours of work, about 0.8 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 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 132,203 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.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Raises the score by about 4 points · Low effort · Project Cohesion
2
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with number.test.ts.
Raises the score by about 2 points · Low effort · Test Quality
3
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with mapDataStatistic.ts.
Raises the score by about 2 points · Low effort · Change Coupling
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Architecture, at 40 (Weak). Architecture is about whether the structure holds up as the product grows, and when the structure is weak, a change in one place ripples into many others. Because the weakest lens counts most in the score, work on Architecture also moves the score most.
Based on: the rebuild estimate · the Architecture grade · how much each lens counts
What to do: Start with the Architecture actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 1 Project Cohesion findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 5% to 10% on every change. The history of the code shows how much it changes: about 35 lines over the last 90 days, which is about 142 lines a year. At that pace, the extra work comes to an estimated 0 to 0.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
407 modules, with 1383 dependencies between them. 10 loops run through 49 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 367 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
component.legend.LegendModel uses model.Model, so a change to model.Model can break component.legend.LegendModel, while a change to component.legend.LegendModel can't break model.Model.
Position
Below the diagonal: component.legend.LegendModel uses a module listed above it, which is the healthy direction.
4→12 component.legend.LegendModel uses model.Globalpart of a loop✕
Connections
1 pair of types, where a type in component.legend.LegendModel uses a type in model.Global.
component.legend.LegendModel uses model.Global, so a change to model.Global can break component.legend.LegendModel, while a change to component.legend.LegendModel can't break model.Global.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→13 component.legend.LegendModel uses model.Componentpart of a loop✕
Connections
1 pair of types, where a type in component.legend.LegendModel uses a type in model.Component.
component.legend.LegendModel uses model.Component, so a change to model.Component can break component.legend.LegendModel, while a change to component.legend.LegendModel can't break model.Component.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→14 component.legend.LegendModel uses util.typespart of a loop✕
Connections
5 pairs of types, where a type in component.legend.LegendModel uses a type in util.types.
component.legend.LegendModel uses util.types, so a change to util.types can break component.legend.LegendModel, while a change to component.legend.LegendModel can't break util.types.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→8 coord.AxisBaseModel uses coord.Axispart of a loop✕
Connections
1 pair of types, where a type in coord.AxisBaseModel uses a type in coord.Axis.
coord.AxisBaseModel uses coord.Axis, so a change to coord.Axis can break coord.AxisBaseModel, while a change to coord.AxisBaseModel can't break coord.Axis.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
view.Component uses core.ExtensionAPI, so a change to core.ExtensionAPI can break view.Component, while a change to view.Component can't break core.ExtensionAPI.
Position
Below the diagonal: view.Component uses a module listed above it, which is the healthy direction.
7→12 view.Component uses model.Globalpart of a loop✕
Connections
1 pair of types, where a type in view.Component uses a type in model.Global.
view.Component uses model.Component, so a change to model.Component can break view.Component, while a change to view.Component can't break model.Component.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→14 view.Component uses util.typespart of a loop✕
Connections
2 pairs of types, where a type in view.Component uses a type in util.types.
coord.Axis uses coord.AxisBaseModel, so a change to coord.AxisBaseModel can break coord.Axis, while a change to coord.Axis can't break coord.AxisBaseModel.
Position
Below the diagonal: coord.Axis uses a module listed above it, which is the healthy direction.
model.Series uses component.legend.LegendModel, so a change to component.legend.LegendModel can break model.Series, while a change to model.Series can't break component.legend.LegendModel.
Position
Below the diagonal: model.Series uses a module listed above it, which is the healthy direction.
core.echarts uses core.ExtensionAPI, so a change to core.ExtensionAPI can break core.echarts, while a change to core.echarts can't break core.ExtensionAPI.
Position
Below the diagonal: core.echarts uses a module listed above it, which is the healthy direction.
core.Scheduler uses core.ExtensionAPI, so a change to core.ExtensionAPI can break core.Scheduler, while a change to core.Scheduler can't break core.ExtensionAPI.
Position
Below the diagonal: core.Scheduler uses a module listed above it, which is the healthy direction.
core.Scheduler uses data.SeriesData, so a change to data.SeriesData can break core.Scheduler, while a change to core.Scheduler can't break data.SeriesData.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
component.axis uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.axis, while a change to component.axis can't break core.ExtensionAPI.
Position
Below the diagonal: component.axis uses a module listed above it, which is the healthy direction.
component.axis uses coord.AxisBaseModel, so a change to coord.AxisBaseModel can break component.axis, while a change to component.axis can't break coord.AxisBaseModel.
Position
Below the diagonal: component.axis uses a module listed above it, which is the healthy direction.
component.axis uses model.Component, so a change to model.Component can break component.axis, while a change to component.axis can't break model.Component.
Position
Below the diagonal: component.axis uses a module listed above it, which is the healthy direction.
component.axisPointer uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break component.axisPointer, while a change to component.axisPointer can't break component.axisPointer.globalListener.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.axisPointer, while a change to component.axisPointer can't break core.ExtensionAPI.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses model.Model, so a change to model.Model can break component.axisPointer, while a change to component.axisPointer can't break model.Model.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses coord.AxisBaseModel, so a change to coord.AxisBaseModel can break component.axisPointer, while a change to component.axisPointer can't break coord.AxisBaseModel.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses coord.Axis, so a change to coord.Axis can break component.axisPointer, while a change to component.axisPointer can't break coord.Axis.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses model.Global, so a change to model.Global can break component.axisPointer, while a change to component.axisPointer can't break model.Global.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses model.Component, so a change to model.Component can break component.axisPointer, while a change to component.axisPointer can't break model.Component.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.axisPointer uses util.types, so a change to util.types can break component.axisPointer, while a change to component.axisPointer can't break util.types.
Position
Below the diagonal: component.axisPointer uses a module listed above it, which is the healthy direction.
component.dataZoom.DataZoomModel uses model.Model, so a change to model.Model can break component.dataZoom.DataZoomModel, while a change to component.dataZoom.DataZoomModel can't break model.Model.
Position
Below the diagonal: component.dataZoom.DataZoomModel uses a module listed above it, which is the healthy direction.
component.dataZoom.DataZoomModel uses coord.AxisBaseModel, so a change to coord.AxisBaseModel can break component.dataZoom.DataZoomModel, while a change to component.dataZoom.DataZoomModel can't break coord.AxisBaseModel.
Position
Below the diagonal: component.dataZoom.DataZoomModel uses a module listed above it, which is the healthy direction.
component.dataZoom.DataZoomModel uses model.Global, so a change to model.Global can break component.dataZoom.DataZoomModel, while a change to component.dataZoom.DataZoomModel can't break model.Global.
Position
Below the diagonal: component.dataZoom.DataZoomModel uses a module listed above it, which is the healthy direction.
component.dataZoom.DataZoomModel uses model.Component, so a change to model.Component can break component.dataZoom.DataZoomModel, while a change to component.dataZoom.DataZoomModel can't break model.Component.
Position
Below the diagonal: component.dataZoom.DataZoomModel uses a module listed above it, which is the healthy direction.
component.dataZoom.DataZoomModel uses util.types, so a change to util.types can break component.dataZoom.DataZoomModel, while a change to component.dataZoom.DataZoomModel can't break util.types.
Position
Below the diagonal: component.dataZoom.DataZoomModel uses a module listed above it, which is the healthy direction.
component.helper.MapDraw uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.helper.MapDraw, while a change to component.helper.MapDraw can't break core.ExtensionAPI.
Position
Below the diagonal: component.helper.MapDraw uses a module listed above it, which is the healthy direction.
component.helper.MapDraw uses model.Global, so a change to model.Global can break component.helper.MapDraw, while a change to component.helper.MapDraw can't break model.Global.
Position
Below the diagonal: component.helper.MapDraw uses a module listed above it, which is the healthy direction.
component.helper.MapDraw uses util.types, so a change to util.types can break component.helper.MapDraw, while a change to component.helper.MapDraw can't break util.types.
Position
Below the diagonal: component.helper.MapDraw uses a module listed above it, which is the healthy direction.
coord.CoordinateSystem uses model.Global, so a change to model.Global can break coord.CoordinateSystem, while a change to coord.CoordinateSystem can't break model.Global.
Position
Below the diagonal: coord.CoordinateSystem uses a module listed above it, which is the healthy direction.
coord.CoordinateSystem uses model.Component, so a change to model.Component can break coord.CoordinateSystem, while a change to coord.CoordinateSystem can't break model.Component.
Position
Below the diagonal: coord.CoordinateSystem uses a module listed above it, which is the healthy direction.
coord.CoordinateSystem uses util.types, so a change to util.types can break coord.CoordinateSystem, while a change to coord.CoordinateSystem can't break util.types.
Position
Below the diagonal: coord.CoordinateSystem uses a module listed above it, which is the healthy direction.
chart.helper.baseDraw uses util.types, so a change to util.types can break chart.helper.baseDraw, while a change to chart.helper.baseDraw can't break util.types.
Position
Below the diagonal: chart.helper.baseDraw uses a module listed above it, which is the healthy direction.
chart.helper.baseDraw uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break chart.helper.baseDraw, while a change to chart.helper.baseDraw can't break coord.CoordinateSystem.
Position
Below the diagonal: chart.helper.baseDraw uses a module listed above it, which is the healthy direction.
component.dataZoom uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.dataZoom, while a change to component.dataZoom can't break core.ExtensionAPI.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses coord.AxisBaseModel, so a change to coord.AxisBaseModel can break component.dataZoom, while a change to component.dataZoom can't break coord.AxisBaseModel.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses model.Series, so a change to model.Series can break component.dataZoom, while a change to component.dataZoom can't break model.Series.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses model.Global, so a change to model.Global can break component.dataZoom, while a change to component.dataZoom can't break model.Global.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses util.types, so a change to util.types can break component.dataZoom, while a change to component.dataZoom can't break util.types.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses component.dataZoom.DataZoomModel, so a change to component.dataZoom.DataZoomModel can break component.dataZoom, while a change to component.dataZoom can't break component.dataZoom.DataZoomModel.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
component.dataZoom uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break component.dataZoom, while a change to component.dataZoom can't break coord.CoordinateSystem.
Position
Below the diagonal: component.dataZoom uses a module listed above it, which is the healthy direction.
coord.cartesian.Cartesian2D uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break coord.cartesian.Cartesian2D, while a change to coord.cartesian.Cartesian2D can't break coord.CoordinateSystem.
Position
Below the diagonal: coord.cartesian.Cartesian2D uses a module listed above it, which is the healthy direction.
data.SeriesData uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break data.SeriesData, while a change to data.SeriesData can't break component.axisPointer.globalListener.
Position
Below the diagonal: data.SeriesData uses a module listed above it, which is the healthy direction.
chart.helper.LineDraw uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break chart.helper.LineDraw, while a change to chart.helper.LineDraw can't break component.axisPointer.globalListener.
Position
Below the diagonal: chart.helper.LineDraw uses a module listed above it, which is the healthy direction.
chart.helper.LineDraw uses model.Model, so a change to model.Model can break chart.helper.LineDraw, while a change to chart.helper.LineDraw can't break model.Model.
Position
Below the diagonal: chart.helper.LineDraw uses a module listed above it, which is the healthy direction.
chart.helper.LineDraw uses util.types, so a change to util.types can break chart.helper.LineDraw, while a change to chart.helper.LineDraw can't break util.types.
Position
Below the diagonal: chart.helper.LineDraw uses a module listed above it, which is the healthy direction.
chart.helper.LineDraw uses chart.helper.baseDraw, so a change to chart.helper.baseDraw can break chart.helper.LineDraw, while a change to chart.helper.LineDraw can't break chart.helper.baseDraw.
Position
Below the diagonal: chart.helper.LineDraw uses a module listed above it, which is the healthy direction.
chart.helper.LineDraw uses data.SeriesData, so a change to data.SeriesData can break chart.helper.LineDraw, while a change to chart.helper.LineDraw can't break data.SeriesData.
Position
Below the diagonal: chart.helper.LineDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break component.axisPointer.globalListener.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses model.Model, so a change to model.Model can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break model.Model.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses model.Series, so a change to model.Series can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break model.Series.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses util.types, so a change to util.types can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break util.types.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses chart.helper.baseDraw, so a change to chart.helper.baseDraw can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break chart.helper.baseDraw.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.helper.SymbolDraw uses data.SeriesData, so a change to data.SeriesData can break chart.helper.SymbolDraw, while a change to chart.helper.SymbolDraw can't break data.SeriesData.
Position
Below the diagonal: chart.helper.SymbolDraw uses a module listed above it, which is the healthy direction.
chart.map.MapSeries uses model.Model, so a change to model.Model can break chart.map.MapSeries, while a change to chart.map.MapSeries can't break model.Model.
Position
Below the diagonal: chart.map.MapSeries uses a module listed above it, which is the healthy direction.
chart.map.MapSeries uses component.legend.LegendModel, so a change to component.legend.LegendModel can break chart.map.MapSeries, while a change to chart.map.MapSeries can't break component.legend.LegendModel.
Position
Below the diagonal: chart.map.MapSeries uses a module listed above it, which is the healthy direction.
chart.map.MapSeries uses model.Series, so a change to model.Series can break chart.map.MapSeries, while a change to chart.map.MapSeries can't break model.Series.
Position
Below the diagonal: chart.map.MapSeries uses a module listed above it, which is the healthy direction.
chart.map.MapSeries uses util.types, so a change to util.types can break chart.map.MapSeries, while a change to chart.map.MapSeries can't break util.types.
Position
Below the diagonal: chart.map.MapSeries uses a module listed above it, which is the healthy direction.
chart.map.MapSeries uses data.SeriesData, so a change to data.SeriesData can break chart.map.MapSeries, while a change to chart.map.MapSeries can't break data.SeriesData.
Position
Below the diagonal: chart.map.MapSeries uses a module listed above it, which is the healthy direction.
component.helper uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.helper, while a change to component.helper can't break core.ExtensionAPI.
Position
Below the diagonal: component.helper uses a module listed above it, which is the healthy direction.
component.helper uses model.Global, so a change to model.Global can break component.helper, while a change to component.helper can't break model.Global.
Position
Below the diagonal: component.helper uses a module listed above it, which is the healthy direction.
component.helper uses model.Component, so a change to model.Component can break component.helper, while a change to component.helper can't break model.Component.
Position
Below the diagonal: component.helper uses a module listed above it, which is the healthy direction.
component.helper uses component.helper.MapDraw, so a change to component.helper.MapDraw can break component.helper, while a change to component.helper can't break component.helper.MapDraw.
Position
Below the diagonal: component.helper uses a module listed above it, which is the healthy direction.
component.helper uses coord.cartesian.Cartesian2D, so a change to coord.cartesian.Cartesian2D can break component.helper, while a change to component.helper can't break coord.cartesian.Cartesian2D.
Position
Below the diagonal: component.helper uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses model.Model, so a change to model.Model can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break model.Model.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses model.Series, so a change to model.Series can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break model.Series.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses model.Global, so a change to model.Global can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break model.Global.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses model.Component, so a change to model.Component can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break model.Component.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses util.types, so a change to util.types can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break util.types.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.marker.MarkerModel uses data.SeriesData, so a change to data.SeriesData can break component.marker.MarkerModel, while a change to component.marker.MarkerModel can't break data.SeriesData.
Position
Below the diagonal: component.marker.MarkerModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses model.Model, so a change to model.Model can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break model.Model.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses model.Series, so a change to model.Series can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break model.Series.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses model.Global, so a change to model.Global can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break model.Global.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses model.Component, so a change to model.Component can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break model.Component.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses util.types, so a change to util.types can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break util.types.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
component.visualMap.VisualMapModel uses data.SeriesData, so a change to data.SeriesData can break component.visualMap.VisualMapModel, while a change to component.visualMap.VisualMapModel can't break data.SeriesData.
Position
Below the diagonal: component.visualMap.VisualMapModel uses a module listed above it, which is the healthy direction.
coord.cartesian uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break coord.cartesian, while a change to coord.cartesian can't break component.axisPointer.globalListener.
Position
Below the diagonal: coord.cartesian uses a module listed above it, which is the healthy direction.
coord.cartesian uses core.ExtensionAPI, so a change to core.ExtensionAPI can break coord.cartesian, while a change to coord.cartesian can't break core.ExtensionAPI.
Position
Below the diagonal: coord.cartesian uses a module listed above it, which is the healthy direction.
coord.cartesian uses coord.cartesian.Cartesian2D, so a change to coord.cartesian.Cartesian2D can break coord.cartesian, while a change to coord.cartesian can't break coord.cartesian.Cartesian2D.
Position
Below the diagonal: coord.cartesian uses a module listed above it, which is the healthy direction.
coord.parallel.Parallel uses core.ExtensionAPI, so a change to core.ExtensionAPI can break coord.parallel.Parallel, while a change to coord.parallel.Parallel can't break core.ExtensionAPI.
Position
Below the diagonal: coord.parallel.Parallel uses a module listed above it, which is the healthy direction.
coord.parallel.Parallel uses model.Global, so a change to model.Global can break coord.parallel.Parallel, while a change to coord.parallel.Parallel can't break model.Global.
Position
Below the diagonal: coord.parallel.Parallel uses a module listed above it, which is the healthy direction.
coord.parallel.Parallel uses util.types, so a change to util.types can break coord.parallel.Parallel, while a change to coord.parallel.Parallel can't break util.types.
Position
Below the diagonal: coord.parallel.Parallel uses a module listed above it, which is the healthy direction.
coord.parallel.Parallel uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break coord.parallel.Parallel, while a change to coord.parallel.Parallel can't break coord.CoordinateSystem.
Position
Below the diagonal: coord.parallel.Parallel uses a module listed above it, which is the healthy direction.
coord.parallel.Parallel uses data.SeriesData, so a change to data.SeriesData can break coord.parallel.Parallel, while a change to coord.parallel.Parallel can't break data.SeriesData.
Position
Below the diagonal: coord.parallel.Parallel uses a module listed above it, which is the healthy direction.
util uses component.axisPointer.globalListener, so a change to component.axisPointer.globalListener can break util, while a change to util can't break component.axisPointer.globalListener.
Position
Below the diagonal: util uses a module listed above it, which is the healthy direction.
chart.chord.ChordSeries uses model.Series, so a change to model.Series can break chart.chord.ChordSeries, while a change to chart.chord.ChordSeries can't break model.Series.
Position
Below the diagonal: chart.chord.ChordSeries uses a module listed above it, which is the healthy direction.
chart.chord.ChordSeries uses model.Global, so a change to model.Global can break chart.chord.ChordSeries, while a change to chart.chord.ChordSeries can't break model.Global.
Position
Below the diagonal: chart.chord.ChordSeries uses a module listed above it, which is the healthy direction.
chart.chord.ChordSeries uses util.types, so a change to util.types can break chart.chord.ChordSeries, while a change to chart.chord.ChordSeries can't break util.types.
Position
Below the diagonal: chart.chord.ChordSeries uses a module listed above it, which is the healthy direction.
chart.chord.ChordSeries uses data.SeriesData, so a change to data.SeriesData can break chart.chord.ChordSeries, while a change to chart.chord.ChordSeries can't break data.SeriesData.
Position
Below the diagonal: chart.chord.ChordSeries uses a module listed above it, which is the healthy direction.
chart.chord.ChordSeries uses data.Graph, so a change to data.Graph can break chart.chord.ChordSeries, while a change to chart.chord.ChordSeries can't break data.Graph.
Position
Below the diagonal: chart.chord.ChordSeries uses a module listed above it, which is the healthy direction.
chart.helper uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break chart.helper, while a change to chart.helper can't break coord.CoordinateSystem.
Position
Below the diagonal: chart.helper uses a module listed above it, which is the healthy direction.
chart.helper uses chart.helper.baseDraw, so a change to chart.helper.baseDraw can break chart.helper, while a change to chart.helper can't break chart.helper.baseDraw.
Position
Below the diagonal: chart.helper uses a module listed above it, which is the healthy direction.
chart.helper uses coord.cartesian.Cartesian2D, so a change to coord.cartesian.Cartesian2D can break chart.helper, while a change to chart.helper can't break coord.cartesian.Cartesian2D.
Position
Below the diagonal: chart.helper uses a module listed above it, which is the healthy direction.
chart.helper uses chart.helper.LineDraw, so a change to chart.helper.LineDraw can break chart.helper, while a change to chart.helper can't break chart.helper.LineDraw.
Position
Below the diagonal: chart.helper uses a module listed above it, which is the healthy direction.
chart.helper uses chart.helper.SymbolDraw, so a change to chart.helper.SymbolDraw can break chart.helper, while a change to chart.helper can't break chart.helper.SymbolDraw.
Position
Below the diagonal: chart.helper uses a module listed above it, which is the healthy direction.
chart.line.LineView uses core.ExtensionAPI, so a change to core.ExtensionAPI can break chart.line.LineView, while a change to chart.line.LineView can't break core.ExtensionAPI.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses model.Model, so a change to model.Model can break chart.line.LineView, while a change to chart.line.LineView can't break model.Model.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses view.Chart, so a change to view.Chart can break chart.line.LineView, while a change to chart.line.LineView can't break view.Chart.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses model.Global, so a change to model.Global can break chart.line.LineView, while a change to chart.line.LineView can't break model.Global.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses util.types, so a change to util.types can break chart.line.LineView, while a change to chart.line.LineView can't break util.types.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break chart.line.LineView, while a change to chart.line.LineView can't break coord.CoordinateSystem.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses coord.cartesian.Cartesian2D, so a change to coord.cartesian.Cartesian2D can break chart.line.LineView, while a change to chart.line.LineView can't break coord.cartesian.Cartesian2D.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses data.SeriesData, so a change to data.SeriesData can break chart.line.LineView, while a change to chart.line.LineView can't break data.SeriesData.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
chart.line.LineView uses chart.helper.SymbolDraw, so a change to chart.helper.SymbolDraw can break chart.line.LineView, while a change to chart.line.LineView can't break chart.helper.SymbolDraw.
Position
Below the diagonal: chart.line.LineView uses a module listed above it, which is the healthy direction.
component.marker uses core.ExtensionAPI, so a change to core.ExtensionAPI can break component.marker, while a change to component.marker can't break core.ExtensionAPI.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
component.marker uses model.Series, so a change to model.Series can break component.marker, while a change to component.marker can't break model.Series.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
component.marker uses model.Global, so a change to model.Global can break component.marker, while a change to component.marker can't break model.Global.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
component.marker uses coord.CoordinateSystem, so a change to coord.CoordinateSystem can break component.marker, while a change to component.marker can't break coord.CoordinateSystem.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
component.marker uses data.SeriesData, so a change to data.SeriesData can break component.marker, while a change to component.marker can't break data.SeriesData.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
component.marker uses component.marker.MarkerModel, so a change to component.marker.MarkerModel can break component.marker, while a change to component.marker can't break component.marker.MarkerModel.
Position
Below the diagonal: component.marker uses a module listed above it, which is the healthy direction.
export.option uses chart.map.MapSeries, so a change to chart.map.MapSeries can break export.option, while a change to export.option can't break chart.map.MapSeries.
Position
Below the diagonal: export.option uses a module listed above it, which is the healthy direction.
export.option uses chart.chord.ChordSeries, so a change to chart.chord.ChordSeries can break export.option, while a change to export.option can't break chart.chord.ChordSeries.
Position
Below the diagonal: export.option uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Weak · gated by D2, R2, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
41
High / Critical
A05:2025 — Injection
27
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Begin by resolving oversized project cohesion and fixing the extensive cross-package import violations to establish clear architectural boundaries. Next, break existing circular imports by extracting shared logic into independent modules, and address commented-out assertions in test files to improve code reliability. Finally, integrate static analysis and security scanning into the continuous integration pipeline to prevent regressions from reaching production.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 52
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.
Serious — 988
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.
Minor — 397
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 17
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 68 of 68 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 68 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 1413 of 1437 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/terser/-/terser-5.46.0.tgz), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/terser/-/terser-5.46.0.tgz), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the dependency install for the repository root could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/terser/-/terser-5.46.0.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
AC1 Text alternatives — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC2 Forms & labels — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC3 Page structure — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC4 Keyboard semantics — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC5 ARIA correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC6 Visual & motion safety — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AC7 A11y enforcement — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 25 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 120 further occurrence(s) are not listed individually; the score already reflects all 160.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 716 further occurrence(s) are not listed individually; the score already reflects all 756.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 391 further occurrence(s) are not listed individually; the score already reflects all 431.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 646 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
Repo exclusion declarations: 33 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
142 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was createDimensions.prepareSeriesDataSchema at 56. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being sectorLabel.setSectorTextRotation at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/label/sectorLabel.ts (sectorLabel.setSectorTextRotation at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 137 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 21 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with createDimensions.prepareSeriesDataSchema (cyclomatic 56), labelStyle.setTokenTextStyle (cyclomatic 54), TreemapView.renderNode (cyclomatic 54). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 21 together lifts Cyclomatic Complexity from 5.7 to about 6.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 207 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 60 down to 60 or less in Cognitive Complexity — start with labelStyle.setTokenTextStyle (cognitive 83), backwardCompat.globalBackwardCompat (cognitive 81), Time.createIntervalTicks (cognitive 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cognitive Complexity from 3.5 to about 4.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 22 FileTooLong finding(s) in God Classes — start with echarts.ts, AxisBuilder.ts, LineView.ts. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 17 FunctionTooLong finding(s) in God Classes — start with funnelLayout.ts (2), TreemapView.ts, CustomView.ts. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 11 MethodTooLong finding(s) in God Classes — start with GaugeView.ts (2), BarView.ts, LineView.ts. — One of this dimension's main actionable groups (11 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with Series.ts, VisualMapModel.ts, TreemapSeries.ts. — One of this dimension's main actionable groups (8 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
567 test methods: 567 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 567 `it`/`test` case(s) across 26 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 567 tests.
Assertions commented out: large numbertest/ut/spec/util/number.test.ts:935
What to do
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with number.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
1 outdated direct production npm dependency(ies) of 2 graded, 0 pinning defect(s), across 3 REDACTED (1 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: dtslint · ×2REDACTED:97
Deprecated: abab · ×13REDACTED:2773
Outdated (npm): tslib
What to do
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 2 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 2 production dependency(ies) this repository's committed lockfile resolves, across 1 product REDACTED manifest(s). Its 42 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ 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. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
50 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/util/model.ts. Counted over 406 of the 645 production source files in this repository: 193 are under the ~2,400-byte size floor this dimension measures over, and the remaining 46 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
419 deducted task-comment markers across 122455 LoC (0.3/KLoC) → score 9.3. 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.
TodoComment · ×230src/echarts.ts:30
FixmeComment · ×118ssr/client/src/index.ts:20
FixmeComment repeated across 32 filessrc/visual/VisualMapping.ts:484
TodoComment repeated across 23 filessrc/visual/style.ts:86
HackCommentsrc/model/Component.ts:387
What to do
Resolve the 230 TodoComment finding(s) in Explicit Debt — start with echarts.ts (12), universalTransition.ts (11), types.ts (9). — One of this dimension's main actionable groups (230 warning-level).
Resolve the 118 FixmeComment finding(s) in Explicit Debt — start with MapDraw.ts (5), Series.ts (4), CoordinateSystem.ts (4). — One of this dimension's main actionable groups (118 warning-level).
Resolve the 1 FixmeComment repeated across 32 files finding(s) in Explicit Debt — start with VisualMapping.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.2 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
42 % of calls cross a namespace and 13 % go through an interface, but 45 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
27 finding(s): 0 critical, 24 high, 3 medium, 0 low. 23 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 23 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (23 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
315 of 452 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/chart/treemap/TreemapView.ts. Counted over 452 of the 645 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3src/chart/treemap/TreemapView.ts:1
Concentrated knowledge decay
What to do
Resolve the 312 Orphaned file finding(s) in Knowledge Freshness — start with install.ts (8), helper.ts (5), visualEncoding.ts (2). — One of this dimension's main actionable groups (312 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with TreemapView.ts, states.ts, SliderTimelineView.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with mapDataStatistic.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with MapView.ts, boxplotLayout.ts, BarSeries.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`Map` declares 19 required operations: `pointToOverlayPixel`, `overlayPixelToPoint`, `getPanes`, `getCenter`, `getZoom`, `addOverlay`, `centerAndZoom`, `addEventListener`, `removeEventListener`, `enableDragging`, `disableDragging`, `enableScrollWheelZoom`, `disableScrollWheelZoom`, `enableDoubleClickZoom`, `disableDoubleClickZoom`, `enablePinchToZoom`, `disablePinchToZoom`, `setMapStyle`, `setMapStyleV2`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — extension-src/bmap/BMapCoordSys.ts:36
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×8) — extension-src/dataTool/gexf.ts:20, extension-src/dataTool/index.ts:20, src/chart/helper/multipleGraphEdgeHelper.ts:20, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
107 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 10454 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety9.3 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
35 duplicated blocks under src/chart/ have copies in at least two of the sibling directories bar, boxplot, candlestick, chord, custom, effectScatter (+16 more sibling(s) not listed) — 19 of them are reported below, and 16 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 35 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/chart/chord/ChordSeries.ts:152
18 duplicated blocks under src/ have copies in at least two of the sibling directories chart, component, coord, core, data, label (+5 more sibling(s) not listed) — 11 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/chart/graph/categoryFilter.ts:29
8 duplicated blocks under src/coord/ have copies in at least two of the sibling directories calendar, cartesian, matrix, parallel, polar, radar (+1 more sibling(s) not listed) — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/coord/calendar/prepareCustom.ts:41
src/chart/chord/ChordSeries.ts:152 · src/chart/graph/GraphSeries.ts:187 — the two spans are one implementation copied and then locally edited — 618 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. — src/chart/chord/ChordSeries.ts:152
src/component/axis/CartesianAxisView.ts:90 · src/component/axis/SingleAxisView.ts:81 — the two spans are one implementation copied and then locally edited — 416 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. — src/component/axis/CartesianAxisView.ts:90
src/chart/sunburst/SunburstSeries.ts:187 · src/chart/treemap/TreemapSeries.ts:395 — the two spans are one implementation copied and then locally edited — 351 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. — src/chart/sunburst/SunburstSeries.ts:187
theme/dark-blue.js:20 · theme/dark-bold.js:20 · theme/dark-digerati.js:20 · theme/dark-fresh-cut.js:20 · +1 more site(s) not listed — the 5 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 5 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. — theme/dark-blue.js:20
theme/cool.js:20 · theme/tech-blue.js:20 — 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. — theme/cool.js:20
src/component/axisPointer/CartesianAxisPointer.ts:149 · src/component/axisPointer/SingleAxisPointer.ts:136 — 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. — src/component/axisPointer/CartesianAxisPointer.ts:149
src/util/KDTree.ts:120 · src/util/KDTree.ts:225 — the two spans are one implementation copied and then locally edited — 268 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. — src/util/KDTree.ts:120
theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +12 more site(s) not listed — the 16 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 16 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. — theme/azul.js:20
theme/cool.js:20 · theme/mint.js:20 · theme/sakura.js:20 · theme/tech-blue.js:20 — the 4 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 4 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. — theme/cool.js:20
theme/helianthus.js:20 · theme/infographic.js:20 · theme/macarons.js:20 · theme/macarons2.js:20 · +1 more site(s) not listed — the 5 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 5 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. — theme/helianthus.js:20
theme/cool.js:20 · theme/mint.js:20 · theme/sakura.js:20 · theme/tech-blue.js:20 · +1 more site(s) not listed — the 5 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 5 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. — theme/cool.js:20
theme/dark-blue.js:81 · theme/dark-bold.js:81 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — theme/dark-blue.js:81
theme/dark-blue.js:118 · theme/dark-bold.js:118 · theme/dark-digerati.js:118 · theme/dark-fresh-cut.js:118 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — theme/dark-blue.js:118
src/chart/helper/LineDraw.ts:125 · src/chart/helper/SymbolDraw.ts:270 — the two spans are one implementation copied and then locally edited — 124 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. — src/chart/helper/LineDraw.ts:125
src/chart/treemap/TreemapView.ts:874 · src/chart/treemap/TreemapView.ts:932 — the two spans are one implementation copied and then locally edited — 167 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. — src/chart/treemap/TreemapView.ts:874
theme/dark.js:20 · theme/v5.js:20 — the two spans are one implementation copied and then locally edited — 149 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. — theme/dark.js:20
src/component/calendar/CalendarView.ts:381 · src/component/calendar/CalendarView.ts:483 — the two spans are one implementation copied and then locally edited — 101 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. — src/component/calendar/CalendarView.ts:381
src/visual/visualSolution.ts:143 · src/visual/visualSolution.ts:204 — the two spans are one implementation copied and then locally edited — 200 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. — src/visual/visualSolution.ts:143
src/component/marker/MarkLineView.ts:435 · src/component/marker/MarkPointView.ts:192 — 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. — src/component/marker/MarkLineView.ts:435
theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +25 more site(s) not listed — the 29 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 29 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. — theme/azul.js:20
src/chart/funnel/FunnelSeries.ts:110 · src/chart/pie/PieSeries.ts:158 — the two spans are one implementation copied and then locally edited — 152 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. — src/chart/funnel/FunnelSeries.ts:110
src/chart/helper/LargeLineDraw.ts:185 · src/chart/helper/LargeSymbolDraw.ts:192 — 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. — src/chart/helper/LargeLineDraw.ts:185
src/chart/sankey/sankeyLayout.ts:426 · src/chart/sankey/sankeyLayout.ts:491 — 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. — src/chart/sankey/sankeyLayout.ts:426
src/component/axisPointer/CartesianAxisPointer.ts:85 · src/component/axisPointer/SingleAxisPointer.ts:89 — 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. — src/component/axisPointer/CartesianAxisPointer.ts:85
theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +32 more site(s) not listed — the 36 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 36 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. — theme/azul.js:20
src/label/labelGuideHelper.ts:411 · src/label/labelGuideHelper.ts:467 — 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. — src/label/labelGuideHelper.ts:411
src/layout/barGrid.ts:265 · src/layout/barPolar.ts:262 — the two spans are one implementation copied and then locally edited — 146 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. — src/layout/barGrid.ts:265
src/component/tooltip/TooltipHTMLContent.ts:498 · src/component/tooltip/TooltipRichContent.ts:170 — the two spans are one implementation copied and then locally edited — 128 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. — src/component/tooltip/TooltipHTMLContent.ts:498
REDACTED:73 · src/visual/style.ts:180 — the two spans are one implementation copied and then locally edited — 134 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. — REDACTED:73
extension-src/dataTool/prepareBoxplotData.ts:81 · src/chart/boxplot/prepareBoxplotData.ts:61 — the two spans are one implementation copied and then locally edited — 182 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extension-src/dataTool/prepareBoxplotData.ts:81
src/chart/funnel/funnelLayout.ts:351 · src/chart/funnel/funnelLayout.ts:372 — 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. — src/chart/funnel/funnelLayout.ts:351
src/chart/graph/categoryFilter.ts:29 · src/processor/dataFilter.ts:25 — the two spans are one implementation copied and then locally edited — 84 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. — src/chart/graph/categoryFilter.ts:29
src/chart/lines/LinesSeries.ts:369 · src/chart/scatter/ScatterSeries.ts:95 — 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. — src/chart/lines/LinesSeries.ts:369
src/chart/pie/pieLayout.ts:173 · src/chart/pie/pieLayout.ts:198 — the two spans are one implementation copied and then locally edited — 85 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/chart/pie/pieLayout.ts:173
src/util/number.ts:636 · src/util/number.ts:653 — 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. — src/util/number.ts:636
src/chart/line/LineView.ts:734 · src/chart/line/LineView.ts:754 — the two spans are one implementation copied and then locally edited — 76 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. — src/chart/line/LineView.ts:734
src/component/axisPointer/CartesianAxisPointer.ts:53 · src/component/axisPointer/SingleAxisPointer.ts:57 — 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. — src/component/axisPointer/CartesianAxisPointer.ts:53
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.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
extension-src/dataTool/gexf.ts:28 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — extension-src/dataTool/gexf.ts:28
src/animation/basicTransition.ts:28 imports zrender/src/animation/easing, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/basicTransition.ts:28
src/animation/basicTransition.ts:29 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/basicTransition.ts:29
src/animation/basicTransition.ts:31 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/basicTransition.ts:31
src/animation/basicTransition.ts:36 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/basicTransition.ts:36
src/animation/basicTransition.ts:37 imports zrender/src/graphic/Group, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/basicTransition.ts:37
src/animation/customGraphicKeyframeAnimation.ts:20 imports zrender/src/animation/easing, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicKeyframeAnimation.ts:20
src/animation/customGraphicKeyframeAnimation.ts:21 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicKeyframeAnimation.ts:21
src/animation/customGraphicKeyframeAnimation.ts:22 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicKeyframeAnimation.ts:22
src/animation/customGraphicTransition.ts:21 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:21
src/animation/customGraphicTransition.ts:24 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:24
src/animation/customGraphicTransition.ts:25 imports zrender/src/animation/Animator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:25
src/animation/customGraphicTransition.ts:26 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:26
src/animation/customGraphicTransition.ts:32 imports zrender/src/core/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:32
src/animation/customGraphicTransition.ts:33 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:33
src/animation/customGraphicTransition.ts:34 imports zrender/src/core/Transformable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/customGraphicTransition.ts:34
src/animation/morphTransitionHelper.ts:20 imports zrender/src/tool/morphPath, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/morphTransitionHelper.ts:20
src/animation/morphTransitionHelper.ts:30 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/morphTransitionHelper.ts:30
src/animation/morphTransitionHelper.ts:31 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/morphTransitionHelper.ts:31
src/animation/morphTransitionHelper.ts:34 imports zrender/src/tool/path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/morphTransitionHelper.ts:34
src/animation/universalTransition.ts:23 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/universalTransition.ts:23
src/animation/universalTransition.ts:24 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/universalTransition.ts:24
src/animation/universalTransition.ts:26 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/universalTransition.ts:26
src/animation/universalTransition.ts:49 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/animation/universalTransition.ts:49
src/chart/bar/BarView.ts:20 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:20
src/chart/bar/BarView.ts:21 imports zrender/src/graphic/Group, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:21
src/chart/bar/BarView.ts:22 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:22
src/chart/bar/BarView.ts:23 imports zrender/src/core/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:23
src/chart/bar/BarView.ts:24 imports zrender/src/graphic/shape/Sector, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:24
src/chart/bar/BarView.ts:25 imports zrender/src/graphic/shape/Rect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:25
src/chart/bar/BarView.ts:66 imports zrender/src/core/Eventful, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:66
src/chart/bar/BarView.ts:70 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BarView.ts:70
src/chart/bar/BaseBarSeries.ts:34 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/BaseBarSeries.ts:34
src/chart/bar/PictorialBarView.ts:20 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/PictorialBarView.ts:20
src/chart/bar/PictorialBarView.ts:37 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/PictorialBarView.ts:37
src/chart/bar/PictorialBarView.ts:39 imports zrender/src/graphic/Image, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/bar/PictorialBarView.ts:39
src/chart/boxplot/BoxplotSeries.ts:36 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/boxplot/BoxplotSeries.ts:36
src/chart/boxplot/BoxplotView.ts:23 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/boxplot/BoxplotView.ts:23
src/chart/boxplot/BoxplotView.ts:36 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/boxplot/BoxplotView.ts:36
src/chart/boxplot/boxplotLayout.ts:20 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/chart/boxplot/boxplotLayout.ts:20
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
setTokenTextStyle has cyclomatic complexity 54 and cognitive complexity 84; 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. — src/label/labelStyle.ts:533
render has cyclomatic complexity 49 and cognitive complexity 68; 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. — src/chart/line/LineView.ts:635
beforeUpdate has cyclomatic complexity 49 and cognitive complexity 58; 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. — src/chart/helper/Line.ts:358
constructor has cyclomatic complexity 49 and cognitive complexity 55; 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. — src/coord/scaleRawExtentInfo.ts:180
(anonymous) has cyclomatic complexity 42 and cognitive complexity 77; 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. — src/preprocessor/backwardCompat.ts:150
doGuessOrdinal has cyclomatic complexity 35 and cognitive complexity 62; 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. — src/data/helper/sourceHelper.ts:354
(anonymous) has cyclomatic complexity 34 and cognitive complexity 73; 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. — src/chart/funnel/funnelLayout.ts:58
(anonymous) has cyclomatic complexity 34 and cognitive complexity 58; 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. — src/chart/pie/labelLayout.ts:382
(anonymous) has cyclomatic complexity 34 and cognitive complexity 49; 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. — src/component/graphic/GraphicView.ts:125
perform has cyclomatic complexity 31 and cognitive complexity 46; 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. — src/core/task.ts:139
scaleCalcAlign has cyclomatic complexity 30 and cognitive complexity 42; 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. — src/coord/axisAlignTicks.ts:44
(anonymous) has cyclomatic complexity 30 and cognitive complexity 40; 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. — src/chart/sunburst/SunburstPiece.ts:185
_layout has cyclomatic complexity 30 and cognitive complexity 34; 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. — src/component/timeline/SliderTimelineView.ts:166
selectRange has cyclomatic complexity 29 and cognitive complexity 57; 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. — src/data/DataStore.ts:667
_renderOnGridLike has cyclomatic complexity 29 and cognitive complexity 42; 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. — src/chart/heatmap/HeatmapView.ts:164
updateNode has cyclomatic complexity 28 and cognitive complexity 49; 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. — src/chart/tree/TreeView.ts:327
createMatrixCell has cyclomatic complexity 28 and cognitive complexity 36; 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. — src/component/matrix/MatrixView.ts:261
convertToEC4RichItem has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/util/styleCompat.ts:214
getLayoutRect has cyclomatic complexity 27 and cognitive complexity 29; 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. — src/util/layout.ts:263
prepareSeriesDataSchema has cyclomatic complexity 26 and cognitive complexity 34; 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. — src/data/helper/createDimensions.ts:100
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files4.7 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
src/core/echarts.ts has 2972 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/echarts.ts:1
src/util/types.ts has 1960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/util/types.ts:1
src/component/axis/AxisBuilder.ts has 1450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/axis/AxisBuilder.ts:1
src/chart/custom/CustomView.ts has 1353 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/custom/CustomView.ts:1
src/data/SeriesData.ts has 1321 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/data/SeriesData.ts:1
src/util/model.ts has 1314 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/util/model.ts:1
src/chart/line/LineView.ts has 1293 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/line/LineView.ts:1
src/data/DataStore.ts has 1156 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/data/DataStore.ts:1
src/chart/bar/BarView.ts has 1139 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/bar/BarView.ts:1
src/component/tooltip/TooltipView.ts has 1120 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/tooltip/TooltipView.ts:1
src/model/Global.ts has 976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/model/Global.ts:1
src/component/helper/BrushController.ts has 974 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/helper/BrushController.ts:1
src/component/dataZoom/SliderZoomView.ts has 972 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/dataZoom/SliderZoomView.ts:1
src/chart/treemap/TreemapView.ts has 969 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/treemap/TreemapView.ts:1
src/coord/cartesian/Grid.ts has 945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/coord/cartesian/Grid.ts:1
src/util/graphic.ts has 908 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/util/graphic.ts:1
src/component/visualMap/ContinuousView.ts has 864 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/visualMap/ContinuousView.ts:1
src/coord/View.ts has 833 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/coord/View.ts:1
src/chart/bar/PictorialBarView.ts has 821 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/bar/PictorialBarView.ts:1
src/util/states.ts has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/util/states.ts:1
src/label/labelStyle.ts has 781 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/label/labelStyle.ts:1
src/util/number.ts has 770 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/util/number.ts:1
src/component/helper/MapDraw.ts has 769 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/helper/MapDraw.ts:1
src/coord/scaleRawExtentInfo.ts has 769 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/coord/scaleRawExtentInfo.ts:1
src/component/timeline/SliderTimelineView.ts has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/timeline/SliderTimelineView.ts:1
src/model/Series.ts has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/model/Series.ts:1
src/animation/universalTransition.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/animation/universalTransition.ts:1
src/scale/breakImpl.ts has 721 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scale/breakImpl.ts:1
src/util/layout.ts 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. — src/util/layout.ts:1
src/scale/Time.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/scale/Time.ts:1
src/chart/tree/TreeView.ts has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/tree/TreeView.ts:1
src/component/legend/LegendView.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/legend/LegendView.ts:1
src/visual/VisualMapping.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/visual/VisualMapping.ts:1
src/chart/gauge/GaugeView.ts has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/gauge/GaugeView.ts:1
src/chart/treemap/treemapLayout.ts has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/chart/treemap/treemapLayout.ts:1
src/core/Scheduler.ts has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/Scheduler.ts:1
src/component/visualMap/VisualMapModel.ts has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/component/visualMap/VisualMapModel.ts:1
src/animation/customGraphicTransition.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/animation/customGraphicTransition.ts:1
src/label/labelGuideHelper.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/label/labelGuideHelper.ts:1
src/coord/matrix/Matrix.ts has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/coord/matrix/Matrix.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage2.7 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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) — src/chart/custom/CustomView.ts:1, src/chart/line/LineView.ts:1, src/chart/bar/BarView.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
605 file(s) (~139228 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: index.d.ts imports './types/dist/echarts', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. (×4) — extension-src/bmap/BMapCoordSys.ts:118, extension-src/bmap/BMapCoordSys.ts:119, src/chart/parallel/ParallelView.ts:51, …
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×7) — src/component/legend/ScrollableLegendView.ts:82, src/component/timeline/SliderTimelineView.ts:92, src/core/echarts.ts:1668, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×2) — theme/tool/thumb.js:20, theme/tool/thumb.js:21
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
src/core/Scheduler.ts → src/core/task.ts → src/core/Scheduler.ts (one verified cycle inside a mutually-dependent group of 81 files) — src/core/Scheduler.ts:21
src/chart/helper/createSeriesData.ts → src/model/referHelper.ts → src/chart/parallel/ParallelSeries.ts → src/chart/helper/createSeriesData.ts (one verified cycle inside a mutually-dependent group of 7 files) — src/chart/helper/createSeriesData.ts:26
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.5 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`lang[0]||model.get('title')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/toolbox/feature/DataView.ts:344
`htmlOrDom` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/toolbox/feature/DataView.ts:358
`lang[1]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/toolbox/feature/DataView.ts:432
`lang[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/toolbox/feature/DataView.ts:433
`((lang&&lang[0])||'')` is text this program did not author, and it is written into a quoted attribute value through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/toolbox/feature/SaveAsImage.ts:119
`content+arrow` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/component/tooltip/TooltipHTMLContent.ts:453
`item.dom` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/echarts.ts:1078
`encodeHTML(color)` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. (×2) — src/util/format.ts:207, src/util/format.ts:210
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. — src/core/Scheduler.ts:652
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.1 `!` null assertions per 1k TypeScript source lines — 8 assertion(s) across the 140053 source line(s) of the 603 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: src/component/axis/axisBreakHelperImpl.ts (6), src/component/axis/AxisBuilder.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
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 `?`).
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC2 Forms & labels — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC3 Page structure — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC4 Keyboard semantics — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC5 ARIA correctness — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC6 Visual & motion safety — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AC7 A11y enforcement — Frontend markup is constructed programmatically — 25 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 13 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
AX1 Captive dependencies — Not applicable: this repository's JavaScript 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.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks. 9 claim(s) of kinds M4 does not check were not checked (path 1, command argument 7, install 1); M4 checks only links and versions.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JavaScript/TypeScript source (2 module(s), 639 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
S1 Web-Security Posture — Not assessed: 646 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Assertions commented out: large number test/ut/spec/util/number.test.ts:935— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Boundary-crossing change coupling: mapDataStatistic.ts ↔ geoCreator.ts src/chart/map/mapDataStatistic.ts:1— `src/chart/map/mapDataStatistic.ts` (context chart) and `src/coord/geo/geoCreator.ts` (context coord) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `21f17bec` fixRegression(map,geo): Resolve circular dependencies introduced by t…; `278bfa26` When using object hash map, we should avoid conflition with props on … (at that commit the files were still `src/chart/map/mapDataStatistic.js` and `src/coord/geo/geoCreator.js`); `4fca3d18` [geo] enable map and scatter share a geo. (change geo color) (at that commit the files were still `src/chart/map/mapDataStatistic.js` and `src/coord/geo/geoCreator.js`) — run `git show` on any of them.
TodoComment src/echarts.ts:30— // TODO: Compatitable with the following code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/echarts.ts:44— // TODO remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/extension.ts:70— // TODO Use ComponentModel and SeriesModel instead of Constructor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/visual/VisualMapping.ts:638— // TODO {}? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:140— // TODO: support for SSR — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/visual/style.ts:90— // TODO style callback — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/visual/style.ts:99— // TODO series count changed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/graphic.ts:901— // TODO if el.emphasis.z2 is spcefied, what about textContent. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/innerStore.ts:71— // TODO: not store dataIndex on children. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/model.ts:1400— // TODO: modDataCount should not updated if `appendData`, otherwise cause whole repaint. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:269— // TODO Share with textContent? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:288— // TODO Share with textContent? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:478— // TODO blurScope: coordinate system — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:579— // TODO Should put it on seriesModel? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:662— // TODO. progressive mode. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/states.ts:781— // TODO dataIndex may be set after this function. This check is not useful. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/symbol.ts:177— // TODO Use function to build symbol path. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/symbol.ts:317— // TODO Same width with lineStyle in LineView — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/symbol.ts:343— // TODO Support image object, DynamicImage. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/symbol.ts:380— // TODO Should deprecate setColor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/types.ts:173— // TODO use unknown — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/types.ts:270— // TODO use unknown — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/types.ts:275— // TODO use unknown — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/types.ts:956— // TODO: TYPE Different callback param for different series — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/util/types.ts:1218— // TODO: TYPE value type? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ssr/client/src/index.ts:20— // FIXME: use only one definition with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/view/Chart.ts:204— // FIXME never used? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/view/Chart.ts:209— // FIXME never used? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/view/Chart.ts:280— // FIXME: remove updateView updateVisual — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/clazz.ts:79— // FIXME: not necessary? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/clazz.ts:357— // FIXME It seems broken in IE8 simulation of IE11 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/graphic.ts:450— // FIXME: This way might be incorrect when graphic clipped by a corner — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/graphic.ts:854— // FIXME: Ideally all the labels should be above all the glyphs by default, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/layout.ts:103— // FIXME compare before adding gap? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/layout.ts:111— // FIXME: consider rect.y is not `0`? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/model.ts:142— // // FIXME: deprecated, check and remove it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/types.ts:306— // - `ComponentMainType.ComponentSubType:ECUpdateMethodName`: (FIXME: Not a rigorous mechanism!) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/util/types.ts:891— // FIXME: In some case (markpoint in geo (geo-map.html)), dataItem is {coord: [...]} — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/scale/Interval.ts:135— // FIXME: `ScaleDataValue` also need to be modified to include numeric string type, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/scale/Time.ts:95— // FIXME 公用？ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/chart/map/mapDataStatistic.ts:27— // FIXME 公用？ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/processor/dataFilter.ts:37— // @ts-ignore FIXME: LegendModel — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/processor/dataSample.ts:80— // FIXME:TS never used, so comment it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/model/Series.ts:399— // FIXME:TS never used, so comment it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/core/Scheduler.ts:492— // FIXME:TS never used, so comment it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/core/Scheduler.ts:530— // FIXME:TS never used, so comment it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/model/Component.ts:264— // FIXME: remove this approach? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/model/Model.ts:91— // FIXME:TS consider there is parentModel, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/model/Model.ts:129— // FIXME:TS do not know how to make it works — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/model/Model.ts:204— // FIXME:TS check whether put this method here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Boundary violation [package:third-party-deep-import] extension-src/dataTool/gexf.ts:28— extension-src/dataTool/gexf.ts:28 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/basicTransition.ts:28— src/animation/basicTransition.ts:28 imports zrender/src/animation/easing, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/basicTransition.ts:29— src/animation/basicTransition.ts:29 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/basicTransition.ts:31— src/animation/basicTransition.ts:31 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/basicTransition.ts:36— src/animation/basicTransition.ts:36 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/basicTransition.ts:37— src/animation/basicTransition.ts:37 imports zrender/src/graphic/Group, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicKeyframeAnimation.ts:20— src/animation/customGraphicKeyframeAnimation.ts:20 imports zrender/src/animation/easing, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicKeyframeAnimation.ts:21— src/animation/customGraphicKeyframeAnimation.ts:21 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicKeyframeAnimation.ts:22— src/animation/customGraphicKeyframeAnimation.ts:22 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:21— src/animation/customGraphicTransition.ts:21 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:24— src/animation/customGraphicTransition.ts:24 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:25— src/animation/customGraphicTransition.ts:25 imports zrender/src/animation/Animator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:26— src/animation/customGraphicTransition.ts:26 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:32— src/animation/customGraphicTransition.ts:32 imports zrender/src/core/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:33— src/animation/customGraphicTransition.ts:33 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/customGraphicTransition.ts:34— src/animation/customGraphicTransition.ts:34 imports zrender/src/core/Transformable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/morphTransitionHelper.ts:20— src/animation/morphTransitionHelper.ts:20 imports zrender/src/tool/morphPath, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/morphTransitionHelper.ts:30— src/animation/morphTransitionHelper.ts:30 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/morphTransitionHelper.ts:31— src/animation/morphTransitionHelper.ts:31 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/morphTransitionHelper.ts:34— src/animation/morphTransitionHelper.ts:34 imports zrender/src/tool/path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/universalTransition.ts:23— src/animation/universalTransition.ts:23 imports zrender/src/core/util, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/universalTransition.ts:24— src/animation/universalTransition.ts:24 imports zrender/src/Element, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/universalTransition.ts:26— src/animation/universalTransition.ts:26 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/animation/universalTransition.ts:49— src/animation/universalTransition.ts:49 imports zrender/src/graphic/Displayable, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/chart/bar/BarView.ts:20— src/chart/bar/BarView.ts:20 imports zrender/src/graphic/Path, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file src/chart/custom/CustomView.ts:1— 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.
No test reaches this file src/chart/line/LineView.ts:1— 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.
No test reaches this file src/chart/bar/BarView.ts:1— 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.
No test reaches this file src/component/tooltip/TooltipView.ts:1— 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.
No test reaches this file src/component/dataZoom/SliderZoomView.ts:1— 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.
No test reaches this file src/chart/treemap/TreemapView.ts:1— 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.
No test reaches this file src/component/visualMap/ContinuousView.ts:1— 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.
No test reaches this file src/chart/bar/PictorialBarView.ts:1— 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.
No test reaches this file src/coord/View.ts:1— 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.
No test reaches this file src/component/helper/MapDraw.ts:1— 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.
No test reaches this file src/component/timeline/SliderTimelineView.ts:1— 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.
No test reaches this file src/animation/universalTransition.ts:1— 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.
No test reaches this file src/scale/breakImpl.ts:1— 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.
No test reaches this file src/component/legend/LegendView.ts:1— 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.
No test reaches this file src/chart/tree/TreeView.ts:1— 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.
No test reaches this file src/chart/gauge/GaugeView.ts:1— 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.
No test reaches this file src/chart/treemap/treemapLayout.ts:1— 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.
No test reaches this file src/chart/treemap/TreemapSeries.ts:1— 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.
No test reaches this file src/data/Graph.ts:1— 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.
No test reaches this file src/chart/pie/labelLayout.ts:1— 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.
No test reaches this file src/component/helper/RoamController.ts:1— 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.
No test reaches this file theme/v5.js:1— 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.
No test reaches this file src/component/axisPointer/BaseAxisPointer.ts:1— 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.
No test reaches this file src/coord/calendar/Calendar.ts:1— 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.
No test reaches this file src/component/axis/axisBreakHelperImpl.ts:1— 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.
FileTooLong: core/echarts.ts src/core/echarts.ts— FileTooLong — 1888 significant lines (blank, comment-only and punctuation-only lines excluded), about 69% of them inside a single declaration: ECharts (454-2843). The bar is 500 significant lines; this is 1388 over it, 3.78× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: axis/AxisBuilder.ts src/component/axis/AxisBuilder.ts— FileTooLong — 981 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 481 over it, 1.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: line/LineView.ts src/chart/line/LineView.ts— FileTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: LineView (599-1468). The bar is 500 significant lines; this is 416 over it, 1.83× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: util/types.ts src/util/types.ts— FileTooLong — 906 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 406 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: custom/CustomView.ts src/chart/custom/CustomView.ts— FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 382 over it, 1.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bar/BarView.ts src/chart/bar/BarView.ts— FileTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 348 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tooltip/TooltipView.ts src/component/tooltip/TooltipView.ts— FileTooLong — 782 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: TooltipView (138-1061). The bar is 500 significant lines; this is 282 over it, 1.56× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: data/SeriesData.ts src/data/SeriesData.ts— FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: SeriesData (152-1500). The bar is 500 significant lines; this is 242 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: data/DataStore.ts src/data/DataStore.ts— FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: DataStore (162-1344). The bar is 500 significant lines; this is 238 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: util/model.ts src/util/model.ts— FileTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 233 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dataZoom/SliderZoomView.ts src/component/dataZoom/SliderZoomView.ts— FileTooLong — 731 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: SliderZoomView (89-1128). The bar is 500 significant lines; this is 231 over it, 1.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: helper/BrushController.ts src/component/helper/BrushController.ts— FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 173 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: treemap/TreemapView.ts src/chart/treemap/TreemapView.ts— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 164 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: visualMap/ContinuousView.ts src/component/visualMap/ContinuousView.ts— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: ContinuousView (92-986). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: bar/PictorialBarView.ts src/chart/bar/PictorialBarView.ts— FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/Global.ts src/model/Global.ts— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: GlobalModel (156-958). The bar is 500 significant lines; this is 90 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: cartesian/Grid.ts src/coord/cartesian/Grid.ts— FileTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 86 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: timeline/SliderTimelineView.ts src/component/timeline/SliderTimelineView.ts— FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: SliderTimelineView (81-735). The bar is 500 significant lines; this is 57 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: util/graphic.ts src/util/graphic.ts— FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 43 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: util/states.ts src/util/states.ts— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: helper/MapDraw.ts src/component/helper/MapDraw.ts— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: gauge/GaugeView.ts src/chart/gauge/GaugeView.ts— FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: GaugeView (76-723). The bar is 500 significant lines; this is 4 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FunctionTooLong: TreemapView.renderNode src/chart/treemap/TreemapView.ts:739— FunctionTooLong — renderNode runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CustomView.makeRenderItem src/chart/custom/CustomView.ts:627— FunctionTooLong — makeRenderItem runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Time.createIntervalTicks src/scale/Time.ts:472— FunctionTooLong — createIntervalTicks runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: labelLayout.pieLabelLayout src/chart/pie/labelLayout.ts:349— FunctionTooLong — pieLabelLayout runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: decal.createOrUpdatePatternFromDecal src/util/decal.ts:51— FunctionTooLong — createOrUpdatePatternFromDecal runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: chordLayout.chordLayout src/chart/chord/chordLayout.ts:39— FunctionTooLong — chordLayout runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: axisAlignTicks.scaleCalcAlign src/coord/axisAlignTicks.ts:44— FunctionTooLong — scaleCalcAlign runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: universalTransition.transitionBetween src/animation/universalTransition.ts:209— FunctionTooLong — transitionBetween runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: createDimensions.prepareSeriesDataSchema src/data/helper/createDimensions.ts:100— FunctionTooLong — prepareSeriesDataSchema runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: axisBreakHelperImpl.rectCoordBuildBreakAxis src/component/axis/axisBreakHelperImpl.ts:102— FunctionTooLong — rectCoordBuildBreakAxis runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: aria.ariaVisual REDACTED:48— FunctionTooLong — ariaVisual runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: funnelLayout.labelLayout src/chart/funnel/funnelLayout.ts:55— FunctionTooLong — labelLayout runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: poly.drawSegment src/chart/line/poly.ts:36— FunctionTooLong — drawSegment runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: pieLayout.pieLayout src/chart/pie/pieLayout.ts:35— FunctionTooLong — pieLayout runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AxisBuilder.buildAxisLabel src/component/axis/AxisBuilder.ts:1346— FunctionTooLong — buildAxisLabel runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TreeView.updateNode src/chart/tree/TreeView.ts:327— FunctionTooLong — updateNode runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: funnelLayout.funnelLayout src/chart/funnel/funnelLayout.ts:252— FunctionTooLong — funnelLayout runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BarView._renderNormal src/chart/bar/BarView.ts:173— MethodTooLong — _renderNormal runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LineView.render src/chart/line/LineView.ts:635— MethodTooLong — render runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SankeyView.render src/chart/sankey/SankeyView.ts:128— MethodTooLong — render runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GaugeView._renderPointer src/chart/gauge/GaugeView.ts:367— MethodTooLong — _renderPointer runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RadarView.render src/chart/radar/RadarView.ts:45— MethodTooLong — render runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HeatmapView._renderOnGridLike src/chart/heatmap/HeatmapView.ts:164— MethodTooLong — _renderOnGridLike runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SliderZoomView._renderHandle src/component/dataZoom/SliderZoomView.ts:549— MethodTooLong — _renderHandle runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Line.beforeUpdate src/chart/helper/Line.ts:358— MethodTooLong — beforeUpdate runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GlobalModel._mergeOption src/model/Global.ts:312— MethodTooLong — _mergeOption runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GaugeView._renderTicks src/chart/gauge/GaugeView.ts:200— MethodTooLong — _renderTicks runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GraphicComponentView._updateElements src/component/graphic/GraphicView.ts:111— MethodTooLong — _updateElements runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium CVE · ×10
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×9
Untrusted text written into markup unescaped src/component/toolbox/feature/DataView.ts:344— `lang[0]||model.get('title')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/component/toolbox/feature/DataView.ts:358— `htmlOrDom` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/component/toolbox/feature/DataView.ts:432— `lang[1]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/component/toolbox/feature/DataView.ts:433— `lang[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/component/toolbox/feature/SaveAsImage.ts:119— `((lang&&lang[0])||'')` is text this program did not author, and it is written into a quoted attribute value through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/component/tooltip/TooltipHTMLContent.ts:453— `content+arrow` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/core/echarts.ts:1078— `item.dom` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/util/format.ts:207— `encodeHTML(color)` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Untrusted text written into markup unescaped src/util/format.ts:210— `encodeHTML(color)` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Low cohesion: SeriesModel (LCOM4 6) src/model/Series.ts:149— SeriesModel's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: VisualMapModel (LCOM4 6) src/component/visualMap/VisualMapModel.ts:179— VisualMapModel's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TreemapSeriesModel (LCOM4 6) src/chart/treemap/TreemapSeries.ts:222— TreemapSeriesModel's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MapSeries (LCOM4 5) src/chart/map/MapSeries.ts:117— MapSeries's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TreeNode (LCOM4 5) src/data/Tree.ts:47— TreeNode's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Radar (LCOM4 4) src/coord/radar/Radar.ts:41— Radar's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SeriesData (LCOM4 4) src/data/SeriesData.ts:152— SeriesData's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Axis (LCOM4 4) src/coord/Axis.ts:60— Axis's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
TooManyMethods: SeriesData src/data/SeriesData.ts:152— TooManyMethods — 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ECharts src/core/echarts.ts:454— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DataStore src/data/DataStore.ts:162— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SeriesModel src/model/Series.ts:149— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GlobalModel src/model/Global.ts:156— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: MapView.ts ↔ mapDataStatistic.ts src/chart/map/MapView.ts:1— `src/chart/map/MapView.ts` and `src/chart/map/mapDataStatistic.ts` change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `21f17bec` fixRegression(map,geo): Resolve circular dependencies introduced by t…; `4fca3d18` [geo] enable map and scatter share a geo. (change geo color) (at that commit the files were still `src/chart/map/MapView.js` and `src/chart/map/mapDataStatistic.js`); `8ea9dfcc` Fix #3436 (at that commit the files were still `src/chart/map/MapView.js` and `src/chart/map/mapDataStatistic.js`) — run `git show` on any of them.
Change coupling: boxplotLayout.ts ↔ candlestickLayout.ts src/chart/boxplot/boxplotLayout.ts:1— `src/chart/boxplot/boxplotLayout.ts` and `src/chart/candlestick/candlestickLayout.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `db12d57a` fix: Enable axis statistics to be able to register -- exclude if unne…; `d2cc085b` tweak: Clarity the previous implements of axis statistics.; `f94f2214` fix: (1) priority of defaults by layout and axis types. (2) init anim… — run `git show` on any of them.
Change coupling: BarSeries.ts ↔ FunnelSeries.ts src/chart/bar/BarSeries.ts:1— `src/chart/bar/BarSeries.ts` and `src/chart/funnel/FunnelSeries.ts` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `7b34b192` fix(theme): update according to the pr review; `66290cc5` [Feature] add borderRadius option to heatmap (#16493); `0779757d` fix(type): fix callback type in itemStyle.color #14279 — run `git show` on any of them.
Duplicated block (22 lines × 2 locations) src/chart/helper/LargeLineDraw.ts:185— src/chart/helper/LargeLineDraw.ts:185 · src/chart/helper/LargeSymbolDraw.ts:192 — 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.
Duplicated block (22 lines × 2 locations) src/chart/sankey/sankeyLayout.ts:426— src/chart/sankey/sankeyLayout.ts:426 · src/chart/sankey/sankeyLayout.ts:491 — 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.
Duplicated block (22 lines × 2 locations) src/component/axisPointer/CartesianAxisPointer.ts:85— src/component/axisPointer/CartesianAxisPointer.ts:85 · src/component/axisPointer/SingleAxisPointer.ts:89 — 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.
Deprecated: dtslint REDACTED:97— dtslint 4.2.1, declared in REDACTED, is marked deprecated by its publisher: "See https://aka.ms/type-testing-tools". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:99— eslint 7.17.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
R10 · Code Duplication· Duplicated block with local edits (28 matched lines × 2 locations) · ×2
Duplicated block with local edits (28 matched lines × 2 locations) src/chart/treemap/TreemapView.ts:874— src/chart/treemap/TreemapView.ts:874 · src/chart/treemap/TreemapView.ts:932 — the two spans are one implementation copied and then locally edited — 167 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.
Duplicated block with local edits (28 matched lines × 2 locations) theme/dark.js:20— theme/dark.js:20 · theme/v5.js:20 — the two spans are one implementation copied and then locally edited — 149 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.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×2
Duplicated block with local edits (26 matched lines × 2 locations) src/component/calendar/CalendarView.ts:381— src/component/calendar/CalendarView.ts:381 · src/component/calendar/CalendarView.ts:483 — the two spans are one implementation copied and then locally edited — 101 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.
Duplicated block with local edits (26 matched lines × 2 locations) src/visual/visualSolution.ts:143— src/visual/visualSolution.ts:143 · src/visual/visualSolution.ts:204 — the two spans are one implementation copied and then locally edited — 200 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.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×2
Duplicated block with local edits (20 matched lines × 2 locations) src/component/tooltip/TooltipHTMLContent.ts:498— src/component/tooltip/TooltipHTMLContent.ts:498 · src/component/tooltip/TooltipRichContent.ts:170 — the two spans are one implementation copied and then locally edited — 128 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.
Duplicated block with local edits (20 matched lines × 2 locations) REDACTED:73— REDACTED:73 · src/visual/style.ts:180 — the two spans are one implementation copied and then locally edited — 134 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.
Duplicated block (17 lines × 2 locations) src/chart/lines/LinesSeries.ts:369— src/chart/lines/LinesSeries.ts:369 · src/chart/scatter/ScatterSeries.ts:95 — 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.
Duplicated block (17 lines × 2 locations) src/util/number.ts:636— src/util/number.ts:636 · src/util/number.ts:653 — 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.
createDimensions.prepareSeriesDataSchema (cyclomatic 56) src/data/helper/createDimensions.ts:100— createDimensions.prepareSeriesDataSchema has cyclomatic complexity 56 (threshold 15). Of this number, 26 points are the body's own statements and 30 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
labelStyle.setTokenTextStyle (cyclomatic 54) src/label/labelStyle.ts:533— labelStyle.setTokenTextStyle has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreemapView.renderNode (cyclomatic 54) src/chart/treemap/TreemapView.ts:739— TreemapView.renderNode has cyclomatic complexity 54 (threshold 15). Of this number, 22 points are the body's own statements and 32 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CustomView.makeRenderItem (cyclomatic 52) src/chart/custom/CustomView.ts:627— CustomView.makeRenderItem has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 11 of the 52 points are its own statements and the rest belongs to 12 function items inside it that branch (style, ordinalRawValue, styleEmphasis, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Line.beforeUpdate (cyclomatic 51) src/chart/helper/Line.ts:358— Line.beforeUpdate has cyclomatic complexity 51 (threshold 15). Of this number, 49 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LineView.render (cyclomatic 51) src/chart/line/LineView.ts:635— LineView.render has cyclomatic complexity 51 (threshold 15). Of this number, 49 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
axisAlignTicks.scaleCalcAlign (cyclomatic 49) src/coord/axisAlignTicks.ts:44— axisAlignTicks.scaleCalcAlign has cyclomatic complexity 49 (threshold 15). Of this number, 30 points are the body's own statements and 19 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScaleRawExtentInfo.constructor (cyclomatic 49) src/coord/scaleRawExtentInfo.ts:180— ScaleRawExtentInfo.constructor has cyclomatic complexity 49 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
labelLayout.pieLabelLayout (cyclomatic 48) src/chart/pie/labelLayout.ts:349— labelLayout.pieLabelLayout has cyclomatic complexity 48 (threshold 15). Most of this is not in the body itself: 12 of the 48 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 382, isLabelShown). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
backwardCompat.globalBackwardCompat (cyclomatic 45) src/preprocessor/backwardCompat.ts:144— backwardCompat.globalBackwardCompat has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 2 of the 45 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 150, 262). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
BarView._renderNormal (cyclomatic 43) src/chart/bar/BarView.ts:173— BarView._renderNormal has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 11 of the 43 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 315, a function literal at line 241, createBackground, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
chordLayout.chordLayout (cyclomatic 42) src/chart/chord/chordLayout.ts:39— chordLayout.chordLayout has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 11 of the 42 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 72, 88, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
sourceHelper.doGuessOrdinal (cyclomatic 41) src/data/helper/sourceHelper.ts:354— sourceHelper.doGuessOrdinal has cyclomatic complexity 41 (threshold 15). Of this number, 35 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
universalTransition.transitionBetween (cyclomatic 41) src/animation/universalTransition.ts:209— universalTransition.transitionBetween has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (updateOneToOne, a function literal at line 492, updateMorphingPathProps, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GraphicComponentView._updateElements (cyclomatic 35) src/component/graphic/GraphicView.ts:111— GraphicComponentView._updateElements has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 125). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
funnelLayout.labelLayout (cyclomatic 34) src/chart/funnel/funnelLayout.ts:55— funnelLayout.labelLayout has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to one function literal inside it that branches (line 58). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
VisualMapModel.completeVisualOption (cyclomatic 33) src/component/visualMap/VisualMapModel.ts:484— VisualMapModel.completeVisualOption has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 573, completeController, a function literal at line 540, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SunburstPiece._updateLabel (cyclomatic 33) src/chart/sunburst/SunburstPiece.ts:163— SunburstPiece._updateLabel has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 185, getLabelAttr). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Task.perform (cyclomatic 32) src/core/task.ts:139— Task.perform has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreeView.updateNode (cyclomatic 32) src/chart/tree/TreeView.ts:327— TreeView.updateNode has cyclomatic complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
aria.ariaVisual (cyclomatic 31) REDACTED:48— aria.ariaVisual has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 10 function items inside it that branch (setLabel, a function literal at line 188, getTitle, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
customGraphicKeyframeAnimation.applyKeyframeAnimation (cyclomatic 30) src/animation/customGraphicKeyframeAnimation.ts:59— customGraphicKeyframeAnimation.applyKeyframeAnimation has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 102, 91, 140). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SliderTimelineView._layout (cyclomatic 30) src/component/timeline/SliderTimelineView.ts:166— SliderTimelineView._layout has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dataStackHelper.enableDataStack (cyclomatic 29) src/data/helper/dataStackHelper.ts:59— dataStackHelper.enableDataStack has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 13 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 115, a function literal at line 104, dimTypeIsNotOrdinalAndTime, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DataStore.selectRange (cyclomatic 29) src/data/DataStore.ts:667— DataStore.selectRange has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HeatmapView._renderOnGridLike (cyclomatic 29) src/chart/heatmap/HeatmapView.ts:164— HeatmapView._renderOnGridLike has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
states.blurSeries (cyclomatic 28) src/util/states.ts:429— states.blurSeries has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 461, a function literal at line 481, a function literal at line 508, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
IntervalScale.getTicks (cyclomatic 28) src/scale/Interval.ts:183— IntervalScale.getTicks has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GlobalModel._mergeOption (cyclomatic 28) src/model/Global.ts:312— GlobalModel._mergeOption has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 397, a function literal at line 327, visitComponent, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
styleCompat.convertToEC4RichItem (cyclomatic 28) src/util/styleCompat.ts:214— styleCompat.convertToEC4RichItem has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MatrixView.createMatrixCell (cyclomatic 28) src/component/matrix/MatrixView.ts:261— MatrixView.createMatrixCell has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sourceHelper.makeSeriesEncodeForNameBased (cyclomatic 27) src/data/helper/sourceHelper.ts:192— sourceHelper.makeSeriesEncodeForNameBased has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 6 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 219, 210, 266). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MatrixBodyCorner._ensureCellMap (cyclomatic 27) src/coord/matrix/MatrixBodyCorner.ts:103— MatrixBodyCorner._ensureCellMap has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (fillCellMap, a function literal at line 130, a function literal at line 200, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
layout.getLayoutRect (cyclomatic 27) src/util/layout.ts:263— layout.getLayoutRect has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AxisBuilder.buildAxisLabel (cyclomatic 26) src/component/axis/AxisBuilder.ts:1346— AxisBuilder.buildAxisLabel has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1381, 1513). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
forceLayout.graphForceLayout (cyclomatic 26) src/chart/graph/forceLayout.ts:40— forceLayout.graphForceLayout has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 41, 131, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Source.determineSourceDimensions (cyclomatic 26) src/data/Source.ts:300— Source.determineSourceDimensions has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SliderZoomView._renderDataShadow (cyclomatic 26) src/component/dataZoom/SliderZoomView.ts:360— SliderZoomView._renderDataShadow has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 411, createDataShadowGroup). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
compatStyle.processSeries (cyclomatic 25) src/preprocessor/helper/compatStyle.ts:148— compatStyle.processSeries has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
morphTransitionHelper.applyMorphAnimation (cyclomatic 25) src/animation/morphTransitionHelper.ts:110— morphTransitionHelper.applyMorphAnimation has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LineView.getVisualGradient (cyclomatic 25) src/chart/line/LineView.ts:268— LineView.getVisualGradient has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KDTree.nearestN (cyclomatic 25) src/util/KDTree.ts:194— KDTree.nearestN has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Time.createIntervalTicks::addLevelTicks (cyclomatic 24) src/scale/Time.ts:543— Time.createIntervalTicks::addLevelTicks has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (Time.createIntervalTicks) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
labelLayoutHelper.shiftLayoutOnXY (cyclomatic 24) src/label/labelLayoutHelper.ts:324— labelLayoutHelper.shiftLayoutOnXY has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (squeezeGaps, squeezeWhenBailout, takeBoundsGap, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Line._updateCommonStl (cyclomatic 24) src/chart/helper/Line.ts:225— Line._updateCommonStl has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LineView._endLabelOnDuring (cyclomatic 24) src/chart/line/LineView.ts:1234— LineView._endLabelOnDuring has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
visualEncoding.brushVisual (cyclomatic 24) src/component/brush/visualEncoding.ts:73— visualEncoding.brushVisual has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 12 function literals inside it that branch (lines 178, 79, 166, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
BaseBarSeriesModel.getMarkerPosition (cyclomatic 23) src/chart/bar/BaseBarSeries.ts:97— BaseBarSeriesModel.getMarkerPosition has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 108). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
barGrid.calcBarWidthAndOffset (cyclomatic 23) src/layout/barGrid.ts:206— barGrid.calcBarWidthAndOffset has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 223, 273, 323, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GaugeView._renderPointer (cyclomatic 23) src/chart/gauge/GaugeView.ts:367— GaugeView._renderPointer has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 527, createProgress, a function literal at line 491, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
breakImpl.parseAxisBreakOption (cyclomatic 23) src/scale/breakImpl.ts:508— breakImpl.parseAxisBreakOption has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 530, 581, 606). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ToolboxView.render::processFeature (cyclomatic 23) src/component/toolbox/ToolboxView.ts:103— ToolboxView.render::processFeature has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Time.createIntervalTicks (cyclomatic 22) src/scale/Time.ts:472— Time.createIntervalTicks has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Time.createIntervalTicks::addLevelTicks) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
barGrid.createProgressiveLayout.reset.progress (cyclomatic 22) src/layout/barGrid.ts:416— barGrid.createProgressiveLayout.reset.progress has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Symbol._updateCommon (cyclomatic 22) src/chart/helper/Symbol.ts:208— Symbol._updateCommon has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
funnelLayout.funnelLayout (cyclomatic 22) src/chart/funnel/funnelLayout.ts:252— funnelLayout.funnelLayout has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 253, 290). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
poly.drawSegment (cyclomatic 22) src/chart/line/poly.ts:36— poly.drawSegment has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sunburstLayout.sunburstLayout (cyclomatic 22) src/chart/sunburst/sunburstLayout.ts:33— sunburstLayout.sunburstLayout has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 95, 37, 69). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TooltipView._updateContentNotChangedOnAxis (cyclomatic 22) src/component/tooltip/TooltipView.ts:983— TooltipView._updateContentNotChangedOnAxis has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
states.createEmphasisDefaultState (cyclomatic 21) src/util/states.ts:225— states.createEmphasisDefaultState has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VisualMapping.findPieceIndex (cyclomatic 21) src/visual/VisualMapping.ts:475— VisualMapping.findPieceIndex has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
modelHelper.collectAxesInfo (cyclomatic 21) src/component/axisPointer/modelHelper.ts:116— modelHelper.collectAxesInfo has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 169, 124). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
labelStyle.setLabelStyle (cyclomatic 21) src/label/labelStyle.ts:212— labelStyle.setLabelStyle has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
axisStatisticsMetricsImpl.metricLiPosMinGapImpl (cyclomatic 21) src/coord/axisStatisticsMetricsImpl.ts:39— axisStatisticsMetricsImpl.metricLiPosMinGapImpl has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OptionManager.parseRawOption (cyclomatic 21) src/model/OptionManager.ts:294— OptionManager.parseRawOption has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ECharts._initEvents (cyclomatic 21) src/core/echarts.ts:1290— ECharts._initEvents has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 1292, 1302). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
labelGuideHelper.setLabelLineStyle (cyclomatic 21) src/label/labelGuideHelper.ts:589— labelGuideHelper.setLabelLineStyle has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MapDraw._buildGeoJSON (cyclomatic 21) src/component/helper/MapDraw.ts:249— MapDraw._buildGeoJSON has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 300, transformPolygonPoints, a function literal at line 329, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
labelLayout.avoidOverlap (cyclomatic 21) src/chart/pie/labelLayout.ts:149— labelLayout.avoidOverlap has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pieLayout.pieLayout (cyclomatic 21) src/chart/pie/pieLayout.ts:35— pieLayout.pieLayout has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 100, 39, 199, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SankeyView.render (cyclomatic 21) src/chart/sankey/SankeyView.ts:128— SankeyView.render has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 156, 277, 336). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
preprocessor.visualMapPreprocessor (cyclomatic 21) src/component/visualMap/preprocessor.ts:25— preprocessor.visualMapPreprocessor has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 32, 45, 61). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
clazz.enableClassManagement (cyclomatic 20) src/util/clazz.ts:227— clazz.enableClassManagement has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 242, a function literal at line 277, makeContainer, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tooltipMarkup.buildNameValue (cyclomatic 20) src/component/tooltip/tooltipMarkup.ts:315— tooltipMarkup.buildNameValue has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
transform.applySingleDataTransform (cyclomatic 20) src/data/helper/transform.ts:392— transform.applySingleDataTransform has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 450, 436). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
markerHelper.dataTransform (cyclomatic 20) src/component/marker/markerHelper.ts:105— markerHelper.dataTransform has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Matrix.pointToDataOneDimPrepareCtx (cyclomatic 20) src/coord/matrix/Matrix.ts:495— Matrix.pointToDataOneDimPrepareCtx has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GaugeView._renderTicks (cyclomatic 20) src/chart/gauge/GaugeView.ts:200— GaugeView._renderTicks has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sankeyLayout.computeNodeBreadths (cyclomatic 20) src/chart/sankey/sankeyLayout.ts:106— sankeyLayout.computeNodeBreadths has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SunburstView.render (cyclomatic 20) src/chart/sunburst/SunburstView.ts:49— SunburstView.render has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (doRenderNode, renderRollUp, dualTravel, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
axisBreakHelperImpl.rectCoordBuildBreakAxis (cyclomatic 20) src/component/axis/axisBreakHelperImpl.ts:102— axisBreakHelperImpl.rectCoordBuildBreakAxis has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LegendView.renderInner (cyclomatic 20) src/component/legend/LegendView.ts:174— LegendView.renderInner has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 193, 254, 189). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LabelManager.updateLayoutConfig (cyclomatic 20) src/label/LabelManager.ts:330— LabelManager.updateLayoutConfig has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
number.parseDate (cyclomatic 19) src/util/number.ts:502— number.parseDate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TitleView.render (cyclomatic 19) src/component/title/install.ts:148— TitleView.render has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AxisProxy.calculateDataWindow (cyclomatic 19) src/component/dataZoom/AxisProxy.ts:151— AxisProxy.calculateDataWindow has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 184, a function literal at line 300, restrictSet). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SaveAsImage.onclick (cyclomatic 19) src/component/toolbox/feature/SaveAsImage.ts:47— SaveAsImage.onclick has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
layout.positionElement (cyclomatic 19) src/util/layout.ts:568— layout.positionElement has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
styleCompat.convertToEC4StyleForCustomSerise (cyclomatic 19) src/util/styleCompat.ts:169— styleCompat.convertToEC4StyleForCustomSerise has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CustomView.createEl (cyclomatic 19) src/chart/custom/CustomView.ts:333— CustomView.createEl has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
axisTrigger.axisTrigger (cyclomatic 19) src/component/axisPointer/axisTrigger.ts:113— axisTrigger.axisTrigger has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 168, 189, 184, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GraphicComponentView._relocate (cyclomatic 19) src/component/graphic/GraphicView.ts:280— GraphicComponentView._relocate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataDiffer._executeMultiple (cyclomatic 18) src/data/DataDiffer.ts:208— DataDiffer._executeMultiple has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MarkAreaView.getSingleMarkerEndPoint (cyclomatic 18) src/component/marker/MarkAreaView.ts:156— MarkAreaView.getSingleMarkerEndPoint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dataStack.calculateStack (cyclomatic 18) src/processor/dataStack.ts:105— dataStack.calculateStack has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 116, 106). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
forceHelper.forceLayout.step (cyclomatic 18) src/chart/graph/forceHelper.ts:152— forceHelper.forceLayout.step has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
model.interpolateRawValues (cyclomatic 18) src/util/model.ts:1095— model.interpolateRawValues has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
styleCompat.convertEC4CompatibleRichItem (cyclomatic 18) src/util/styleCompat.ts:133— styleCompat.convertEC4CompatibleRichItem has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CustomView.processTxInfo (cyclomatic 18) src/chart/custom/CustomView.ts:1249— CustomView.processTxInfo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GraphView.render (cyclomatic 18) src/chart/graph/GraphView.ts:99— GraphView.render has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 170, 157, 211, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ECPolyline.getPointOn (cyclomatic 18) src/chart/line/poly.ts:276— ECPolyline.getPointOn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RadarView._buildSplitLineAndArea (cyclomatic 18) src/component/radar/RadarView.ts:66— RadarView._buildSplitLineAndArea has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
treeLayout.commonLayout (cyclomatic 18) src/chart/tree/treeLayout.ts:45— treeLayout.commonLayout has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreemapView._doAnimation (cyclomatic 18) src/chart/treemap/TreemapView.ts:354— TreemapView._doAnimation has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 369, 424). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
breakImpl.updateAxisBreakGapReal (cyclomatic 18) src/scale/breakImpl.ts:274— breakImpl.updateAxisBreakGapReal has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 327, 377). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LegendView.getLegendStyle (cyclomatic 18) src/component/legend/LegendView.ts:599— LegendView.getLegendStyle has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScrollableLegendView._getPageInfo (cyclomatic 18) src/component/legend/ScrollableLegendView.ts:408— ScrollableLegendView._getPageInfo has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TooltipView._updatePosition (cyclomatic 18) src/component/tooltip/TooltipView.ts:905— TooltipView._updatePosition has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LabelManager._animateLabels (cyclomatic 18) src/label/LabelManager.ts:528— LabelManager._animateLabels has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KDTree.nearest (cyclomatic 18) src/util/KDTree.ts:112— KDTree.nearest has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
labelLayoutHelper.computeLabelGeometry (cyclomatic 17) src/label/labelLayoutHelper.ts:156— labelLayoutHelper.computeLabelGeometry has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
geoCreator.resizeGeo (cyclomatic 17) src/coord/geo/geoCreator.ts:50— geoCreator.resizeGeo has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
customGraphicTransition.applyUpdateTransition (cyclomatic 17) src/animation/customGraphicTransition.ts:129— customGraphicTransition.applyUpdateTransition has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compatStyle.globalCompatStyle (cyclomatic 17) src/preprocessor/helper/compatStyle.ts:259— compatStyle.globalCompatStyle has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 293, 279, 260, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AxisProxy.filterData (cyclomatic 17) src/component/dataZoom/AxisProxy.ts:378— AxisProxy.filterData has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 424, a function literal at line 413, a function literal at line 445, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
multipleGraphEdgeHelper.getCurvenessForEdge (cyclomatic 17) src/chart/helper/multipleGraphEdgeHelper.ts:173— multipleGraphEdgeHelper.getCurvenessForEdge has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataView.onclick (cyclomatic 17) src/component/toolbox/feature/DataView.ts:323— DataView.onclick has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
echarts.init (cyclomatic 17) src/core/echarts.ts:2927— echarts.init has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SeriesData.constructor (cyclomatic 17) src/data/SeriesData.ts:268— SeriesData.constructor has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataFormatMixin.getFormattedLabel (cyclomatic 17) src/model/mixin/dataFormat.ts:108— DataFormatMixin.getFormattedLabel has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
basicTransition.getAnimationConfig (cyclomatic 17) src/animation/basicTransition.ts:58— basicTransition.getAnimationConfig has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
styleCompat.convertFromEC4CompatibleStyle (cyclomatic 17) src/util/styleCompat.ts:71— styleCompat.convertFromEC4CompatibleStyle has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MapView.render (cyclomatic 17) src/chart/map/MapView.ts:39— MapView.render has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RadarView.render (cyclomatic 17) src/chart/radar/RadarView.ts:45— RadarView.render has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 7 function items inside it that branch (createSymbol, updateSymbols, a function literal at line 235, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TreeView.drawEdge (cyclomatic 17) src/chart/tree/TreeView.ts:480— TreeView.drawEdge has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TreemapView._doRender (cyclomatic 17) src/chart/treemap/TreemapView.ts:237— TreemapView._doRender has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (dualTravel::processNode, clearStorage, dualTravel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MarkPointView.updateMarkerLayout (cyclomatic 17) src/component/marker/MarkPointView.ts:38— MarkPointView.updateMarkerLayout has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 47). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
barPolar.layoutPerAxisPerSeries (cyclomatic 17) src/layout/barPolar.ts:84— barPolar.layoutPerAxisPerSeries has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AxisBuilder.fixMinMaxLabelShow::deal (cyclomatic 16) src/component/axis/AxisBuilder.ts:1077— AxisBuilder.fixMinMaxLabelShow::deal has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vendor.tryEnsureTypedArray (cyclomatic 16) src/util/vendor.ts:86— vendor.tryEnsureTypedArray has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
customGraphicTransition.prepareStyleTransitionFrom (cyclomatic 16) src/animation/customGraphicTransition.ts:582— customGraphicTransition.prepareStyleTransitionFrom has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
decal.createOrUpdatePatternFromDecal::setPatternnSource (cyclomatic 16) src/util/decal.ts:99— decal.createOrUpdatePatternFromDecal::setPatternnSource has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
layout.mergeLayoutParam (cyclomatic 16) src/util/layout.ts:679— layout.mergeLayoutParam has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (merge, a function literal at line 703, hasValue). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GlobalModel._resetOption (cyclomatic 16) src/model/Global.ts:251— GlobalModel._resetOption has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
basicTransition.animateOrSetProps (cyclomatic 16) src/animation/basicTransition.ts:127— basicTransition.animateOrSetProps has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BarView.updateStyle (cyclomatic 16) src/chart/bar/BarView.ts:984— BarView.updateStyle has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CustomView.updateElNormal (cyclomatic 16) src/chart/custom/CustomView.ts:477— CustomView.updateElNormal has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LineView._doUpdateAnimation (cyclomatic 16) src/chart/line/LineView.ts:1327— LineView._doUpdateAnimation has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
jitterLayout.jitterLayout.reset (cyclomatic 16) src/chart/scatter/jitterLayout.ts:36— jitterLayout.jitterLayout.reset has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
findPointFromSeries.findPointFromSeries (cyclomatic 16) src/component/axisPointer/findPointFromSeries.ts:31— findPointFromSeries.findPointFromSeries has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LegendView._createItem (cyclomatic 16) src/component/legend/LegendView.ts:384— LegendView._createItem has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MarkLineView.markLineTransform (cyclomatic 16) src/component/marker/MarkLineView.ts:66— MarkLineView.markLineTransform has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FixmeComment repeated across 32 files src/visual/VisualMapping.ts:484— The identical FixmeComment appears in 32 files (43 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 43 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// FIXME". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TodoComment repeated across 23 files src/visual/style.ts:86— The identical TodoComment appears in 23 files (27 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 27 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
HackComment src/model/Component.ts:387— // Hack dataset for convenience. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
labelStyle.setTokenTextStyle (cognitive 83) src/label/labelStyle.ts:533— labelStyle.setTokenTextStyle has cognitive complexity 83 (threshold 15). Drivers by points: if/else 33 (60 pts), boolean chains 17, loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
backwardCompat.globalBackwardCompat (cognitive 81) src/preprocessor/backwardCompat.ts:144— backwardCompat.globalBackwardCompat has cognitive complexity 81 (threshold 15). Drivers by points: if/else 31 (64 pts), boolean chains 11, loops 2 (6 pts) (nesting depth added 37). Most of this is not in the body itself: 1 of the 81 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 150, 262). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Time.createIntervalTicks (cognitive 72) src/scale/Time.ts:472— Time.createIntervalTicks has cognitive complexity 72 (threshold 15). Drivers by points: if/else 18 (46 pts), boolean chains 11, loops 7 (11 pts), match/switch 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 34). Of this number, 45 points are the body's own statements and 27 belong to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
createDimensions.prepareSeriesDataSchema (cognitive 69) src/data/helper/createDimensions.ts:100— createDimensions.prepareSeriesDataSchema has cognitive complexity 69 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 25, loops 5 (10 pts), ternaries 3 (4 pts) (nesting depth added 14). Of this number, 33 points are the body's own statements and 36 belong to 8 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sourceHelper.doGuessOrdinal (cognitive 68) src/data/helper/sourceHelper.ts:354— sourceHelper.doGuessOrdinal has cognitive complexity 68 (threshold 15). Drivers by points: if/else 22 (41 pts), loops 5 (12 pts), boolean chains 11, ternaries 2 (4 pts) (nesting depth added 28). Of this number, 62 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LineView.render (cognitive 67) src/chart/line/LineView.ts:635— LineView.render has cognitive complexity 67 (threshold 15). Drivers by points: if/else 25 (45 pts), boolean chains 21, ternaries 1 (nesting depth added 20). Of this number, 66 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
axisAlignTicks.scaleCalcAlign (cognitive 64) src/coord/axisAlignTicks.ts:44— axisAlignTicks.scaleCalcAlign has cognitive complexity 64 (threshold 15). Drivers by points: if/else 28 (48 pts), boolean chains 13, ternaries 2, loops 1 (nesting depth added 20). Of this number, 35 points are the body's own statements and 29 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
poly.drawSegment (cognitive 62) src/chart/line/poly.ts:36— poly.drawSegment has cognitive complexity 62 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 3 (15 pts), loops 3 (10 pts), boolean chains 4 (nesting depth added 38). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TreemapView.renderNode (cognitive 61) src/chart/treemap/TreemapView.ts:739— TreemapView.renderNode has cognitive complexity 61 (threshold 15). Drivers by points: if/else 27 (34 pts), boolean chains 19, ternaries 7 (8 pts) (nesting depth added 8). Of this number, 26 points are the body's own statements and 35 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DataStore.selectRange (cognitive 58) src/data/DataStore.ts:667— DataStore.selectRange has cognitive complexity 58 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 5 (16 pts), boolean chains 10 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
funnelLayout.labelLayout (cognitive 58) src/chart/funnel/funnelLayout.ts:55— funnelLayout.labelLayout has cognitive complexity 58 (threshold 15). Drivers by points: if/else 31 (55 pts), boolean chains 3 (nesting depth added 24). None of this is in the body itself: all 58 points belong to one function literal inside it that branches (line 58). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
labelLayout.avoidOverlap (cognitive 57) src/chart/pie/labelLayout.ts:149— labelLayout.avoidOverlap has cognitive complexity 57 (threshold 15). Drivers by points: if/else 21 (46 pts), ternaries 2 (6 pts), loops 3, boolean chains 2 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelLayout.pieLabelLayout (cognitive 57) src/chart/pie/labelLayout.ts:349— labelLayout.pieLabelLayout has cognitive complexity 57 (threshold 15). Drivers by points: if/else 27 (43 pts), boolean chains 10, loops 2, ternaries 1 (2 pts) (nesting depth added 17). Of this number, 20 points are the body's own statements and 37 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aria.ariaVisual (cognitive 57) REDACTED:48— aria.ariaVisual has cognitive complexity 57 (threshold 15). Drivers by points: if/else 19 (29 pts), ternaries 5 (17 pts), boolean chains 8, loops 1 (3 pts) (nesting depth added 24). Most of this is not in the body itself: 2 of the 57 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 188, setLabel, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GlobalModel._mergeOption (cognitive 56) src/model/Global.ts:312— GlobalModel._mergeOption has cognitive complexity 56 (threshold 15). Drivers by points: if/else 24 (49 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 26). Most of this is not in the body itself: 3 of the 56 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 397, visitComponent, a function literal at line 327, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BarView._renderNormal (cognitive 56) src/chart/bar/BarView.ts:173— BarView._renderNormal has cognitive complexity 56 (threshold 15). Drivers by points: if/else 34 (41 pts), boolean chains 13, loops 1, ternaries 1 (nesting depth added 7). Most of this is not in the body itself: 10 of the 56 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 315, a function literal at line 241, createBackground, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BaseBarSeriesModel.getMarkerPosition (cognitive 55) src/chart/bar/BaseBarSeries.ts:97— BaseBarSeriesModel.getMarkerPosition has cognitive complexity 55 (threshold 15). Drivers by points: if/else 14 (38 pts), ternaries 2 (8 pts), boolean chains 5, loops 1 (4 pts) (nesting depth added 33). Most of this is not in the body itself: 8 of the 55 points are its own statements and the rest belongs to one function literal inside it that branches (line 108). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
universalTransition.transitionBetween (cognitive 55) src/animation/universalTransition.ts:209— universalTransition.transitionBetween has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (33 pts), boolean chains 13, ternaries 3 (6 pts), loops 2 (3 pts) (nesting depth added 14). Most of this is not in the body itself: 13 of the 55 points are its own statements and the rest belongs to 10 function items inside it that branch (updateOneToOne, a function literal at line 300, a function literal at line 435, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CustomView.makeRenderItem (cognitive 54) src/chart/custom/CustomView.ts:627— CustomView.makeRenderItem has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 23, if/else 13 (16 pts), ternaries 9 (13 pts), loops 2 (nesting depth added 7). Most of this is not in the body itself: 11 of the 54 points are its own statements and the rest belongs to 12 function items inside it that branch (style, ordinalRawValue, visual, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GaugeView._renderTicks (cognitive 53) src/chart/gauge/GaugeView.ts:200— GaugeView._renderTicks has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (27 pts), ternaries 5 (21 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TreeView.updateNode (cognitive 53) src/chart/tree/TreeView.ts:327— TreeView.updateNode has cognitive complexity 53 (threshold 15). Drivers by points: if/else 15 (31 pts), ternaries 8 (14 pts), boolean chains 8 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chordLayout.chordLayout (cognitive 49) src/chart/chord/chordLayout.ts:39— chordLayout.chordLayout has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 18, ternaries 6 (10 pts) (nesting depth added 7). Most of this is not in the body itself: 11 of the 49 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 178, 72, 88, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GraphicComponentView._updateElements (cognitive 46) src/component/graphic/GraphicView.ts:111— GraphicComponentView._updateElements has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 10, ternaries 3 (5 pts) (nesting depth added 12). Most of this is not in the body itself: 1 of the 46 points is its own statement and the rest belongs to one function literal inside it that branches (line 125). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ECPolyline.getPointOn (cognitive 44) src/chart/line/poly.ts:276— ECPolyline.getPointOn has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 5 (23 pts), if/else 4 (12 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Task.perform (cognitive 43) src/core/task.ts:139— Task.perform has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 14, loops 1 (4 pts), ternaries 2 (4 pts) (nesting depth added 11). Of this number, 42 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IntervalScale.getTicks (cognitive 43) src/scale/Interval.ts:183— IntervalScale.getTicks has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 6, ternaries 3 (5 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelGuideHelper.setLabelLineStyle (cognitive 43) src/label/labelGuideHelper.ts:589— labelGuideHelper.setLabelLineStyle has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 7, ternaries 2 (7 pts), loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HeatmapView._renderOnGridLike (cognitive 42) src/chart/heatmap/HeatmapView.ts:164— HeatmapView._renderOnGridLike has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (33 pts), boolean chains 7, loops 1, ternaries 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LabelManager.updateLayoutConfig (cognitive 42) src/label/LabelManager.ts:330— LabelManager.updateLayoutConfig has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (26 pts), ternaries 3 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelStyle.setLabelStyle (cognitive 39) src/label/labelStyle.ts:212— labelStyle.setLabelStyle has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forceLayout.graphForceLayout (cognitive 39) src/chart/graph/forceLayout.ts:40— forceLayout.graphForceLayout has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 7, loops 3 (6 pts), ternaries 3 (6 pts) (nesting depth added 15). None of this is in the body itself: all 39 points belong to 6 function literals inside it that branch (lines 41, 131, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
pieLayout.pieLayout (cognitive 39) src/chart/pie/pieLayout.ts:35— pieLayout.pieLayout has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (27 pts), ternaries 4 (8 pts), boolean chains 4 (nesting depth added 15). None of this is in the body itself: all 39 points belong to 5 function literals inside it that branch (lines 100, 39, 199, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
multipleGraphEdgeHelper.getCurvenessForEdge (cognitive 38) src/chart/helper/multipleGraphEdgeHelper.ts:173— multipleGraphEdgeHelper.getCurvenessForEdge has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 5 (17 pts), boolean chains 2, loops 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GaugeView._renderPointer (cognitive 38) src/chart/gauge/GaugeView.ts:367— GaugeView._renderPointer has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (25 pts), ternaries 6 (10 pts), boolean chains 3 (nesting depth added 16). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 527, a function literal at line 491, createProgress, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
breakImpl.parseAxisBreakOption (cognitive 38) src/scale/breakImpl.ts:508— breakImpl.parseAxisBreakOption has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 3 (nesting depth added 17). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 530, 581, 606). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
KDTree.nearestN (cognitive 38) src/util/KDTree.ts:194— KDTree.nearestN has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 11, loops 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MatrixBodyCorner._ensureCellMap (cognitive 37) src/coord/matrix/MatrixBodyCorner.ts:103— MatrixBodyCorner._ensureCellMap has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 6, loops 4 (6 pts), ternaries 1 (nesting depth added 11). Most of this is not in the body itself: 1 of the 37 points is its own statement and the rest belongs to 4 function items inside it that branch (fillCellMap, a function literal at line 130, a function literal at line 200, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ScaleRawExtentInfo.constructor (cognitive 37) src/coord/scaleRawExtentInfo.ts:180— ScaleRawExtentInfo.constructor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 15, ternaries 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
LineView._endLabelOnDuring (cognitive 36) src/chart/line/LineView.ts:1234— LineView._endLabelOnDuring has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 5 (13 pts), boolean chains 8 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VisualMapping.findPieceIndex (cognitive 35) src/visual/VisualMapping.ts:475— VisualMapping.findPieceIndex has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6, ternaries 2 (5 pts), loops 2 (nesting depth added 15). Of this number, 34 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
universalTransition.findTransitionSeriesBatches (cognitive 35) src/animation/universalTransition.ts:544— universalTransition.findTransitionSeriesBatches has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (34 pts), boolean chains 1 (nesting depth added 21). None of this is in the body itself: all 35 points belong to 4 function items inside it that branch (a function literal at line 589, a function literal at line 562, checkTransitionSeriesKeyDuplicated, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RadarView._buildSplitLineAndArea (cognitive 35) src/component/radar/RadarView.ts:66— RadarView._buildSplitLineAndArea has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 3 (7 pts), boolean chains 3, ternaries 2 (nesting depth added 17). Of this number, 34 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelLayoutHelper.shiftLayoutOnXY (cognitive 34) src/label/labelLayoutHelper.ts:324— labelLayoutHelper.shiftLayoutOnXY has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 6 (8 pts), boolean chains 3, ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 4 function items inside it that branch (squeezeGaps, takeBoundsGap, squeezeWhenBailout, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OptionManager.parseRawOption (cognitive 34) src/model/OptionManager.ts:294— OptionManager.parseRawOption has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 6 (nesting depth added 15). Of this number, 17 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
funnelLayout.funnelLayout (cognitive 34) src/chart/funnel/funnelLayout.ts:252— funnelLayout.funnelLayout has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (26 pts), match/switch 2 (3 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 13). None of this is in the body itself: all 34 points belong to 2 function literals inside it that branch (lines 253, 290). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MatrixView.createMatrixCell (cognitive 34) src/component/matrix/MatrixView.ts:261— MatrixView.createMatrixCell has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 9, ternaries 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AxisBuilder.buildAxisLabel (cognitive 33) src/component/axis/AxisBuilder.ts:1346— AxisBuilder.buildAxisLabel has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 8 (13 pts), if/else 7 (11 pts), boolean chains 9 (nesting depth added 9). Most of this is not in the body itself: 4 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1381, 1513). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
sourceHelper.makeSeriesEncodeForNameBased (cognitive 33) src/data/helper/sourceHelper.ts:192— sourceHelper.makeSeriesEncodeForNameBased has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 8, ternaries 3 (5 pts), loops 1 (nesting depth added 11). Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 219, 210, 266). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
dataStackHelper.enableDataStack (cognitive 33) src/data/helper/dataStackHelper.ts:59— dataStackHelper.enableDataStack has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 12 (nesting depth added 7). Of this number, 17 points are the body's own statements and 16 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoordinateSystem.decideCoordSysUsageKind (cognitive 33) src/core/CoordinateSystem.ts:186— CoordinateSystem.decideCoordSysUsageKind has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (30 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
compatStyle.processSeries (cognitive 33) src/preprocessor/helper/compatStyle.ts:148— compatStyle.processSeries has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (18 pts), loops 4 (9 pts), boolean chains 6 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
sankeyLayout.computeNodeBreadths (cognitive 33) src/chart/sankey/sankeyLayout.ts:106— sankeyLayout.computeNodeBreadths has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (9 pts), ternaries 4 (8 pts), boolean chains 4 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LegendView.renderInner (cognitive 33) src/component/legend/LegendView.ts:174— LegendView.renderInner has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 5 (nesting depth added 13). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 193, 254, 189). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
customGraphicTransition.applyUpdateTransition (cognitive 32) src/animation/customGraphicTransition.ts:129— customGraphicTransition.applyUpdateTransition has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 3 (8 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 14). Of this number, 16 points are the body's own statements and 16 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
decal.createOrUpdatePatternFromDecal::setPatternnSource::brushDecal (cognitive 32) src/util/decal.ts:209— decal.createOrUpdatePatternFromDecal::setPatternnSource::brushDecal has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 4 (9 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
barGrid.createProgressiveLayout.reset.progress (cognitive 31) src/layout/barGrid.ts:416— barGrid.createProgressiveLayout.reset.progress has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
customGraphicKeyframeAnimation.applyKeyframeAnimation (cognitive 31) src/animation/customGraphicKeyframeAnimation.ts:59— customGraphicKeyframeAnimation.applyKeyframeAnimation has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 10, ternaries 2, loops 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 102, 91, 140). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VisualMapModel.completeVisualOption (cognitive 31) src/component/visualMap/VisualMapModel.ts:484— VisualMapModel.completeVisualOption has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 18, if/else 9 (13 pts) (nesting depth added 4). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 573, completeController, a function literal at line 540, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Source.determineSourceDimensions (cognitive 31) src/data/Source.ts:300— Source.determineSourceDimensions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 6 (nesting depth added 10). Of this number, 21 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LineView.getVisualGradient (cognitive 31) src/chart/line/LineView.ts:268— LineView.getVisualGradient has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 6 (11 pts), boolean chains 7, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
states.createEmphasisDefaultState (cognitive 30) src/util/states.ts:225— states.createEmphasisDefaultState has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomView.createEl (cognitive 30) src/chart/custom/CustomView.ts:333— CustomView.createEl has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 11). Of this number, 23 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Line._updateCommonStl (cognitive 30) src/chart/helper/Line.ts:225— Line._updateCommonStl has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 12, loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 267). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Line.beforeUpdate (cognitive 30) src/chart/helper/Line.ts:358— Line.beforeUpdate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, match/switch 2 (4 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 8). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LargeLinesPath.findDataIndex (cognitive 30) src/chart/helper/LargeLineDraw.ts:134— LargeLinesPath.findDataIndex has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 3 (8 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LineView._initSymbolLabelAnimation (cognitive 30) src/chart/line/LineView.ts:1078— LineView._initSymbolLabelAnimation has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 3 (5 pts), boolean chains 1 (nesting depth added 13). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 1106). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SunburstPiece._updateLabel (cognitive 30) src/chart/sunburst/SunburstPiece.ts:163— SunburstPiece._updateLabel has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 9, ternaries 4 (nesting depth added 3). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 185, getLabelAttr). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LabelManager._animateLabels (cognitive 30) src/label/LabelManager.ts:528— LabelManager._animateLabels has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 4 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
states.blurSeries (cognitive 29) src/util/states.ts:429— states.blurSeries has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 12, if/else 10 (12 pts), loops 2 (4 pts), ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 461, a function literal at line 508, leaveBlurOfIndices, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
geoCreator.resizeGeo (cognitive 29) src/coord/geo/geoCreator.ts:50— geoCreator.resizeGeo has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 12). Of this number, 25 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform.applySingleDataTransform (cognitive 29) src/data/helper/transform.ts:392— transform.applySingleDataTransform has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 10). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 450, 436). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
layout.getLayoutRect (cognitive 29) src/util/layout.ts:263— layout.getLayoutRect has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 10, match/switch 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeView.drawEdge (cognitive 29) src/chart/tree/TreeView.ts:480— TreeView.drawEdge has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 4, loops 1 (4 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GraphicComponentView._relocate (cognitive 29) src/component/graphic/GraphicView.ts:280— GraphicComponentView._relocate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, ternaries 3 (6 pts), loops 3 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScrollableLegendView._getPageInfo (cognitive 29) src/component/legend/ScrollableLegendView.ts:408— ScrollableLegendView._getPageInfo has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 6, loops 2, ternaries 1 (nesting depth added 11). Of this number, 27 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preprocessor.visualMapPreprocessor (cognitive 29) src/component/visualMap/preprocessor.ts:25— preprocessor.visualMapPreprocessor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 8 (nesting depth added 10). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 32, 45, 61). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
log.makePrintable::makePrintableStringIfPossible (cognitive 28) src/util/log.ts:83— log.makePrintable::makePrintableStringIfPossible has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (28 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
barGrid.calcBarWidthAndOffset (cognitive 28) src/layout/barGrid.ts:206— barGrid.calcBarWidthAndOffset has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 9 (nesting depth added 5). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 273, 223, 323, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
customGraphicTransition.prepareStyleTransitionFrom (cognitive 28) src/animation/customGraphicTransition.ts:582— customGraphicTransition.prepareStyleTransitionFrom has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (7 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ToolboxView.render::processFeature (cognitive 28) src/component/toolbox/ToolboxView.ts:103— ToolboxView.render::processFeature has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 10, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
number.parseDate (cognitive 27) src/util/number.ts:502— number.parseDate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 10, ternaries 2 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Symbol._updateCommon (cognitive 27) src/chart/helper/Symbol.ts:208— Symbol._updateCommon has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 9, ternaries 4 (6 pts) (nesting depth added 4). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SaveAsImage.onclick (cognitive 27) src/component/toolbox/feature/SaveAsImage.ts:47— SaveAsImage.onclick has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), loops 1 (4 pts), ternaries 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SeriesData.constructor (cognitive 27) src/data/SeriesData.ts:268— SeriesData.constructor has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
morphTransitionHelper.applyMorphAnimation::morphOneBatch (cognitive 27) src/animation/morphTransitionHelper.ts:154— morphTransitionHelper.applyMorphAnimation::morphOneBatch has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (18 pts), if/else 4 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
styleCompat.convertToEC4RichItem (cognitive 27) src/util/styleCompat.ts:214— styleCompat.convertToEC4RichItem has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 26, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderTimelineView._layout (cognitive 27) src/component/timeline/SliderTimelineView.ts:166— SliderTimelineView._layout has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 16, if/else 6, ternaries 5. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KDTree.nearest (cognitive 27) src/util/KDTree.ts:112— KDTree.nearest has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 9, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model.interpolateRawValues (cognitive 26) src/util/model.ts:1095— model.interpolateRawValues has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 6 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SliderZoomView._positionGroup (cognitive 26) src/component/dataZoom/SliderZoomView.ts:277— SliderZoomView._positionGroup has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (21 pts), boolean chains 5 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SliderZoomView._renderDataShadow (cognitive 26) src/component/dataZoom/SliderZoomView.ts:360— SliderZoomView._renderDataShadow has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 8, ternaries 3 (4 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 411, createDataShadowGroup). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MarkAreaView.getSingleMarkerEndPoint (cognitive 25) src/component/marker/MarkAreaView.ts:156— MarkAreaView.getSingleMarkerEndPoint has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vendor.tryEnsureTypedArray (cognitive 25) src/util/vendor.ts:86— vendor.tryEnsureTypedArray has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 1 (4 pts), error handling 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compatStyle.compatEC2ItemStyle (cognitive 25) src/preprocessor/helper/compatStyle.ts:34— compatStyle.compatEC2ItemStyle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStore._updateDims (cognitive 25) src/data/DataStore.ts:811— DataStore._updateDims has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SeriesData._doInit (cognitive 25) src/data/SeriesData.ts:622— SeriesData._doInit has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
format.makeValueReadable (cognitive 25) src/util/format.ts:64— format.makeValueReadable has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (18 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 11). Of this number, 23 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataFormatMixin.getFormattedLabel (cognitive 25) src/model/mixin/dataFormat.ts:108— DataFormatMixin.getFormattedLabel has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 150). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Matrix.pointToDataOneDimPrepareCtx (cognitive 24) src/coord/matrix/Matrix.ts:495— Matrix.pointToDataOneDimPrepareCtx has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 5 (6 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
compatStyle.convertNormalEmphasis (cognitive 24) src/preprocessor/helper/compatStyle.ts:72— compatStyle.convertNormalEmphasis has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forceHelper.forceLayout.step (cognitive 24) src/chart/graph/forceHelper.ts:152— forceHelper.forceLayout.step has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 7, loops 5 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
echarts.init (cognitive 24) src/core/echarts.ts:2927— echarts.init has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 8 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomView.doCreateOrUpdateAttachedTx (cognitive 24) src/chart/custom/CustomView.ts:1183— CustomView.doCreateOrUpdateAttachedTx has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RadarView.render (cognitive 24) src/chart/radar/RadarView.ts:45— RadarView.render has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8, ternaries 1 (4 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 24 points belong to 7 function items inside it that branch (updateSymbols, createSymbol, a function literal at line 235, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SunburstView.render (cognitive 24) src/chart/sunburst/SunburstView.ts:49— SunburstView.render has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 5 function items inside it that branch (doRenderNode, renderRollUp, dualTravel, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
sunburstLayout.sunburstLayout (cognitive 24) src/chart/sunburst/sunburstLayout.ts:33— sunburstLayout.sunburstLayout has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, ternaries 2 (3 pts) (nesting depth added 5). None of this is in the body itself: all 24 points belong to 3 function literals inside it that branch (lines 95, 37, 69). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
axisBreakHelperImpl.rectCoordBuildBreakAxis (cognitive 24) src/component/axis/axisBreakHelperImpl.ts:102— axisBreakHelperImpl.rectCoordBuildBreakAxis has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, loops 2, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to one function item inside it that branches (addZigzagShapes). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
barPolar.layoutPerAxisPerSeries (cognitive 24) src/layout/barPolar.ts:84— barPolar.layoutPerAxisPerSeries has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6, ternaries 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
axisStatisticsMetricsImpl.metricLiPosMinGapImpl (cognitive 23) src/coord/axisStatisticsMetricsImpl.ts:39— axisStatisticsMetricsImpl.metricLiPosMinGapImpl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, loops 2, ternaries 2 (nesting depth added 4). Of this number, 12 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
customGraphicTransition.prepareShapeOrExtraTransitionFrom (cognitive 23) src/animation/customGraphicTransition.ts:471— customGraphicTransition.prepareShapeOrExtraTransitionFrom has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AxisProxy.calculateDataWindow (cognitive 23) src/component/dataZoom/AxisProxy.ts:151— AxisProxy.calculateDataWindow has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 5, ternaries 3, loops 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 184, a function literal at line 300, restrictSet). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GraphNode.getTrajectoryDataIndices (cognitive 23) src/data/Graph.ts:391— GraphNode.getTrajectoryDataIndices has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 3 (10 pts), boolean chains 2 (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ECharts.getConnectedDataURL (cognitive 23) src/core/echarts.ts:1013— ECharts.getConnectedDataURL has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (5 pts), boolean chains 4 (nesting depth added 9). Of this number, 18 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model.compressBatches (cognitive 23) src/util/model.ts:642— model.compressBatches has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (makeMap, mapToArray). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LineView.createLineClipPath (cognitive 23) src/chart/line/LineView.ts:510— LineView.createLineClipPath has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). Of this number, 17 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
treeLayout.commonLayout (cognitive 23) src/chart/tree/treeLayout.ts:45— treeLayout.commonLayout has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
visualEncoding.brushVisual (cognitive 23) src/component/brush/visualEncoding.ts:73— visualEncoding.brushVisual has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, ternaries 5 (7 pts), if/else 5 (6 pts) (nesting depth added 3). None of this is in the body itself: all 23 points belong to 12 function literals inside it that branch (lines 178, 166, 88, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MarkLineView.markLineTransform (cognitive 23) src/component/marker/MarkLineView.ts:66— MarkLineView.markLineTransform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markerHelper.dataTransform (cognitive 22) src/component/marker/markerHelper.ts:105— markerHelper.dataTransform has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VisualMapModel.formatValueText (cognitive 22) src/component/visualMap/VisualMapModel.ts:351— VisualMapModel.formatValueText has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 8 (9 pts), boolean chains 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BarView.updateStyle (cognitive 22) src/chart/bar/BarView.ts:984— BarView.updateStyle has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 5 (6 pts), boolean chains 3 (nesting depth added 8). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sankeyLayout.resolveCollisions (cognitive 22) src/chart/sankey/sankeyLayout.ts:359— sankeyLayout.resolveCollisions has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 4 (7 pts), loops 2 (3 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 368). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
jitterLayout.jitterLayout.reset.progress (cognitive 22) src/chart/scatter/jitterLayout.ts:62— jitterLayout.jitterLayout.reset.progress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContinuousView._createBarGroup (cognitive 22) src/component/visualMap/ContinuousView.ts:594— ContinuousView._createBarGroup has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (19 pts), boolean chains 3 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
gexf.parseNodes (cognitive 21) extension-src/dataTool/gexf.ts:73— gexf.parseNodes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (5 pts), loops 1 (3 pts), ternaries 1 (nesting depth added 13). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 74). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Time.getMinutesAndSecondsInterval (cognitive 21) src/scale/Time.ts:430— Time.getMinutesAndSecondsInterval has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (21 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DataDiffer._executeMultiple (cognitive 21) src/data/DataDiffer.ts:208— DataDiffer._executeMultiple has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), loops 2 (4 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GeoSVGResource._buildGraphic (cognitive 21) src/coord/geo/GeoSVGResource.ts:134— GeoSVGResource._buildGraphic has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, error handling 1 (nesting depth added 7). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MatrixDim._initByDimModelData (cognitive 21) REDACTED:174— MatrixDim._initByDimModelData has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 6). None of this is in the body itself: all 21 points belong to 3 function items inside it that branch (a function literal at line 197, postInitCells, traverseInitCells). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TitleView.render (cognitive 21) src/component/title/install.ts:148— TitleView.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStore.lttbDownSample (cognitive 21) src/data/DataStore.ts:870— DataStore.lttbDownSample has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomView.updateElNormal (cognitive 21) src/chart/custom/CustomView.ts:477— CustomView.updateElNormal has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomView.processTxInfo (cognitive 21) src/chart/custom/CustomView.ts:1249— CustomView.processTxInfo has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 6 (7 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LineView._doUpdateAnimation (cognitive 21) src/chart/line/LineView.ts:1327— LineView._doUpdateAnimation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
number.linearMap (cognitive 20) src/util/number.ts:67— number.linearMap has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
modelHelper.collectAxesInfo (cognitive 20) src/component/axisPointer/modelHelper.ts:116— modelHelper.collectAxesInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, ternaries 1 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 124, 169). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
matrixCoordHelper.parseCoordRangeOptionOnOneDim (cognitive 20) src/coord/matrix/matrixCoordHelper.ts:107— matrixCoordHelper.parseCoordRangeOptionOnOneDim has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Graph.breadthFirstTraverse (cognitive 20) src/data/Graph.ts:218— Graph.breadthFirstTraverse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (6 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataView.onclick (cognitive 20) src/component/toolbox/feature/DataView.ts:323— DataView.onclick has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, error handling 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ECharts._initEvents (cognitive 20) src/core/echarts.ts:1290— ECharts._initEvents has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (10 pts) (nesting depth added 4). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 1292, 1302). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
scaleRawExtentInfo.scaleRawExtentInfoCreateDeal (cognitive 20) src/coord/scaleRawExtentInfo.ts:574— scaleRawExtentInfo.scaleRawExtentInfoCreateDeal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 585). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
layout.mergeLayoutParam (cognitive 20) src/util/layout.ts:679— layout.mergeLayoutParam has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (merge, a function literal at line 703, hasValue). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MapDraw.resetLabelForRegion (cognitive 20) src/component/helper/MapDraw.ts:679— MapDraw.resetLabelForRegion has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelLayout.constrainTextWidth (cognitive 20) src/chart/pie/labelLayout.ts:269— labelLayout.constrainTextWidth has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (13 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AxisBuilder.fixMinMaxLabelShow::deal (cognitive 19) src/component/axis/AxisBuilder.ts:1077— AxisBuilder.fixMinMaxLabelShow::deal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Geo.constructor (cognitive 19) src/coord/geo/Geo.ts:86— Geo.constructor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AxisProxy.filterData (cognitive 19) src/component/dataZoom/AxisProxy.ts:378— AxisProxy.filterData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 424, a function literal at line 413, a function literal at line 445, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Source.detectSourceFormat (cognitive 19) src/data/Source.ts:256— Source.detectSourceFormat has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model.queryReferringComponents (cognitive 19) src/util/model.ts:938— model.queryReferringComponents has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
basicTransition.getAnimationConfig (cognitive 19) src/animation/basicTransition.ts:58— basicTransition.getAnimationConfig has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 7 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomView.mergeChildren (cognitive 19) src/chart/custom/CustomView.ts:1341— CustomView.mergeChildren has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 2, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapDraw._buildGeoJSON (cognitive 19) src/component/helper/MapDraw.ts:249— MapDraw._buildGeoJSON has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8, loops 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 329, a function literal at line 300, transformPolygonPoints, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TreemapView._doAnimation (cognitive 19) src/chart/treemap/TreemapView.ts:354— TreemapView._doAnimation has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 424, 369). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
axisTrigger.axisTrigger (cognitive 19) src/component/axisPointer/axisTrigger.ts:113— axisTrigger.axisTrigger has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (8 pts) (nesting depth added 2). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 168, 189, 184, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TooltipView._tryShow (cognitive 19) src/component/tooltip/TooltipView.ts:453— TooltipView._tryShow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2 (nesting depth added 5). Of this number, 11 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conditionalExpression.parseRelationalOption (cognitive 19) REDACTED:384— conditionalExpression.parseRelationalOption has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler._performStageTasks (cognitive 18) src/core/Scheduler.ts:305— Scheduler._performStageTasks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 7 (nesting depth added 4). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 315, a function literal at line 348, needSetDirty, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
transform.createExternalSource (cognitive 18) src/data/helper/transform.ts:162— transform.createExternalSource has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). Of this number, 9 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compatStyle.globalCompatStyle (cognitive 18) src/preprocessor/helper/compatStyle.ts:259— compatStyle.globalCompatStyle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (nesting depth added 3). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 293, 279, 260, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ECEventProcessor.normalizeQuery (cognitive 18) src/util/ECEventProcessor.ts:57— ECEventProcessor.normalizeQuery has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 75). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
layout.positionElement (cognitive 18) src/util/layout.ts:568— layout.positionElement has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts), ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GlobalModel._resetOption (cognitive 18) src/model/Global.ts:251— GlobalModel._resetOption has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BarView.createBackgroundShape (cognitive 18) src/chart/bar/BarView.ts:1232— BarView.createBackgroundShape has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepareBoxplotData.prepareBoxplotData (cognitive 18) src/chart/boxplot/prepareBoxplotData.ts:47— prepareBoxplotData.prepareBoxplotData has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 3, if/else 1 (3 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
styleCompat.convertFromEC4CompatibleStyle (cognitive 18) src/util/styleCompat.ts:71— styleCompat.convertFromEC4CompatibleStyle has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (5 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
labelGuideHelper.limitSurfaceAngle (cognitive 18) src/label/labelGuideHelper.ts:467— labelGuideHelper.limitSurfaceAngle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphView.render (cognitive 18) src/chart/graph/GraphView.ts:99— GraphView.render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 2, match/switch 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 157, 170, 211, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LargeLinesPath.buildPath (cognitive 18) src/chart/helper/LargeLineDraw.ts:95— LargeLinesPath.buildPath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (8 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sankeyLayout.adjustNodeWithNodeAlign (cognitive 18) src/chart/sankey/sankeyLayout.ts:190— sankeyLayout.adjustNodeWithNodeAlign has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (9 pts) (nesting depth added 11). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findPointFromSeries.findPointFromSeries (cognitive 18) src/component/axisPointer/findPointFromSeries.ts:31— findPointFromSeries.findPointFromSeries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (3 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MatrixView.createBodyAndCorner::createBodyOrCornerCells (cognitive 18) src/component/matrix/MatrixView.ts:199— MatrixView.createBodyAndCorner::createBodyOrCornerCells has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooltipView._showTooltipContent (cognitive 18) src/component/tooltip/TooltipView.ts:812— TooltipView._showTooltipContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelStyle.setTextStyleCommon (cognitive 17) src/label/labelStyle.ts:394— labelStyle.setTextStyleCommon has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tooltipMarkup.buildSection (cognitive 17) src/component/tooltip/tooltipMarkup.ts:243— tooltipMarkup.buildSection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 4 (5 pts) (nesting depth added 2). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
dataStack.calculateStack (cognitive 17) src/processor/dataStack.ts:105— dataStack.calculateStack has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 1 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 116, 106). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ContinuousModel.getVisualMeta (cognitive 17) src/component/visualMap/ContinuousModel.ts:245— ContinuousModel.getVisualMeta has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 5, loops 3, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SankeySeriesModel.getInitialData (cognitive 17) src/chart/sankey/SankeySeries.ts:178— SankeySeriesModel.getInitialData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 1 (nesting depth added 5). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MagicType.onclick (cognitive 17) src/component/toolbox/feature/MagicType.ts:98— MagicType.onclick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (generateNewSeriesTypes, a function literal at line 138). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
dimensionHelper.summarizeDimensions (cognitive 17) src/data/helper/dimensionHelper.ts:93— dimensionHelper.summarizeDimensions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 105, 138). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
scaleRawExtentInfo.adoptScaleExtentKindMapping (cognitive 17) src/coord/scaleRawExtentInfo.ts:775— scaleRawExtentInfo.adoptScaleExtentKindMapping has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
time.parseTimeAxisLabelFormatterDictionary (cognitive 17) src/util/time.ts:166— time.parseTimeAxisLabelFormatterDictionary has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 180). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
layout.applyPreserveAspect (cognitive 17) src/util/layout.ts:399— layout.applyPreserveAspect has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4, boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
basicTransition.animateOrSetProps (cognitive 17) src/animation/basicTransition.ts:127— basicTransition.animateOrSetProps has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 3 (4 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dataSample.dataSample.reset (cognitive 17) src/processor/dataSample.ts:83— dataSample.dataSample.reset has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
styleCompat.convertEC4CompatibleRichItem (cognitive 17) src/util/styleCompat.ts:133— styleCompat.convertEC4CompatibleRichItem has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 16, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
styleCompat.convertToEC4StyleForCustomSerise (cognitive 17) src/util/styleCompat.ts:169— styleCompat.convertToEC4StyleForCustomSerise has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4 (6 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CustomView.doCreateOrUpdateEl (cognitive 17) src/chart/custom/CustomView.ts:997— CustomView.doCreateOrUpdateEl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
simpleLayout.graphSimpleLayout (cognitive 17) src/chart/graph/simpleLayout.ts:30— simpleLayout.graphSimpleLayout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 8). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 31). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
adjustEdge.intersectCurveCircle (cognitive 17) src/chart/graph/adjustEdge.ts:31— adjustEdge.intersectCurveCircle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
adjustEdge.adjustEdge (cognitive 17) src/chart/graph/adjustEdge.ts:98— adjustEdge.adjustEdge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 106). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
LineView.highlight (cognitive 17) src/chart/line/LineView.ts:937— LineView.highlight has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelLayout.adjustSingleSide (cognitive 17) src/chart/pie/labelLayout.ts:62— labelLayout.adjustSingleSide has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (5 pts), loops 3, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (recalculateX, recalculateXOnSemiToAlignOnEllipseCurve). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TreemapView._doRender (cognitive 17) src/chart/treemap/TreemapView.ts:237— TreemapView._doRender has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, ternaries 4, if/else 2. Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (dualTravel::processNode, dualTravel, clearStorage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LegendView._createItem (cognitive 17) src/component/legend/LegendView.ts:384— LegendView._createItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 5, if/else 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkPointView.updateMarkerLayout (cognitive 17) src/component/marker/MarkPointView.ts:38— MarkPointView.updateMarkerLayout has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 5, boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 47). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
BrushController.updateCoverByMouse (cognitive 16) src/component/helper/BrushController.ts:868— BrushController.updateCoverByMouse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
labelLayoutHelper.hideOverlap (cognitive 16) src/label/labelLayoutHelper.ts:522— labelLayoutHelper.hideOverlap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Matrix.layOutUnitsOnDimension (cognitive 16) src/coord/matrix/Matrix.ts:325— Matrix.layOutUnitsOnDimension has cognitive complexity 16 (threshold 15). Drivers by points: loops 6, if/else 4 (5 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 2). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
customGraphicTransition.updateLeaveTo (cognitive 16) src/animation/customGraphicTransition.ts:210— customGraphicTransition.updateLeaveTo has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dataSelectAction.handleSeriesLegacySelectEvents (cognitive 16) src/legacy/dataSelectAction.ts:64— dataSelectAction.handleSeriesLegacySelectEvents has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 3 (6 pts), loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 78). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
LinesSeriesModel._processFlatCoordsArray (cognitive 16) src/chart/lines/LinesSeries.ts:256— LinesSeriesModel._processFlatCoordsArray has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
axisHelper.retrieveAxisBreaksOption (cognitive 16) src/coord/axisHelper.ts:291— axisHelper.retrieveAxisBreaksOption has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
helper.intervalScaleEnsureValidExtent (cognitive 16) src/scale/helper.ts:224— helper.intervalScaleEnsureValidExtent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model.mappingToExists (cognitive 16) src/util/model.ts:233— model.mappingToExists has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6 (nesting depth added 2). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
universalTransition.installUniversalTransition (cognitive 16) src/animation/universalTransition.ts:723— universalTransition.installUniversalTransition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 738, 727, 761). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
labelGuideHelper.updateLabelLinePoints (cognitive 16) src/label/labelGuideHelper.ts:338— labelGuideHelper.updateLabelLinePoints has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 4 (5 pts), ternaries 2 (5 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EffectPolyline._updateSymbolPosition (cognitive 16) src/chart/helper/EffectPolyline.ts:69— EffectPolyline._updateSymbolPosition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
backwardCompat.radarBackwardCompat (cognitive 16) src/chart/radar/backwardCompat.ts:25— backwardCompat.radarBackwardCompat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 32, 49). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TreeView.getEdgeShape (cognitive 16) src/chart/tree/TreeView.ts:685— TreeView.getEdgeShape has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (6 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MarkLineView.updateSingleMarkerEndLayout (cognitive 16) src/component/marker/MarkLineView.ts:199— MarkLineView.updateSingleMarkerEndLayout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooltipHTMLContent.setContent (cognitive 16) src/component/tooltip/TooltipHTMLContent.ts:433— TooltipHTMLContent.setContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooltipView._updatePosition (cognitive 16) src/component/tooltip/TooltipView.ts:905— TooltipView._updatePosition has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 2 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ClassTooLong: ECharts src/core/echarts.ts:454— ClassTooLong — 1307 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 907 over it, 3.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Duplication concentrated across 22 sibling directories (35 clone groups) src/chart/chord/ChordSeries.ts:152— 35 duplicated blocks under src/chart/ have copies in at least two of the sibling directories bar, boxplot, candlestick, chord, custom, effectScatter (+16 more sibling(s) not listed) — 19 of them are reported below, and 16 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 35 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 11 sibling directories (18 clone groups) src/chart/graph/categoryFilter.ts:29— 18 duplicated blocks under src/ have copies in at least two of the sibling directories chart, component, coord, core, data, label (+5 more sibling(s) not listed) — 11 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (8 clone groups) src/coord/calendar/prepareCustom.ts:41— 8 duplicated blocks under src/coord/ have copies in at least two of the sibling directories calendar, cartesian, matrix, parallel, polar, radar (+1 more sibling(s) not listed) — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (93 matched lines × 2 locations) · ×1
Duplicated block with local edits (93 matched lines × 2 locations) src/chart/chord/ChordSeries.ts:152— src/chart/chord/ChordSeries.ts:152 · src/chart/graph/GraphSeries.ts:187 — the two spans are one implementation copied and then locally edited — 618 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.
R10 · Code Duplication· Duplicated block with local edits (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) src/component/axis/CartesianAxisView.ts:90— src/component/axis/CartesianAxisView.ts:90 · src/component/axis/SingleAxisView.ts:81 — the two spans are one implementation copied and then locally edited — 416 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.
R10 · Code Duplication· Duplicated block with local edits (56 matched lines × 2 locations) · ×1
Duplicated block with local edits (56 matched lines × 2 locations) src/chart/sunburst/SunburstSeries.ts:187— src/chart/sunburst/SunburstSeries.ts:187 · src/chart/treemap/TreemapSeries.ts:395 — the two spans are one implementation copied and then locally edited — 351 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.
Duplicated block (51 lines × 5 locations) theme/dark-blue.js:20— theme/dark-blue.js:20 · theme/dark-bold.js:20 · theme/dark-digerati.js:20 · theme/dark-fresh-cut.js:20 · +1 more site(s) not listed — the 5 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 5 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.
Duplicated block (47 lines × 2 locations) theme/cool.js:20— theme/cool.js:20 · theme/tech-blue.js:20 — 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.
Duplicated block (41 lines × 2 locations) src/component/axisPointer/CartesianAxisPointer.ts:149— src/component/axisPointer/CartesianAxisPointer.ts:149 · src/component/axisPointer/SingleAxisPointer.ts:136 — 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.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) src/util/KDTree.ts:120— src/util/KDTree.ts:120 · src/util/KDTree.ts:225 — the two spans are one implementation copied and then locally edited — 268 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.
Duplicated block (36 lines × 16 locations) theme/azul.js:20— theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +12 more site(s) not listed — the 16 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 16 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.
Duplicated block (36 lines × 4 locations) theme/cool.js:20— theme/cool.js:20 · theme/mint.js:20 · theme/sakura.js:20 · theme/tech-blue.js:20 — the 4 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 4 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.
Duplicated block (36 lines × 5 locations) theme/helianthus.js:20— theme/helianthus.js:20 · theme/infographic.js:20 · theme/macarons.js:20 · theme/macarons2.js:20 · +1 more site(s) not listed — the 5 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 5 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.
Duplicated block (33 lines × 5 locations) theme/cool.js:20— theme/cool.js:20 · theme/mint.js:20 · theme/sakura.js:20 · theme/tech-blue.js:20 · +1 more site(s) not listed — the 5 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 5 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.
Duplicated block (33 lines × 2 locations) theme/dark-blue.js:81— theme/dark-blue.js:81 · theme/dark-bold.js:81 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (31 lines × 5 locations) theme/dark-blue.js:118— theme/dark-blue.js:118 · theme/dark-bold.js:118 · theme/dark-digerati.js:118 · theme/dark-fresh-cut.js:118 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) src/chart/helper/LineDraw.ts:125— src/chart/helper/LineDraw.ts:125 · src/chart/helper/SymbolDraw.ts:270 — the two spans are one implementation copied and then locally edited — 124 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.
Duplicated block (25 lines × 2 locations) src/component/marker/MarkLineView.ts:435— src/component/marker/MarkLineView.ts:435 · src/component/marker/MarkPointView.ts:192 — 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.
Duplicated block (24 lines × 29 locations) theme/azul.js:20— theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +25 more site(s) not listed — the 29 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 29 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.
R10 · Code Duplication· Duplicated block with local edits (23 matched lines × 2 locations) · ×1
Duplicated block with local edits (23 matched lines × 2 locations) src/chart/funnel/FunnelSeries.ts:110— src/chart/funnel/FunnelSeries.ts:110 · src/chart/pie/PieSeries.ts:158 — the two spans are one implementation copied and then locally edited — 152 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.
Duplicated block (22 lines × 36 locations) theme/azul.js:20— theme/azul.js:20 · theme/bee-inspired.js:20 · theme/blue.js:20 · theme/caravan.js:20 · +32 more site(s) not listed — the 36 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 36 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.
Duplicated block (21 lines × 2 locations) src/label/labelGuideHelper.ts:411— src/label/labelGuideHelper.ts:411 · src/label/labelGuideHelper.ts:467 — 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.
R10 · Code Duplication· Duplicated block with local edits (21 matched lines × 2 locations) · ×1
Duplicated block with local edits (21 matched lines × 2 locations) src/layout/barGrid.ts:265— src/layout/barGrid.ts:265 · src/layout/barPolar.ts:262 — the two spans are one implementation copied and then locally edited — 146 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.
R10 · Code Duplication· Duplicated block with local edits (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) extension-src/dataTool/prepareBoxplotData.ts:81— extension-src/dataTool/prepareBoxplotData.ts:81 · src/chart/boxplot/prepareBoxplotData.ts:61 — the two spans are one implementation copied and then locally edited — 182 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.
Duplicated block (18 lines × 2 locations) src/chart/funnel/funnelLayout.ts:351— src/chart/funnel/funnelLayout.ts:351 · src/chart/funnel/funnelLayout.ts:372 — 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.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) src/chart/graph/categoryFilter.ts:29— src/chart/graph/categoryFilter.ts:29 · src/processor/dataFilter.ts:25 — the two spans are one implementation copied and then locally edited — 84 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.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) src/chart/pie/pieLayout.ts:173— src/chart/pie/pieLayout.ts:173 · src/chart/pie/pieLayout.ts:198 — the two spans are one implementation copied and then locally edited — 85 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) src/chart/line/LineView.ts:734— src/chart/line/LineView.ts:734 · src/chart/line/LineView.ts:754 — the two spans are one implementation copied and then locally edited — 76 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.
Duplicated block (16 lines × 2 locations) src/component/axisPointer/CartesianAxisPointer.ts:53— src/component/axisPointer/CartesianAxisPointer.ts:53 · src/component/axisPointer/SingleAxisPointer.ts:57 — 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.
Complex function setTokenTextStyle (cyclomatic 54, cognitive 84) src/label/labelStyle.ts:533— setTokenTextStyle has cyclomatic complexity 54 and cognitive complexity 84; 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.
Complex function render (cyclomatic 49, cognitive 68) src/chart/line/LineView.ts:635— render has cyclomatic complexity 49 and cognitive complexity 68; 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.
Complex function beforeUpdate (cyclomatic 49, cognitive 58) src/chart/helper/Line.ts:358— beforeUpdate has cyclomatic complexity 49 and cognitive complexity 58; 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.
Complex function constructor (cyclomatic 49, cognitive 55) src/coord/scaleRawExtentInfo.ts:180— constructor has cyclomatic complexity 49 and cognitive complexity 55; 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.
Complex function (anonymous) (cyclomatic 42, cognitive 77) src/preprocessor/backwardCompat.ts:150— (anonymous) has cyclomatic complexity 42 and cognitive complexity 77; 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.
Complex function doGuessOrdinal (cyclomatic 35, cognitive 62) src/data/helper/sourceHelper.ts:354— doGuessOrdinal has cyclomatic complexity 35 and cognitive complexity 62; 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.
Complex function (anonymous) (cyclomatic 34, cognitive 73) src/chart/funnel/funnelLayout.ts:58— (anonymous) has cyclomatic complexity 34 and cognitive complexity 73; 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.
Complex function (anonymous) (cyclomatic 34, cognitive 58) src/chart/pie/labelLayout.ts:382— (anonymous) has cyclomatic complexity 34 and cognitive complexity 58; 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.
Complex function (anonymous) (cyclomatic 34, cognitive 49) src/component/graphic/GraphicView.ts:125— (anonymous) has cyclomatic complexity 34 and cognitive complexity 49; 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.
Complex function perform (cyclomatic 31, cognitive 46) src/core/task.ts:139— perform has cyclomatic complexity 31 and cognitive complexity 46; 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.
Complex function scaleCalcAlign (cyclomatic 30, cognitive 42) src/coord/axisAlignTicks.ts:44— scaleCalcAlign has cyclomatic complexity 30 and cognitive complexity 42; 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.
Complex function (anonymous) (cyclomatic 30, cognitive 40) src/chart/sunburst/SunburstPiece.ts:185— (anonymous) has cyclomatic complexity 30 and cognitive complexity 40; 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.
Complex function _layout (cyclomatic 30, cognitive 34) src/component/timeline/SliderTimelineView.ts:166— _layout has cyclomatic complexity 30 and cognitive complexity 34; 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.
Complex function selectRange (cyclomatic 29, cognitive 57) src/data/DataStore.ts:667— selectRange has cyclomatic complexity 29 and cognitive complexity 57; 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.
Complex function _renderOnGridLike (cyclomatic 29, cognitive 42) src/chart/heatmap/HeatmapView.ts:164— _renderOnGridLike has cyclomatic complexity 29 and cognitive complexity 42; 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.
Complex function updateNode (cyclomatic 28, cognitive 49) src/chart/tree/TreeView.ts:327— updateNode has cyclomatic complexity 28 and cognitive complexity 49; 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.
Complex function createMatrixCell (cyclomatic 28, cognitive 36) src/component/matrix/MatrixView.ts:261— createMatrixCell has cyclomatic complexity 28 and cognitive complexity 36; 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.
Complex function convertToEC4RichItem (cyclomatic 28, cognitive 27) src/util/styleCompat.ts:214— convertToEC4RichItem has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Complex function getLayoutRect (cyclomatic 27, cognitive 29) src/util/layout.ts:263— getLayoutRect has cyclomatic complexity 27 and cognitive complexity 29; 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.
Complex function prepareSeriesDataSchema (cyclomatic 26, cognitive 34) src/data/helper/createDimensions.ts:100— prepareSeriesDataSchema has cyclomatic complexity 26 and cognitive complexity 34; 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.
src/core/echarts.ts: 2972 lines of code src/core/echarts.ts:1— src/core/echarts.ts has 2972 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/types.ts: 1960 lines of code src/util/types.ts:1— src/util/types.ts has 1960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/axis/AxisBuilder.ts · ×1
src/component/axis/AxisBuilder.ts: 1450 lines of code src/component/axis/AxisBuilder.ts:1— src/component/axis/AxisBuilder.ts has 1450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/chart/custom/CustomView.ts · ×1
src/chart/custom/CustomView.ts: 1353 lines of code src/chart/custom/CustomView.ts:1— src/chart/custom/CustomView.ts has 1353 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/data/SeriesData.ts: 1321 lines of code src/data/SeriesData.ts:1— src/data/SeriesData.ts has 1321 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/model.ts: 1314 lines of code src/util/model.ts:1— src/util/model.ts has 1314 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/chart/line/LineView.ts: 1293 lines of code src/chart/line/LineView.ts:1— src/chart/line/LineView.ts has 1293 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/data/DataStore.ts: 1156 lines of code src/data/DataStore.ts:1— src/data/DataStore.ts has 1156 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/chart/bar/BarView.ts: 1139 lines of code src/chart/bar/BarView.ts:1— src/chart/bar/BarView.ts has 1139 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/tooltip/TooltipView.ts · ×1
src/component/tooltip/TooltipView.ts: 1120 lines of code src/component/tooltip/TooltipView.ts:1— src/component/tooltip/TooltipView.ts has 1120 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/model/Global.ts: 976 lines of code src/model/Global.ts:1— src/model/Global.ts has 976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/helper/BrushController.ts · ×1
src/component/helper/BrushController.ts: 974 lines of code src/component/helper/BrushController.ts:1— src/component/helper/BrushController.ts has 974 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/dataZoom/SliderZoomView.ts · ×1
src/component/dataZoom/SliderZoomView.ts: 972 lines of code src/component/dataZoom/SliderZoomView.ts:1— src/component/dataZoom/SliderZoomView.ts has 972 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/chart/treemap/TreemapView.ts · ×1
src/chart/treemap/TreemapView.ts: 969 lines of code src/chart/treemap/TreemapView.ts:1— src/chart/treemap/TreemapView.ts has 969 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/coord/cartesian/Grid.ts · ×1
src/coord/cartesian/Grid.ts: 945 lines of code src/coord/cartesian/Grid.ts:1— src/coord/cartesian/Grid.ts has 945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/graphic.ts: 908 lines of code src/util/graphic.ts:1— src/util/graphic.ts has 908 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/visualMap/ContinuousView.ts · ×1
src/component/visualMap/ContinuousView.ts: 864 lines of code src/component/visualMap/ContinuousView.ts:1— src/component/visualMap/ContinuousView.ts has 864 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/coord/View.ts: 833 lines of code src/coord/View.ts:1— src/coord/View.ts has 833 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/chart/bar/PictorialBarView.ts · ×1
src/chart/bar/PictorialBarView.ts: 821 lines of code src/chart/bar/PictorialBarView.ts:1— src/chart/bar/PictorialBarView.ts has 821 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/states.ts: 819 lines of code src/util/states.ts:1— src/util/states.ts has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/label/labelStyle.ts: 781 lines of code src/label/labelStyle.ts:1— src/label/labelStyle.ts has 781 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/number.ts: 770 lines of code src/util/number.ts:1— src/util/number.ts has 770 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/helper/MapDraw.ts · ×1
src/component/helper/MapDraw.ts: 769 lines of code src/component/helper/MapDraw.ts:1— src/component/helper/MapDraw.ts has 769 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/coord/scaleRawExtentInfo.ts · ×1
src/coord/scaleRawExtentInfo.ts: 769 lines of code src/coord/scaleRawExtentInfo.ts:1— src/coord/scaleRawExtentInfo.ts has 769 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/timeline/SliderTimelineView.ts · ×1
src/component/timeline/SliderTimelineView.ts: 734 lines of code src/component/timeline/SliderTimelineView.ts:1— src/component/timeline/SliderTimelineView.ts has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/model/Series.ts: 733 lines of code src/model/Series.ts:1— src/model/Series.ts has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/animation/universalTransition.ts · ×1
src/animation/universalTransition.ts: 724 lines of code src/animation/universalTransition.ts:1— src/animation/universalTransition.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/scale/breakImpl.ts: 721 lines of code src/scale/breakImpl.ts:1— src/scale/breakImpl.ts has 721 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/util/layout.ts: 701 lines of code src/util/layout.ts:1— src/util/layout.ts 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.
src/scale/Time.ts: 699 lines of code src/scale/Time.ts:1— src/scale/Time.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/chart/tree/TreeView.ts: 660 lines of code src/chart/tree/TreeView.ts:1— src/chart/tree/TreeView.ts has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/legend/LegendView.ts · ×1
src/component/legend/LegendView.ts: 658 lines of code src/component/legend/LegendView.ts:1— src/component/legend/LegendView.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/visual/VisualMapping.ts · ×1
src/visual/VisualMapping.ts: 642 lines of code src/visual/VisualMapping.ts:1— src/visual/VisualMapping.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/chart/gauge/GaugeView.ts · ×1
src/chart/gauge/GaugeView.ts: 641 lines of code src/chart/gauge/GaugeView.ts:1— src/chart/gauge/GaugeView.ts has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/chart/treemap/treemapLayout.ts · ×1
src/chart/treemap/treemapLayout.ts: 602 lines of code src/chart/treemap/treemapLayout.ts:1— src/chart/treemap/treemapLayout.ts has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/core/Scheduler.ts: 597 lines of code src/core/Scheduler.ts:1— src/core/Scheduler.ts has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/component/visualMap/VisualMapModel.ts · ×1
src/component/visualMap/VisualMapModel.ts: 595 lines of code src/component/visualMap/VisualMapModel.ts:1— src/component/visualMap/VisualMapModel.ts has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/animation/customGraphicTransition.ts · ×1
src/animation/customGraphicTransition.ts: 590 lines of code src/animation/customGraphicTransition.ts:1— src/animation/customGraphicTransition.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/label/labelGuideHelper.ts · ×1
src/label/labelGuideHelper.ts: 590 lines of code src/label/labelGuideHelper.ts:1— src/label/labelGuideHelper.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/coord/matrix/Matrix.ts: 559 lines of code src/coord/matrix/Matrix.ts:1— src/coord/matrix/Matrix.ts has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency '@microsoft/api-extractor' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'dtslint' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Swallowed exception (empty catch) src/core/Scheduler.ts:652— 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.
Orphaned file src/animation/universalTransition.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/visual/VisualMapping.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/animation/customGraphicTransition.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/label/labelGuideHelper.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/axis/axisBreakHelperImpl.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/helper/BrushTargetManager.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/helper/transform.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/legend/ScrollableLegendView.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/visualMap/PiecewiseModel.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/chart/helper/Line.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/tooltip/tooltipMarkup.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/helper/dataProvider.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/graphic/GraphicView.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/util/time.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/model/OptionManager.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/Graph.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/axisPointer/BaseAxisPointer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/helper/sourceManager.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/coord/calendar/Calendar.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/calendar/CalendarView.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/graphic/GraphicModel.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/component/toolbox/ToolboxView.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/helper/sourceHelper.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file theme/v5.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/data/helper/createDimensions.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate src/component/marker/MarkAreaView.ts:103— `!isNaN(val as number) && !isFinite(val as number)` appears character-identically in 2 files — src/component/marker/MarkAreaView.ts, src/component/marker/MarkLineView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/sunburst/SunburstSeries.ts:315— `!viewRoot || (viewRoot !== root && !root.contains(viewRoot))` appears character-identically in 2 files — src/chart/sunburst/SunburstSeries.ts, src/chart/treemap/TreemapSeries.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/map/MapSeries.ts:152— `(region as GeoJSONRegion).properties && (region as GeoJSONRegion).properties.echartsStyle` appears character-identically in 2 files — src/chart/map/MapSeries.ts, src/coord/geo/geoCreator.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/bar/PictorialBarView.ts:263— `(symbolRotate || 0) * Math.PI / 180 || 0` appears character-identically in 4 files — src/chart/bar/PictorialBarView.ts, src/chart/helper/EffectSymbol.ts, src/chart/helper/Symbol.ts, src/component/timeline/SliderTimelineView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/tooltip/TooltipHTMLContent.ts:388— `alwaysShowContent && this._moveIfResized()` appears character-identically in 2 files — src/component/tooltip/TooltipHTMLContent.ts, src/component/tooltip/TooltipRichContent.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/axis/CartesianAxisView.ts:230— `axisBreakHelper && scale.type !== 'ordinal'` appears character-identically in 2 files — src/component/axis/CartesianAxisView.ts, src/component/axis/SingleAxisView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/axisPointer/CartesianAxisPointer.ts:55— `axisPointerType && axisPointerType !== 'none'` appears character-identically in 3 files — src/component/axisPointer/CartesianAxisPointer.ts, src/component/axisPointer/PolarAxisPointer.ts, src/component/axisPointer/SingleAxisPointer.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/scale/Interval.ts:300— `brkAvailable && opt.breakTicks !== 'none'` appears character-identically in 2 files — src/scale/Interval.ts, src/scale/Time.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate theme/azul.js:37— `console && console.error && console.error(msg)` appears character-identically in 35 files — theme/azul.js, theme/bee-inspired.js, theme/blue.js, theme/caravan.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/pie/PieView.ts:138— `cursorStyle && sector.attr('cursor', cursorStyle)` appears character-identically in 2 files — src/chart/pie/PieView.ts, src/chart/sunburst/SunburstPiece.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:103— `dataAll.getName(rawIdx) || (rawIdx + '')` appears character-identically in 2 files — REDACTED, src/visual/style.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/coord/axisNiceTicks.ts:258— `isIntervalScale(scale) || isTimeScale(scale)` appears character-identically in 2 files — src/coord/axisNiceTicks.ts, src/scale/helper.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/dataZoom/AxisProxy.ts:285— `isOrdinalScale(scale) || isTimeScale(scale)` appears character-identically in 2 files — src/component/dataZoom/AxisProxy.ts, src/component/dataZoom/SliderZoomView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/chord/ChordEdge.ts:192— `isString(sourceColor) && isString(targetColor)` appears character-identically in 2 files — src/chart/chord/ChordEdge.ts, src/chart/sankey/SankeyView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/funnel/FunnelSeries.ts:138— `labelLineEmphasisOpt.show && option.emphasis.label.show` appears character-identically in 2 files — src/chart/funnel/FunnelSeries.ts, src/chart/pie/PieSeries.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/funnel/FunnelSeries.ts:136— `labelLineNormalOpt.show && option.label.show` appears character-identically in 2 files — src/chart/funnel/FunnelSeries.ts, src/chart/pie/PieSeries.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/coord/axisNiceTicks.ts:137— `maxInterval != null && interval > maxInterval` appears character-identically in 2 files — src/coord/axisNiceTicks.ts, src/scale/helper.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/coord/axisNiceTicks.ts:134— `minInterval != null && interval < minInterval` appears character-identically in 2 files — src/coord/axisNiceTicks.ts, src/scale/helper.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/boxplot/BoxplotView.ts:60— `needClip && createClipPath(coordSys, false, seriesModel)` appears character-identically in 2 files — src/chart/boxplot/BoxplotView.ts, src/chart/candlestick/CandlestickView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/scale/Log.ts:181— `opt && opt.depth === SCALE_MAPPER_DEPTH_OUT_OF_BREAK` appears character-identically in 2 files — src/scale/Log.ts, src/scale/breakImpl.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/chord/ChordSeries.ts:222— `pathArr && (pathArr[0] === 'label' || pathArr[1] === 'label')` appears character-identically in 2 files — src/chart/chord/ChordSeries.ts, src/chart/graph/GraphSeries.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/axisPointer/axisTrigger.ts:121— `payload.dispatchAction || bind(api.dispatchAction, api)` appears character-identically in 2 files — src/component/axisPointer/axisTrigger.ts, src/component/tooltip/TooltipView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/coord/cartesian/Axis2D.ts:97— `position === 'top' || position === 'bottom'` appears character-identically in 2 files — src/coord/cartesian/Axis2D.ts, src/coord/single/SingleAxis.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/chart/pie/PieView.ts:314— `radius <= itemLayout.r && radius >= itemLayout.r0` appears character-identically in 2 files — src/chart/pie/PieView.ts, src/chart/sunburst/SunburstView.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/component/axis/AngleAxisView.ts:266— `rawCategoryData && rawCategoryData[tickValue]` appears character-identically in 2 files — src/component/axis/AngleAxisView.ts, src/component/axis/AxisBuilder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Deprecated: abab REDACTED:2773— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: domexception REDACTED:4318— domexception 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5550— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: har-validator REDACTED:5646— har-validator 5.1.5 is resolved in REDACTED and is marked deprecated by its publisher: "this library is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: request REDACTED:9474— request 2.88.2 is resolved in REDACTED and is marked deprecated by its publisher: "request has been deprecated, see https://github.com/request/request/issues/3142". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:9519— uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:9601— resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:9638— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: sane REDACTED:9725— sane 4.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve REDACTED:10394— source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-url REDACTED:10428— source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: urix REDACTED:11512— urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: w3c-hr-time REDACTED:11631— w3c-hr-time 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native performance.now() and performance.timeOrigin.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Blanket warning suppression extension-src/dataTool/gexf.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression extension-src/dataTool/index.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/chart/helper/multipleGraphEdgeHelper.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/chart/radar/backwardCompat.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/component/timeline/preprocessor.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/component/toolbox/feature/Brush.ts:136— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/component/visualMap/preprocessor.ts:20— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/core/Scheduler.ts:673— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
R7 · Dead Code· Unused private field 'internalField' · ×5
Unused private field 'internalField' src/core/echarts.ts:1668— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
Unused private field 'internalField' src/data/DataStore.ts:1297— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
Unused private field 'internalField' src/data/SeriesData.ts:1385— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
Unused private field 'internalField' src/data/helper/dataProvider.ts:157— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
Unused private field 'internalField' src/model/Global.ts:910— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file src/chart/treemap/TreemapView.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/util/states.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/component/timeline/SliderTimelineView.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 39 significant file(s) lose their only recent owner: src/util/model.ts, src/coord/cartesian/Grid.ts, src/coord/View.ts, src/scale/breakImpl.ts, src/core/Scheduler.ts, src/chart/tree/TreeView.ts, src/label/labelLayoutHelper.ts, src/component/dataZoom/AxisProxy.ts (+31 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: src/chart/chord/chordLayout.ts, src/component/marker/markerHelper.ts, src/coord/calendar/CalendarModel.ts, src/chart/chord/ChordPiece.ts, src/visual/tokens.ts. Pair on, review, or document these before any departure.
Fat interface: Map (19 required operations) extension-src/bmap/BMapCoordSys.ts:36— `Map` declares 19 required operations: `pointToOverlayPixel`, `overlayPixelToPoint`, `getPanes`, `getCenter`, `getZoom`, `addOverlay`, `centerAndZoom`, `addEventListener`, `removeEventListener`, `enableDragging`, `disableDragging`, `enableScrollWheelZoom`, `disableScrollWheelZoom`, `enableDoubleClickZoom`, `disableDoubleClickZoom`, `enablePinchToZoom`, `disablePinchToZoom`, `setMapStyle`, `setMapStyleV2`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (50 single-owned of 406 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 406 of the 645 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/component/helper/BrushController.ts, src/component/visualMap/preprocessor.ts, src/i18n/langLV.ts, src/i18n/langDE.ts, src/component/helper/cursorHelper.ts, src/data/Source.ts.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (122455 LoC, 1238 module-visible types across 85 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Scattered collaborators — 42 % of calls cross a namespace and only 45 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 315 of 452 significant files have no living knowledge, while the repository is still being changed at a low rate (15 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 315 separate risks. Counted over 452 of the 645 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 10454 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Write-only private field '_zoom' · ×1
Write-only private field '_zoom' extension-src/bmap/BMapCoordSys.ts:118— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code· Write-only private field '_center' · ×1
Write-only private field '_center' extension-src/bmap/BMapCoordSys.ts:119— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code· Write-only private field '_progressiveEls' · ×1
Write-only private field '_progressiveEls' src/chart/parallel/ParallelView.ts:51— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code· Unused private field '_currentIndex' · ×1
Unused private field '_currentIndex' src/component/legend/ScrollableLegendView.ts:82— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Unused private field '_viewRect' · ×1
Unused private field '_viewRect' src/component/timeline/SliderTimelineView.ts:92— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Write-only private field '_mapName' · ×1
Write-only private field '_mapName' src/coord/geo/GeoSVGResource.ts:71— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 0/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~0.1 `!` null assertions per 1k TypeScript source lines — 8 assertion(s) across the 140053 source line(s) of the 603 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: src/component/axis/axisBreakHelperImpl.ts (6), src/component/axis/AxisBuilder.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Silent fallback default in catch src/util/log.ts:111— `makePrintable` swallows every exception into `return '?'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated (npm): tslib — tslib is pinned at 2.3.0; registry.npmjs.org publishes 2.8.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a17886-7b69-7a79-9a3a-d6ae51347354 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 52 · Warnings: 988 · Recommendations: 396 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 14:04 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.