Public report of perspective-dev/perspective, published 14 November 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.11.4). Assert 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, 14 November 2026, 16:11 UTC · Survey ID cd_a9bf1f6169894c6eb8601714c8dea784
perspective-dev/perspective
Measured 14 November 2026, 16:11 UTC, at code version 56038ac
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: 126,823 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Accessibility, 32
Findings by how serious they are
135 critical1117 serious143 minor
19 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 16:11 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer 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. We work 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 ▸
67of 67 dimensions measured by tools.
1358of 1395 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
67dimensions across 7 lenses, read from 126,823 lines of product code in 22 projects.
perspective-dev/perspective is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 41 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 32, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 5 points. Adding text alternatives comes next, worth about 4 points. Raising Accessibility to 70 would lift the score to about 49.
Eighty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-five known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. Passing outside input through environment variables would fix the four pipeline steps that put outside input straight into a shell command, and the two places where the code runs text as code or as a command need a direct call instead. The two loops of files that import each other need breaking.
The product code is 126,823 lines, about €110,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.
If Accessibility rose from 32 to 70, the lowest score rated Strong, the score would rise from 41 to about 49.
Code composition: what the lines of code are
Product code 100%Tests 0%
New since the last survey: 321 findings
These 321 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FunctionTooLong: index.createDataListener.dataListener packages/viewer-datagrid/src/ts/data_listener/index.ts
God Classes · FileTooLong: perspective-viewer/tools.mjs rust/perspective-viewer/tools.mjs
God Classes · MethodTooLong: ViewQueryContext.build_query_ordered rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs
God Classes · FunctionTooLong: last-group-by-split.lastGroupBySplit packages/viewer-charts/src/ts/data/last-group-by-split.ts
God Classes · FileTooLong: client/client_async.rs rust/perspective-python/src/client/client_async.rs
God Classes · ClassTooLong: JsServerHandler rust/perspective-js/src/rust/virtual_server.rs
God Classes · TooManyMethods: GenericSQLVirtualServerModel rust/perspective-client/src/rust/virtual_server/generic_sql_model.rs
Code Duplication · Edited copy of a member (81 corresponding lines) rust/perspective-viewer/src/rust/tasks/copy_export.rs
Code Duplication · Edited copies of one member (3 members, 67+ corresponding lines) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs
Code Duplication · Edited copy of a member (47 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (43 corresponding lines) rust/perspective-client/src/rust/config/view_config.rs
Code Duplication · Edited copy of a member (46 corresponding lines) rust/perspective-python/src/client/pandas.rs
Code Duplication · Edited copy of a member (50 corresponding lines) rust/perspective-viewer/src/rust/components/viewer/wiring.rs
Code Duplication · Edited copy of a member (24 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (33 corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copy of a member (32 corresponding lines) rust/perspective-viewer/src/rust/components/column_dropdown.rs
Code Duplication · Edited copy of a member (24 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (25 corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs
Code Duplication · Edited copy of a member (25 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (24 corresponding lines) rust/perspective-python/src/server/generic_sql_model.rs
Code Duplication · Edited copy of a member (30 corresponding lines) rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs
Code Duplication · Edited copy of a member (18 corresponding lines) rust/perspective-python/src/server/server_async.rs
Code Duplication · Edited copy of a member (18 corresponding lines) rust/perspective-viewer/src/rust/ui/form/select_enum_field.rs
Code Duplication · Edited copy of a member (18 corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs
Code Duplication · Edited copy of a member (20 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py
Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs
Code Duplication · Edited copy of a member (15 corresponding lines) rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs
Code Duplication · Edited copy of a member (19 corresponding lines) rust/perspective-client/src/rust/view.rs
Code Duplication · Edited copy of a member (17 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (16 corresponding lines) rust/perspective-viewer/src/rust/presentation.rs
Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs
Code Duplication · Edited copy of a member (14 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (19 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py
Code Duplication · Edited copy of a member (11 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs
Code Duplication · Edited copy of a member (23 corresponding lines) rust/perspective-viewer/src/rust/tasks/apply_config_defaults.rs
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) rust/perspective-js/src/rust/generic_sql_model.rs
Code Duplication · Edited copy of a member (16 corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs
Code Duplication · Edited copy of a member (10 corresponding lines) rust/perspective-js/src/rust/view.rs
Code Duplication · Edited copy of a member (13 corresponding lines) rust/perspective-client/src/rust/table.rs
Code Duplication · Edited copy of a member (14 corresponding lines) rust/perspective-client/src/rust/client.rs
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) rust/perspective-client/src/rust/view.rs
Code Duplication · Edited copy of a member (11 corresponding lines) rust/perspective-js/src/rust/table.rs
Code Duplication · Edited copy of a member (13 corresponding lines) rust/perspective-js/src/rust/utils/local_poll_loop.rs
Code Duplication · Edited copy of a member (10 corresponding lines) rust/perspective-client/src/rust/utils/mod.rs
Code Duplication · Edited copy of a member (12 corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copy of a member (8 corresponding lines) rust/perspective-js/src/rust/table.rs
Code Duplication · Edited copy of a member (9 corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) rust/perspective-client/src/rust/table.rs
Code Duplication · Edited copy of a member (7 corresponding lines) rust/perspective-viewer/src/rust/agent/tools.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs
Code Duplication · Edited copy of a member (14 corresponding lines) rust/perspective-viewer/src/rust/tasks/edit_expression.rs
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) rust/perspective-client/src/rust/client.rs
Code Duplication · Edited copy of a member (13 corresponding lines) rust/perspective-viewer/src/rust/tasks/copy_export.rs
Code Duplication · Edited copy of a member (11 corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copy of a member (12 corresponding lines) rust/perspective-viewer/src/rust/tasks/edit_expression.rs
Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) rust/perspective-python/src/server/generic_sql_model.rs
Code Duplication · Edited copies of one member (5 members, 7+ corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copy of a member (6 corresponding lines) rust/perspective-python/src/client/client_async.rs
Code Duplication · Edited copy of a member (10 corresponding lines) rust/perspective-viewer/src/rust/renderer/config_defaults.rs
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) rust/perspective-python/src/client/pandas.rs
Code Duplication · Edited copy of a member (11 corresponding lines) rust/perspective-viewer/src/rust/custom_events.rs
Code Duplication · Edited copy of a member (14 corresponding lines) rust/perspective-viewer/src/rust/renderer.rs
Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) rust/perspective-js/src/rust/generic_sql_model.rs
Code Duplication · Edited copy of a member (8 corresponding lines) rust/perspective-python/src/client/client_async.rs
We compare 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: 235 findings
These 235 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one. The first 100 are listed here.
€36,000 to €180,000, for 600 to 1,903 hours of work, about 0.7 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 41. 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: 126,823 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: We price 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
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 4 points · Medium effort · Text alternatives
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 4 points · Medium effort · Page structure
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 €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Accessibility, at 32 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. 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.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 93,457 lines over the last 90 days, which is about 379,020 lines a year. At that pace, the extra work comes to an estimated 38.2 to 229 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 our 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 · Code Duplication · 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 — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
539 modules, with 922 dependencies between them. 9 loops run through 30 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 499 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.
packages.viewer-charts.src.ts.axis uses docs.src.data.theme, so a change to docs.src.data.theme can break packages.viewer-charts.src.ts.axis, while a change to packages.viewer-charts.src.ts.axis can't break docs.src.data.theme.
Position
Below the diagonal: packages.viewer-charts.src.ts.axis uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.axis uses packages.viewer-charts.src.ts.layout.plot-layout, so a change to packages.viewer-charts.src.ts.layout.plot-layout can break packages.viewer-charts.src.ts.axis, while a change to packages.viewer-charts.src.ts.axis can't break packages.viewer-charts.src.ts.layout.plot-layout.
Position
Below the diagonal: packages.viewer-charts.src.ts.axis uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.common uses docs.src.data.theme, so a change to docs.src.data.theme can break packages.viewer-charts.src.ts.charts.common, while a change to packages.viewer-charts.src.ts.charts.common can't break docs.src.data.theme.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.common uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.common uses packages.viewer-charts.src.ts.layout.plot-layout, so a change to packages.viewer-charts.src.ts.layout.plot-layout can break packages.viewer-charts.src.ts.charts.common, while a change to packages.viewer-charts.src.ts.charts.common can't break packages.viewer-charts.src.ts.layout.plot-layout.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.common uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.viewer-charts.src.ts.webgl.context-manager uses a type in packages.viewer-charts.src.ts.webgl.shader-registry.
packages.viewer-charts.src.ts.webgl.context-manager uses packages.viewer-charts.src.ts.webgl.shader-registry, so a change to packages.viewer-charts.src.ts.webgl.shader-registry can break packages.viewer-charts.src.ts.webgl.context-manager, while a change to packages.viewer-charts.src.ts.webgl.context-manager can't break packages.viewer-charts.src.ts.webgl.shader-registry.
Position
Below the diagonal: packages.viewer-charts.src.ts.webgl.context-manager uses a module listed above it, which is the healthy direction.
perspective_client.rust.config.view_config uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_client.rust.config.view_config, while a change to perspective_client.rust.config.view_config can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_client.rust.config.view_config uses a module listed above it, which is the healthy direction.
17→20 perspective_client.rust.view uses perspective_client.rust.tablepart of a loop✕
Connections
1 pair of types, where a type in perspective_client.rust.view uses a type in perspective_client.rust.table.
perspective_client.rust.view uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_client.rust.view, while a change to perspective_client.rust.view can't break perspective_client.rust.table.
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.
17→24 perspective_client.rust.view uses perspective_client.rust.clientpart of a loop✕
Connections
1 pair of types, where a type in perspective_client.rust.view uses a type in perspective_client.rust.client.
perspective_client.rust.view uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_client.rust.view, while a change to perspective_client.rust.view can't break perspective_client.rust.client.
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.
perspective_viewer.rust.presentation uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.presentation, while a change to perspective_viewer.rust.presentation can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.presentation uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.presentation uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.presentation, while a change to perspective_viewer.rust.presentation can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.presentation uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.presentation uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.presentation, while a change to perspective_viewer.rust.presentation can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.presentation uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.chart uses packages.viewer-charts.src.ts.webgl.context-manager, so a change to packages.viewer-charts.src.ts.webgl.context-manager can break packages.viewer-charts.src.ts.charts.chart, while a change to packages.viewer-charts.src.ts.charts.chart can't break packages.viewer-charts.src.ts.webgl.context-manager.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.chart uses a module listed above it, which is the healthy direction.
perspective_client.rust.table uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_client.rust.table, while a change to perspective_client.rust.table can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_client.rust.table uses a module listed above it, which is the healthy direction.
perspective_client.rust.table uses perspective_client.rust.view, so a change to perspective_client.rust.view can break perspective_client.rust.table, while a change to perspective_client.rust.table can't break perspective_client.rust.view.
Position
Below the diagonal: perspective_client.rust.table uses a module listed above it, which is the healthy direction.
20→24 perspective_client.rust.table uses perspective_client.rust.clientpart of a loop✕
Connections
1 pair of types, where a type in perspective_client.rust.table uses a type in perspective_client.rust.client.
perspective_client.rust.table uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_client.rust.table, while a change to perspective_client.rust.table can't break perspective_client.rust.client.
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.
perspective_viewer.rust.config.plugin_static_config uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.config.plugin_static_config, while a change to perspective_viewer.rust.config.plugin_static_config can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.config.plugin_static_config uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.chart-base uses docs.src.data.theme, so a change to docs.src.data.theme can break packages.viewer-charts.src.ts.charts.chart-base, while a change to packages.viewer-charts.src.ts.charts.chart-base can't break docs.src.data.theme.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.chart-base uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.chart-base uses packages.viewer-charts.src.ts.webgl.context-manager, so a change to packages.viewer-charts.src.ts.webgl.context-manager can break packages.viewer-charts.src.ts.charts.chart-base, while a change to packages.viewer-charts.src.ts.charts.chart-base can't break packages.viewer-charts.src.ts.webgl.context-manager.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.chart-base uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.chart-base uses packages.viewer-charts.src.ts.charts.chart, so a change to packages.viewer-charts.src.ts.charts.chart can break packages.viewer-charts.src.ts.charts.chart-base, while a change to packages.viewer-charts.src.ts.charts.chart-base can't break packages.viewer-charts.src.ts.charts.chart.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.chart-base uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.viewer-charts.src.ts.charts.series.series uses a type in packages.viewer-charts.src.ts.webgl.context-manager.
packages.viewer-charts.src.ts.charts.series.series uses packages.viewer-charts.src.ts.webgl.context-manager, so a change to packages.viewer-charts.src.ts.webgl.context-manager can break packages.viewer-charts.src.ts.charts.series.series, while a change to packages.viewer-charts.src.ts.charts.series.series can't break packages.viewer-charts.src.ts.webgl.context-manager.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.series.series uses a module listed above it, which is the healthy direction.
packages.viewer-charts.src.ts.charts.series.series uses packages.viewer-charts.src.ts.charts.chart, so a change to packages.viewer-charts.src.ts.charts.chart can break packages.viewer-charts.src.ts.charts.series.series, while a change to packages.viewer-charts.src.ts.charts.series.series can't break packages.viewer-charts.src.ts.charts.chart.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.series.series uses a module listed above it, which is the healthy direction.
perspective_client.rust.client uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_client.rust.client, while a change to perspective_client.rust.client can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_client.rust.client uses a module listed above it, which is the healthy direction.
perspective_client.rust.client uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_client.rust.client, while a change to perspective_client.rust.client can't break perspective_client.rust.table.
Position
Below the diagonal: perspective_client.rust.client uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.props uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.session.props, while a change to perspective_viewer.rust.session.props can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.session.props uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.props uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.session.props, while a change to perspective_viewer.rust.session.props can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.session.props uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.props uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.session.props, while a change to perspective_viewer.rust.session.props can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.session.props uses a module listed above it, which is the healthy direction.
25→29 perspective_viewer.rust.session.props uses perspective_viewer.rust.sessionpart of a loop✕
Connections
1 pair of types, where a type in perspective_viewer.rust.session.props uses a type in perspective_viewer.rust.session.
perspective_viewer.rust.session.props uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.session.props, while a change to perspective_viewer.rust.session.props can't break perspective_viewer.rust.session.
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.
1 pair of types, where a type in packages.viewer-charts.src.ts.charts.cartesian.cartesian uses a type in packages.viewer-charts.src.ts.webgl.context-manager.
packages.viewer-charts.src.ts.charts.cartesian.cartesian uses packages.viewer-charts.src.ts.webgl.context-manager, so a change to packages.viewer-charts.src.ts.webgl.context-manager can break packages.viewer-charts.src.ts.charts.cartesian.cartesian, while a change to packages.viewer-charts.src.ts.charts.cartesian.cartesian can't break packages.viewer-charts.src.ts.webgl.context-manager.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.cartesian.cartesian uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.viewer-charts.src.ts.charts.cartesian.cartesian uses a type in packages.viewer-charts.src.ts.charts.chart-base.
packages.viewer-charts.src.ts.charts.cartesian.cartesian uses packages.viewer-charts.src.ts.charts.chart-base, so a change to packages.viewer-charts.src.ts.charts.chart-base can break packages.viewer-charts.src.ts.charts.cartesian.cartesian, while a change to packages.viewer-charts.src.ts.charts.cartesian.cartesian can't break packages.viewer-charts.src.ts.charts.chart-base.
Position
Below the diagonal: packages.viewer-charts.src.ts.charts.cartesian.cartesian uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.metadata uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.session.metadata, while a change to perspective_viewer.rust.session.metadata can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.session.metadata uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.metadata uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_viewer.rust.session.metadata, while a change to perspective_viewer.rust.session.metadata can't break perspective_client.rust.table.
Position
Below the diagonal: perspective_viewer.rust.session.metadata uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.metadata uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_viewer.rust.session.metadata, while a change to perspective_viewer.rust.session.metadata can't break perspective_client.rust.client.
Position
Below the diagonal: perspective_viewer.rust.session.metadata uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.panel_state uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_viewer.rust.session.panel_state uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.panel_state uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.session.panel_state uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.panel_state uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_client.rust.table.
Position
Below the diagonal: perspective_viewer.rust.session.panel_state uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.panel_state uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_client.rust.client.
Position
Below the diagonal: perspective_viewer.rust.session.panel_state uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session.panel_state uses perspective_viewer.rust.session.metadata, so a change to perspective_viewer.rust.session.metadata can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_viewer.rust.session.metadata.
Position
Below the diagonal: perspective_viewer.rust.session.panel_state uses a module listed above it, which is the healthy direction.
28→29 perspective_viewer.rust.session.panel_state uses perspective_viewer.rust.sessionpart of a loop✕
Connections
1 pair of types, where a type in perspective_viewer.rust.session.panel_state uses a type in perspective_viewer.rust.session.
perspective_viewer.rust.session.panel_state uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.session.panel_state, while a change to perspective_viewer.rust.session.panel_state can't break perspective_viewer.rust.session.
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.
perspective_viewer.rust.session uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_client.rust.view, so a change to perspective_client.rust.view can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_client.rust.view.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_client.rust.table.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_client.rust.client.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_viewer.rust.session.metadata, so a change to perspective_viewer.rust.session.metadata can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.session.metadata.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.session uses perspective_viewer.rust.session.panel_state, so a change to perspective_viewer.rust.session.panel_state can break perspective_viewer.rust.session, while a change to perspective_viewer.rust.session can't break perspective_viewer.rust.session.panel_state.
Position
Below the diagonal: perspective_viewer.rust.session uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer.plugin_config uses perspective_viewer.rust.config.column_config_schema, so a change to perspective_viewer.rust.config.column_config_schema can break perspective_viewer.rust.renderer.plugin_config, while a change to perspective_viewer.rust.renderer.plugin_config can't break perspective_viewer.rust.config.column_config_schema.
Position
Below the diagonal: perspective_viewer.rust.renderer.plugin_config uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer.plugin_config uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.renderer.plugin_config, while a change to perspective_viewer.rust.renderer.plugin_config can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.renderer.plugin_config uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer.plugin_config uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.renderer.plugin_config, while a change to perspective_viewer.rust.renderer.plugin_config can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.renderer.plugin_config uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer.plugin_config uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.renderer.plugin_config, while a change to perspective_viewer.rust.renderer.plugin_config can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.renderer.plugin_config uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_js.rust.utils.futures, so a change to perspective_js.rust.utils.futures can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_js.rust.utils.futures.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_viewer.rust.config.column_config_schema, so a change to perspective_viewer.rust.config.column_config_schema can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_viewer.rust.config.column_config_schema.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_client.rust.view, so a change to perspective_client.rust.view can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_client.rust.view.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_client.rust.table, so a change to perspective_client.rust.table can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_client.rust.table.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_client.rust.client.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.renderer uses perspective_viewer.rust.renderer.plugin_config, so a change to perspective_viewer.rust.renderer.plugin_config can break perspective_viewer.rust.renderer, while a change to perspective_viewer.rust.renderer can't break perspective_viewer.rust.renderer.plugin_config.
Position
Below the diagonal: perspective_viewer.rust.renderer uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector.config_selector uses a type in perspective_viewer.rust.presentation.column_locator.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector.config_selector uses a type in perspective_viewer.rust.utils.ptr_eq_rc.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector.config_selector uses a type in perspective_viewer.rust.presentation.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector.config_selector uses a type in perspective_viewer.rust.config.plugin_static_config.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector.config_selector uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.column_selector.config_selector, while a change to perspective_viewer.rust.components.column_selector.config_selector can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector.config_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_client.rust.client, so a change to perspective_client.rust.client can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_client.rust.client.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_viewer.rust.session.panel_state, so a change to perspective_viewer.rust.session.panel_state can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_viewer.rust.session.panel_state.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.workspace uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.workspace, while a change to perspective_viewer.rust.workspace can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.workspace uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector uses a type in perspective_viewer.rust.presentation.column_locator.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_client.rust.config.view_config, so a change to perspective_client.rust.config.view_config can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_client.rust.config.view_config.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in perspective_viewer.rust.components.column_selector uses a type in perspective_viewer.rust.config.plugin_static_config.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.session.metadata, so a change to perspective_viewer.rust.session.metadata can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.session.metadata.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.column_selector uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.components.column_selector, while a change to perspective_viewer.rust.components.column_selector can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.components.column_selector uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.main_panel uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.components.main_panel, while a change to perspective_viewer.rust.components.main_panel can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.components.main_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.config.plugin_static_config, so a change to perspective_viewer.rust.config.plugin_static_config can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.config.plugin_static_config.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.settings_panel uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.components.settings_panel, while a change to perspective_viewer.rust.components.settings_panel can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.components.settings_panel uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.utils.ptr_eq_rc, so a change to perspective_viewer.rust.utils.ptr_eq_rc can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.utils.ptr_eq_rc.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.status_bar uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.components.status_bar, while a change to perspective_viewer.rust.components.status_bar can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.components.status_bar uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.custom_elements.viewer uses perspective_js.rust.utils.futures, so a change to perspective_js.rust.utils.futures can break perspective_viewer.rust.custom_elements.viewer, while a change to perspective_viewer.rust.custom_elements.viewer can't break perspective_js.rust.utils.futures.
Position
Below the diagonal: perspective_viewer.rust.custom_elements.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.custom_elements.viewer uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.custom_elements.viewer, while a change to perspective_viewer.rust.custom_elements.viewer can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.custom_elements.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.custom_elements.viewer uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.custom_elements.viewer, while a change to perspective_viewer.rust.custom_elements.viewer can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.custom_elements.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.custom_elements.viewer uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.custom_elements.viewer, while a change to perspective_viewer.rust.custom_elements.viewer can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.custom_elements.viewer uses a module listed above it, which is the healthy direction.
38→39 perspective_viewer.rust.custom_elements.viewer uses perspective_viewer.rust.agent.toolspart of a loop✕
Connections
1 pair of types, where a type in perspective_viewer.rust.custom_elements.viewer uses a type in perspective_viewer.rust.agent.tools.
perspective_viewer.rust.custom_elements.viewer uses perspective_viewer.rust.agent.tools, so a change to perspective_viewer.rust.agent.tools can break perspective_viewer.rust.custom_elements.viewer, while a change to perspective_viewer.rust.custom_elements.viewer can't break perspective_viewer.rust.agent.tools.
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.
perspective_viewer.rust.agent.tools uses perspective_viewer.rust.config.column_config_schema, so a change to perspective_viewer.rust.config.column_config_schema can break perspective_viewer.rust.agent.tools, while a change to perspective_viewer.rust.agent.tools can't break perspective_viewer.rust.config.column_config_schema.
Position
Below the diagonal: perspective_viewer.rust.agent.tools uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.agent.tools uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.agent.tools, while a change to perspective_viewer.rust.agent.tools can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.agent.tools uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.agent.tools uses perspective_viewer.rust.custom_elements.viewer, so a change to perspective_viewer.rust.custom_elements.viewer can break perspective_viewer.rust.agent.tools, while a change to perspective_viewer.rust.agent.tools can't break perspective_viewer.rust.custom_elements.viewer.
Position
Below the diagonal: perspective_viewer.rust.agent.tools uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_client.rust.config.filters, so a change to perspective_client.rust.config.filters can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_client.rust.config.filters.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.presentation.column_locator, so a change to perspective_viewer.rust.presentation.column_locator can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.presentation.column_locator.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.utils.pubsub, so a change to perspective_viewer.rust.utils.pubsub can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.utils.pubsub.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.presentation, so a change to perspective_viewer.rust.presentation can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.presentation.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.session.props, so a change to perspective_viewer.rust.session.props can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.session.props.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.session, so a change to perspective_viewer.rust.session can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.session.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.renderer, so a change to perspective_viewer.rust.renderer can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.renderer.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.workspace, so a change to perspective_viewer.rust.workspace can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.workspace.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
perspective_viewer.rust.components.viewer uses perspective_viewer.rust.components.settings_panel, so a change to perspective_viewer.rust.components.settings_panel can break perspective_viewer.rust.components.viewer, while a change to perspective_viewer.rust.components.viewer can't break perspective_viewer.rust.components.settings_panel.
Position
Below the diagonal: perspective_viewer.rust.components.viewer uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 45% · Weak · gated by D2, R3, R7, X4 ·
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
A05:2025 — Injection
102
High / Critical
A03:2025 — Software Supply Chain Failures
83
High / Critical
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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 — 135
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 — 1117
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 — 143
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 19
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 67 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 67 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, 1358 of 1395 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 90 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cpp (59,414 lines, 32% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication. Duplication in .ts is measured by R10 Code Duplication and is not part of this gap.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (@playwright/test), docs/ (puppeteer), packages/cli/ (puppeteer) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2,826 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 5 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .ts, .js, .tsx, .mjs) and this repository declares a Cargo test suite (repository root, 12 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D26 Project Cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Project size and spread are measured over build units whose source a code model reads. This repository's .cpp source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts`, `packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts`, `packages/viewer-charts/src/ts/charts/chart-base.ts`, `packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts`, `packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts`, … (+10 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docs/compose.yml). compose up failed (exit 18 — an image could not be pulled) — minio Error pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied minio-init Error context canceled mdbook Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: mdbook Pulling minio-init Error pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied minio Error context canceled mdbook Error context canceled Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 112 further occurrence(s) are not listed individually; the score already reflects all 152.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 152 further occurrence(s) are not listed individually; the score already reflects all 192.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 123 further occurrence(s) are not listed individually; the score already reflects all 163.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X30 Support guard that admits what it rejects — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 32 further occurrence(s) are not listed individually; the score already reflects all 72.
Repo exclusion declarations: 30 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
113 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was series-build.buildSeriesPipeline at 154. A further 6 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 ExportMethod::as_filename at 22 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: rust/perspective-viewer/src/rust/config/export_method.rs (ExportMethod::as_filename at 22), rust/perspective-viewer/src/rust/tasks/copy_export.rs (perspective_viewer::rust::tasks::copy_export::export_selection_to_blob at 22), packages/viewer-charts/src/ts/interaction/zoom-controller.ts (ZoomController.attach at 21), packages/viewer-charts/src/ts/worker/dispatch.ts (dispatch.dispatch at 19), rust/perspective-js/src/rust/utils/errors.rs (ApiError::kind at 18). 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.
+ 90 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with series-build.buildSeriesPipeline (cyclomatic 154). — Refactoring it lifts Cyclomatic Complexity from 5.3 to about 5.6/10.
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.
+ 134 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with series-build.buildSeriesPipeline (cognitive 369), cartesian-build.processCartesianChunk (cognitive 173). — 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 2 together lifts Cognitive Complexity from 2.0 to about 4.0/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.4 / 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 41 FunctionTooLong finding(s) in God Classes — start with series-render.ts (4), heatmap-render.ts (4), cartesian-build.ts (2). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 26 FileTooLong finding(s) in God Classes — start with series-render.ts, viewer.rs, session.rs. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 20 MethodTooLong finding(s) in God Classes — start with config_selector.rs (2), render.rs (2), column_settings_sidebar.rs (2). — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
90 duplicated block group(s) detected. 3.4 % of the production lines (4,271 of 126,823) are in a reported copy. A further 90 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 180 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .cpp (32% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count. Measured on part of this repository only: .ts (26% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 78 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with virtual_server_sync.rs (2), aggregate_selector.rs, primitive_field.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 7 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with client_async.rs, presentation.rs, view.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with column_dropdown.rs (2), charts.rs, wiring.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
22 production modules (Cargo+npm+Python+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 11 of the 22 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: perspective-client · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_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 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with presentation.rs, viewer.rs, session.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.0 / 10Stronggated by 153 serious findings✓ 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.
90 skipped (3 with a documented reason), 65 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2826 tests. Measured on the JavaScript/TypeScript suite only — at least 5 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
Skipped test: columns > overwrites a duplicate expression alias · ×87rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:217
No assertions: delete an unused window column from the editor · ×65rust/perspective-viewer/test/js/windows.spec.ts:223
Test project verifies nothing: packages/jupyterlabpackages/jupyterlab/test/jupyter/utils.mjs:133
Resolve the 87 Skipped test finding(s) in Test Quality — start with updates.spec.js (13), constructors.spec.js (8), string.spec.js (6). — One of this dimension's main actionable groups (87 warning-level).
Resolve the 65 No assertions finding(s) in Test Quality — start with column_style.spec.ts (12), column-style-colors.spec.ts (6), frame-timing.spec.ts (5). — One of this dimension's main actionable groups (65 warning-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with utils.mjs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
19 outdated, 0 yanked direct Cargo dependencies. 61 of 67 direct crates were graded against crates.io (0 not published there, 6 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×19
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 385 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Resolve the 34 Hotspot finding(s) in Churn × Complexity Hotspots — start with viewer.rs (2), body.ts, series-build.ts. — One of this dimension's main actionable groups (34 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor4.9 / 10Weak✓ Tool-verified
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.
273 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is rust/perspective-viewer/src/rust/custom_elements/viewer.rs. Counted over 544 of the 574 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk 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.
43 deducted task-comment markers across 126823 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 42 TodoComment finding(s) in Explicit Debt — start with filter_column.rs (5), metadata.rs (3), window_editor.rs (3). — One of this dimension's main actionable groups (42 warning-level).
Resolve the 1 XxxComment finding(s) in Explicit Debt — start with __init__.py. — One of this dimension's main actionable groups (1 warning-level).
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.
2 of 2 documentation facets pass in full. 14 document(s) read across 14 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
3 of 17 build units (Cargo, npm) flagged as possibly oversized/incoherent. This repository's .cpp source was read by no build unit, so this covers part of the tree, not all of it.
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret 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.
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).
102 finding(s): 0 critical, 94 high, 4 medium, 4 low. 69 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 40 file(s) — `packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts` (line 176), `packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts` (line 124, line 125, line 141, …), `packages/viewer-charts/src/ts/charts/chart-base.ts` (line 384), `packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts` (line 133), `packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts` (line 80), … (+35 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 REDACTED finding(s) charged to Static Analysis (SAST) — the other 69 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (82 issue-level, 13 of them charged here).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 30 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27), REDACTED (3). — One of this dimension's main actionable groups (30 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 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.
10 of 544 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/viewer-charts/src/ts/webgl/shader-registry.ts. Counted over 544 of the 574 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 3 Change coupling finding(s) in Change Coupling — start with table_make_view.rs, viewer.rs, column_settings_sidebar.rs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with duckdb.ts. — One of this dimension's main actionable groups (1 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 1 platform declaration(s) and 29 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives2.2 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×3) — packages/viewer-charts/src/ts/plugin/plugin.ts:381, packages/viewer-charts/src/ts/plugin/plugin.ts:382, packages/viewer-charts/src/ts/plugin/plugin.ts:383
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels6.8 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — docs/src/components/sidebar.ts:54
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/cli/src/html/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <perspective-viewer id="view1">, so there is no content here to wrap — render the <main> from the component mounted into it. — packages/cli/src/html/index.html:2
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — packages/cli/src/html/index.html:4
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
The repo's own CSS styles .button with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — packages/viewer-datagrid/src/ts/custom_elements/toolbar.ts:46
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`perspective-viewer[theme="Solarized"], perspective-viewer [theme="Solarized"]` sets color: #586e75 on background-color: #eee8d5 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — rust/perspective-viewer/src/themes/solarized.css:22
`& > .rl-panel::part(tab)` sets color: #ff0000 on background-color: #ffffff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — rust/perspective-viewer/src/css/viewer.css:457
`:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×5) — rust/perspective-viewer/src/css/column-dropdown.css:16, rust/perspective-viewer/src/css/filter-dropdown.css:19, rust/perspective-viewer/src/css/function-dropdown.css:19, …
`:host #column_settings_sidebar .sidebar_header_contents .sidebar_header_title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/column-settings-panel.css:105
`:host #column-style-container input.parameter` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/column-style.css:204
`:host #column-style-container details.control-group > summary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/column-style.css:330
`:host #column-style-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/column-style.css:23
`:host #top_panel .column-invalid.pivot-column` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/empty-column.css:47
`:host #top_panel .rrow .input-sizer:focus-within textarea:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/filter-item.css:83
`.input-sizer input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/panel-tab.css:185
`:host .mirrored-textarea > .mirrored-textarea-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/ui/form/mirrored-textarea.css:56
`:host input[type="checkbox"].alternate` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/ui/dom/checkbox.css:21
`:host input[type="checkbox"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/ui/dom/checkbox.css:65
`:host select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/ui/dom/select.css:60
`:host input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/ui/containers/dropdown-menu.css:43
`:host #editor #textarea_editable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — rust/perspective-viewer/src/css/form/code-editor.css:117
`regular-table div[tabindex]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/viewer-datagrid/src/css/pro.css:21
`:host #main_panel_container regular-layout > .overlay` moves (`transition: top 0.1s ease-in-out,
left 0.1s ease-in-out,
width 0.1s ease-in-out,
height 0.1s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — rust/perspective-viewer/src/css/viewer.css:519
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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 read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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's code 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.
Do you agree with this assessment?
P2 · Observability5.8 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 7/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cli`, `rust/bundle`, `rust/lint`, `rust/metadata`, `rust/perspective-js`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
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 cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:30
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:39
What to do
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — 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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×5) — rust/perspective-js/src/ts/perspective.cdn.ts:20, rust/perspective-js/src/ts/perspective.cdn.ts:21, rust/perspective-js/src/ts/perspective.cdn.ts:23, …
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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 each language's code 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.
`fs.readFileSync` in `convert` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/js/index.js:35
`fs.writeFileSync` in `convert` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/cli/src/js/index.js:57, packages/cli/src/js/index.js:63
`fs.readFileSync` in `host` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/js/index.js:90
`execSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — rust/perspective-viewer/build.mjs:48, rust/perspective-viewer/build.mjs:159
`fs.mkdirSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/build.mjs:162
`fs.readdirSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/build.mjs:187
`fs.writeFileSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — rust/perspective-viewer/build.mjs:203, rust/perspective-viewer/build.mjs:215
`fs.existsSync` in `buildToolSchemas` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:406
`fs.existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:437
`fs.readFileSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — rust/perspective-viewer/tools.mjs:446, rust/perspective-viewer/tools.mjs:451
`fs.existsSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:450
`fs.mkdirSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:477
`fs.writeFileSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:478
`fs.mkdirSync` in `buildCustomElementsManifest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:1493
`fs.writeFileSync` in `buildCustomElementsManifest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — rust/perspective-viewer/tools.mjs:1494
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety8.6 / 10Strong✓ 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.
Do you agree with this assessment?
R10 · Code Duplication4.7 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
46 duplicated blocks under packages/viewer-charts/src/ts/charts/ have copies in at least two of the sibling directories candlestick, cartesian, common, heatmap, map, series (+2 more sibling(s) not listed) — 38 of them are reported below, and 8 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 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 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 46 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67
16 duplicated blocks under packages/viewer-charts/src/ts/ have copies in at least two of the sibling directories axis, charts, interaction, map, theme, utils (+2 more sibling(s) not listed) — 11 of them are reported below, and 5 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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. — packages/viewer-charts/src/ts/axis/categorical-axis.ts:591
6 of the duplicated blocks reported below have copies in at least two of the sibling directories anywidget, jupyterlab, react, viewer-charts, viewer-datagrid under packages/. That concentration is one structural fact, not 6 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 6 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. — packages/viewer-charts/src/ts/theme/gradient.ts:211
packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67 · packages/viewer-charts/src/ts/charts/series/series-build.ts:134 — the two spans are one implementation copied and then locally edited — 750 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67
packages/viewer-charts/src/ts/theme/gradient.ts:211 · REDACTED:265 — the two spans are one implementation copied and then locally edited — 879 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. — packages/viewer-charts/src/ts/theme/gradient.ts:211
packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:131 · packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-ohlc.ts:84 — the two spans are one implementation copied and then locally edited — 691 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. — packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:131
packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts:39 · packages/viewer-charts/src/ts/charts/treemap/treemap.ts:32 — the two spans are one implementation copied and then locally edited — 623 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. — packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts:39
packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:64 · packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.ts:94 — the two spans are one implementation copied and then locally edited — 620 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. — packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:64
packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:160 · packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:119 — the two spans are one implementation copied and then locally edited — 514 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. — packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:160
packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:243 · packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:293 — the two spans are one implementation copied and then locally edited — 451 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. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:243
packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts:39 · packages/viewer-charts/src/ts/charts/cartesian/glyphs/points.ts:35 — the two spans are one implementation copied and then locally edited — 373 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. — packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts:39
packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts:54 · packages/viewer-charts/src/ts/interaction/zoom-controller.ts:387 — the two spans are one implementation copied and then locally edited — 258 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. — packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts:54
packages/viewer-charts/src/ts/axis/bar-axis.ts:224 · packages/viewer-charts/src/ts/axis/bar-axis.ts:282 — 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. — packages/viewer-charts/src/ts/axis/bar-axis.ts:224
packages/viewer-charts/src/ts/charts/series/series-render.ts:638 · packages/viewer-charts/src/ts/charts/series/series-render.ts:987 — 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. — packages/viewer-charts/src/ts/charts/series/series-render.ts:638
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:480 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:435 — 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. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:480
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:36 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:37 — 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. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:36
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:368 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:294 — the 2 copies are spread across 2 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. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:368
packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts:188 · packages/viewer-charts/src/ts/charts/treemap/treemap-layout.ts:275 — the two spans are one implementation copied and then locally edited — 255 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. — packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts:188
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:540 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:496 — 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. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:540
packages/viewer-charts/src/ts/axis/numeric-axis.ts:85 · packages/viewer-charts/src/ts/axis/numeric-axis.ts:136 — 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. — packages/viewer-charts/src/ts/axis/numeric-axis.ts:85
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:104 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:127 — 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. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:104
packages/viewer-charts/src/ts/axis/categorical-axis.ts:591 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-y-axis.ts:191 — 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. — packages/viewer-charts/src/ts/axis/categorical-axis.ts:591
packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:549 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:589 — 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. — packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:549
packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:150 · packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:288 — 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. — packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:150
packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:259 · packages/viewer-charts/src/ts/charts/series/series-render.ts:1160 — 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:259
packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts:163 · packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts:325 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts:163
packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1059 · packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1086 — 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1059
rust/perspective-js/src/ts/perspective.node.ts:189 · rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:102 — 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. — rust/perspective-js/src/ts/perspective.node.ts:189
packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:73 · packages/viewer-charts/src/ts/charts/series/series-render.ts:361 — 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:73
packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:394 · packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:541 — 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:394
packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:18 · packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:66 — 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. — packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:18
packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:516 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:634 — 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. — packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:516
packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:169 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:659 — 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. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:169
packages/viewer-charts/src/ts/axis/bar-axis.ts:347 · packages/viewer-charts/src/ts/charts/series/series-render.ts:1099 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/viewer-charts/src/ts/axis/bar-axis.ts:347
packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:210 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:201 — 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. — packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:210
packages/viewer-charts/build.mjs:110 · packages/viewer-charts/build.mjs:151 — all 2 copies are in the same file, 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. — packages/viewer-charts/build.mjs:110
packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:775 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:798 — 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. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:775
packages/anywidget/build.mjs:55 · packages/jupyterlab/build.mjs:41 — 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. — packages/anywidget/build.mjs:55
packages/viewer-charts/src/ts/axis/legend.ts:262 · packages/viewer-charts/src/ts/axis/legend.ts:426 — 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. — packages/viewer-charts/src/ts/axis/legend.ts:262
packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:227 · packages/viewer-charts/src/ts/charts/series/series-interact.ts:644 — the two spans are one implementation copied and then locally edited — 117 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:227
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.
packages/anywidget/build.mjs:20 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead. — packages/anywidget/build.mjs:20
packages/jupyterlab/build.mjs:21 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead. — packages/jupyterlab/build.mjs:21
packages/viewer-charts/build.mjs:20 imports webpack-glsl-minify/build/minify.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-charts/build.mjs:20
packages/viewer-datagrid/build.mjs:17 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead. — packages/viewer-datagrid/build.mjs:17
packages/viewer-datagrid/src/ts/event_handlers/click/edit_click.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/event_handlers/click/edit_click.ts:13
packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:28 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:28
packages/viewer-datagrid/src/ts/style_handlers/table_cell/boolean.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/table_cell/boolean.ts:13
packages/viewer-datagrid/src/ts/style_handlers/table_cell/cell_flash.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/table_cell/cell_flash.ts:13
packages/viewer-datagrid/src/ts/style_handlers/table_cell/datetime.ts:12 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/table_cell/datetime.ts:12
packages/viewer-datagrid/src/ts/style_handlers/table_cell/row_header.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/table_cell/row_header.ts:13
packages/viewer-datagrid/src/ts/style_handlers/types.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/viewer-datagrid/src/ts/style_handlers/types.ts:13
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.
buildSeriesPipeline has cyclomatic complexity 164 and cognitive complexity 389; 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. — packages/viewer-charts/src/ts/charts/series/series-build.ts:420
processCartesianChunk has cyclomatic complexity 99 and cognitive complexity 186; 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:297
renderFacetedChromeOverlay has cyclomatic complexity 74 and cognitive complexity 115; 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970
applyBodyCellStyles has cyclomatic complexity 73 and cognitive complexity 109; 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. — packages/viewer-datagrid/src/ts/style_handlers/body.ts:132
buildCandlestickPipeline has cyclomatic complexity 68 and cognitive complexity 137; 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. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227
renderBarFrame has cyclomatic complexity 54 and cognitive complexity 71; 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. — packages/viewer-charts/src/ts/charts/series/series-render.ts:383
styleColumnHeaderRow has cyclomatic complexity 46 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 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. — packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:95
processTreeChunk has cyclomatic complexity 45 and cognitive complexity 78; 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. — packages/viewer-charts/src/ts/charts/common/tree-data.ts:287
(anonymous) has cyclomatic complexity 44 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/viewer-datagrid/src/ts/style_handlers/body.ts:163
dataListener has cyclomatic complexity 40 and cognitive complexity 59; 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. — packages/viewer-datagrid/src/ts/data_listener/index.ts:71
lastGroupBySplit has cyclomatic complexity 39 and cognitive complexity 69; 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. — packages/viewer-charts/src/ts/data/last-group-by-split.ts:59
renderFacetedFrame has cyclomatic complexity 36 and cognitive complexity 37; 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:554
hitTestAreas has cyclomatic complexity 34 and cognitive complexity 51; 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. — packages/viewer-charts/src/ts/charts/series/series-interact.ts:391
handleBarHover 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. — packages/viewer-charts/src/ts/charts/series/series-interact.ts:66
ensureCatExtents has cyclomatic complexity 29 and cognitive complexity 70; 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. — packages/viewer-charts/src/ts/charts/series/series-render.ts:2007
renderFacetedBarChromeOverlay has cyclomatic complexity 29 and cognitive complexity 45; 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. — packages/viewer-charts/src/ts/charts/series/series-render.ts:1259
buildHeatmapPipeline has cyclomatic complexity 28 and cognitive complexity 48; 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. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:104
parseCssGradient 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. — packages/viewer-charts/src/ts/theme/gradient.ts:37
cell_style_numeric has cyclomatic complexity 28 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/viewer-datagrid/src/ts/style_handlers/table_cell/numeric.ts:97
createModel has cyclomatic complexity 28 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/viewer-datagrid/src/ts/model/create.ts:210
resolveCategoryAxis has cyclomatic complexity 26 and cognitive complexity 43; 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. — packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:292
column_config_schema has cyclomatic complexity 26 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/plugin/plugin.ts:631
buildFacetGrid has cyclomatic complexity 26 and cognitive complexity 28; 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. — packages/viewer-charts/src/ts/layout/facet-grid.ts:218
renderFacetedHeatmapChromeOverlay has cyclomatic complexity 25 and cognitive complexity 37; 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. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:719
hitTest has cyclomatic complexity 24 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. — packages/viewer-charts/src/ts/interaction/legend-controller.ts:522
register has cyclomatic complexity 23 and cognitive complexity 44; 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. — rust/perspective-js/src/ts/wasm/registry.ts:241
handleCandlestickHover has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:53
uploadAndRender has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/series/series.ts:584
renderBarTooltipCanvas has cyclomatic complexity 23 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/series/series-render.ts:1685
renderSinglePlotFrame has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:401
renderCartesianFrame has cyclomatic complexity 22 and cognitive complexity 26; 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. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:135
(anonymous) has cyclomatic complexity 22 and cognitive complexity 26; 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. — packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:200
renderFacetedBarFrame has cyclomatic complexity 22 and cognitive complexity 24; 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. — packages/viewer-charts/src/ts/charts/series/series-render.ts:906
buildCustomElementsManifest has cyclomatic complexity 21 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. — rust/perspective-viewer/tools.mjs:1323
hitTest has cyclomatic complexity 21 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. — packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:40
rebuildBuffers has cyclomatic complexity 21 and cognitive complexity 39; 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. — packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:128
_handleRendererMsg has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/transport/renderer-transport.ts:733
cemMembers has cyclomatic complexity 20 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. — rust/perspective-viewer/tools.mjs:1041
uploadBarInstances has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/series/series-render.ts:129
renderScatterLabels has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1284
Do you agree with this assessment?
R3 · Large Files3.2 / 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.
packages/viewer-charts/src/ts/charts/series/series-render.ts has 1964 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/series/series-render.ts:1
packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts has 1349 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1
rust/perspective-viewer/tools.mjs has 1313 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-viewer/tools.mjs:1
packages/viewer-charts/src/ts/charts/series/series-build.ts has 1158 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/series/series-build.ts:1
packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts has 1124 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts:1
packages/viewer-charts/src/ts/charts/series/series.ts has 964 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/series/series.ts:1
packages/viewer-charts/src/ts/interaction/legend-controller.ts has 951 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/interaction/legend-controller.ts:1
packages/viewer-charts/src/ts/charts/chart-base.ts has 924 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/chart-base.ts:1
packages/viewer-charts/src/ts/plugin/plugin.ts has 917 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/plugin/plugin.ts:1
packages/viewer-charts/src/ts/transport/renderer-transport.ts has 873 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/transport/renderer-transport.ts:1
packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts has 818 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:1
packages/viewer-charts/src/ts/worker/renderer.worker.ts has 791 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/worker/renderer.worker.ts:1
packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:1
packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts has 759 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:1
packages/viewer-charts/src/ts/charts/series/series-interact.ts has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/series/series-interact.ts:1
packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts has 671 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:1
packages/viewer-charts/src/ts/axis/categorical-axis.ts has 661 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/axis/categorical-axis.ts:1
packages/viewer-charts/src/ts/charts/common/tree-data.ts has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/common/tree-data.ts:1
packages/viewer-datagrid/src/ts/types.ts has 580 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-datagrid/src/ts/types.ts:1
rust/perspective-js/src/ts/perspective.node.ts has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-js/src/ts/perspective.node.ts:1
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts has 556 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:1
packages/viewer-charts/src/ts/charts/chart.ts has 532 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/chart.ts:1
rust/perspective-js/src/ts/virtual_servers/duckdb.ts has 532 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-js/src/ts/virtual_servers/duckdb.ts:1
packages/viewer-charts/src/ts/theme/gradient.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/theme/gradient.ts:1
packages/viewer-charts/src/ts/axis/legend.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/axis/legend.ts:1
rust/perspective-js/src/ts/wasm/registry.ts has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-js/src/ts/wasm/registry.ts:1
packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:1
packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:1
packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts:1
packages/viewer-charts/src/ts/interaction/zoom-controller.ts has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/interaction/zoom-controller.ts:1
rust/perspective-js/src/ts/wasm/perspective-server.poly.ts has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:1
packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:1
REDACTED has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:1
packages/viewer-datagrid/src/ts/style_handlers/body.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-datagrid/src/ts/style_handlers/body.ts:1
packages/viewer-datagrid/src/ts/event_handlers/select_region.ts has 416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:1
packages/viewer-charts/src/ts/render/scheduler.ts has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/render/scheduler.ts:1
packages/viewer-charts/src/ts/plugin/charts.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/viewer-charts/src/ts/plugin/charts.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 Coverage1.2 / 10Critical✓ 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) — packages/viewer-charts/src/ts/charts/series/series-render.ts:1, rust/perspective-viewer/tools.mjs:1, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
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 package.json 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: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code3.8 / 10Weak✓ 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.
1 file(s) (~101 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
137 file(s) (~56183 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: rust/perspective-js/src/ts/perspective.browser.ts imports '../../dist/wasm/perspective-js.d.ts', 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. — rust/perspective-js
114 file(s) (~24909 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: rust/perspective-viewer/src/ts/column-format.ts imports '../../dist/ts-rs/CustomNumberFormatConfig.d.ts', 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. — rust/perspective-viewer
Unreachable from the 47 application, 5 tooling and 297 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series-interact.ts, packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/series/series-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-bars.ts, packages/viewer-charts/src/ts/charts/series/series-interact.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/series/series-build.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts, packages/viewer-charts/src/ts/charts/map/map.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (packages/viewer-charts/src/ts/axis/legend.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts, packages/viewer-charts/src/ts/charts/chart-base.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/interaction/legend-controller.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/viewer-charts/src/ts/charts/registry.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-bars.ts and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/series/series.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts, packages/viewer-charts/src/ts/charts/common/categorical-y-chart.ts, packages/viewer-charts/src/ts/charts/common/tree-chart.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/chart-base.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/plugin/plugin.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/plugin/plugin.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/transport/renderer-transport.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-charts/src/ts/transport/renderer-transport.ts, packages/viewer-charts/src/ts/worker/dispatch.ts, packages/viewer-charts/src/ts/worker/session-host.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/worker/renderer.worker.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts, packages/viewer-charts/src/ts/charts/treemap/treemap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 15 in-repo import(s) from 15 other file(s) do name it (packages/viewer-charts/src/ts/axis/bar-axis.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts and 12 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/axis/categorical-axis.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series-render.ts, packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/series/series-interact.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-charts/src/ts/charts/common/tree-interact.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-layout.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/common/tree-data.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (packages/viewer-charts/src/ts/interaction/host-sink-message.ts, packages/viewer-charts/src/ts/interaction/legend-controller.ts, packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/transport/protocol.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts, packages/viewer-charts/src/ts/charts/common/tree-chrome.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/axis/legend.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/common/tree-data.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 10 in-repo import(s) from 10 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts and 7 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-datagrid/src/ts/style_handlers/body.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/plugin/activate.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-datagrid/src/ts/event_handlers/select_region.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/chart-base.ts, packages/viewer-charts/src/ts/worker/renderer.worker.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/render/scheduler.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-datagrid/src/ts/custom_elements/datagrid.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/model/create.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-datagrid/src/ts/data_listener/index.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/jupyterlab/src/js/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/jupyterlab/src/js/renderer.js
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/map/map.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-charts/src/ts/map/tile-layer.ts
no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-datagrid/src/ts/model/index.ts, packages/viewer-datagrid/src/ts/plugin/activate.ts, packages/viewer-datagrid/src/ts/plugin/column_config_schema.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/viewer-datagrid/src/ts/model/create.ts
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.
Declared in rust/perspective-js/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in rust/perspective-viewer/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
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.
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.
The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. (×4) — rust/perspective-python/perspective/widget/__init__.py:236, rust/perspective-python/perspective/widget/__init__.py:300, rust/perspective-python/perspective/handlers/aiohttp.py:55, …
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`extract` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — rust/perspective-js/src/ts/wasm/decompress.ts:19
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
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.
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 log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`debug` at line 344 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/clickhouse.py:344
`error` at line 395 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/clickhouse.py:395
`debug` at line 398 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/clickhouse.py:398
`warning` at line 378 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/duckdb.py:378
`error` at line 402 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/duckdb.py:402
`debug` at line 405 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/duckdb.py:405
`debug` at line 197 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:197
`warning` at line 430 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/postgres.py:430
`error` at line 468 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/postgres.py:468
`debug` at line 471 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rust/perspective-python/perspective/virtual_servers/postgres.py:471
`warn!` at line 784 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer.rs:784
`error!` at line 1095 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/session.rs:1095
`debug!` at line 1624 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/session.rs:1624
`error!` at line 28 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/utils/spawn.rs:28
`warn!` at line 116 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/ui/portal.rs:116
`warn!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/ui/containers/scroll_panel_item.rs:88
`warn!` at line 97 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/restore_derived.rs:97
`warn!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/restore_derived.rs:104
`info!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/restore_panel.rs:233
`warn!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:83
`warn!` at line 165 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:165
`warn!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:228
`warn!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/tasks/table_lifecycle.rs:90
`debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/session/column_defaults_update.rs:56
`debug!` at line 74 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/session/column_defaults_update.rs:74
`warn!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/session/op_queue.rs:331
`error!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/config_defaults.rs:59
`warn!` at line 568 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/dispatch.rs:568
`warn!` at line 532 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/plugin_config.rs:532
`error!` at line 775 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/plugin_config.rs:775
`warn!` at line 813 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/plugin_config.rs:813
`error!` at line 1092 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/plugin_config.rs:1092
`warn!` at line 124 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/renderer/registry.rs:124
`warn!` at line 24 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/queries/hosted_tables.rs:24
`warn!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/exprtk/tokenize.rs:143
`debug!` at line 585 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/custom_elements/viewer.rs:585
`debug!` at line 1616 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1616
`error!` at line 408 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/config/column_config_schema.rs:408
`error!` at line 429 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/config/column_config_schema.rs:429
`warn!` at line 315 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:315
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.
14/15 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.
~6.3 `!` null assertions per 1k TypeScript source lines — 348 assertion(s) across the 54875 source line(s) of the 198 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: packages/viewer-datagrid/src/ts/event_handlers/select_region.ts (64), packages/viewer-charts/src/ts/charts/series/series-render.ts (28), packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts (26). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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 — 38 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 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 — 59 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.
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 Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 28% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines), python (3,803 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — minio Error pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied minio-init Error context canceled mdbook Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: mdbook Pulling minio-init Error pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied minio Error context canceled mdbook Error context canceled Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-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.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .cpp, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 15 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 42 value object(s); a Domain/Aggregates/ValueObjects layer; a Rust domain-layer crate (a .../domain/ clean-architecture layer); a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — X12 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 28% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines), python (3,803 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 28% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines), python (3,803 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — X19 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — X23 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — X24 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — X25 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 41% of this repository's production lines — typescript (49,007 lines), cpp (42,975 lines), c (16,439 lines), javascript (3,660 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 30% of this repository's production lines — rust (74,013 lines), cpp (42,975 lines), c (16,439 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
Import cycle (2 files) packages/viewer-charts/src/ts/charts/series/series-interact.ts:20— packages/viewer-charts/src/ts/charts/series/series-interact.ts → packages/viewer-charts/src/ts/charts/series/series-render.ts → packages/viewer-charts/src/ts/charts/series/series-interact.ts (one verified cycle inside a mutually-dependent group of 3 files)
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text docs/src/components/sidebar.ts:54— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<html> without a lang packages/cli/src/html/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
Viewport restricts zoom packages/cli/src/html/index.html:4— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×1
Clickable element isn't keyboard-operable packages/viewer-datagrid/src/ts/custom_elements/toolbar.ts:46— The repo's own CSS styles .button with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Skipped test: columns > overwrites a duplicate expression alias rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:217— Skipped — switched off by test.skip
Skipped test: columns > overwrites a duplicate expression rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:234— Skipped — switched off by test.skip
Skipped test: delete > flush after delete waits for view removal rust/perspective-viewer/test/js/viewer_api/delete.spec.ts:49— Skipped — switched off by test.skip
Skipped test: (unnamed test) rust/perspective-viewer/test/js/stability/leaks.spec.ts:30— Skipped — switched off by test.skip
Skipped test: a chart survivor is not re-rendered after an exact presize rust/perspective-viewer/test/js/multi_panel/close_presize.spec.ts:187— Skipped — switched off by test.skip
Skipped test: (unnamed test) rust/perspective-viewer/test/js/multi_panel/restore_workspace_throttled.spec.ts:86— Skipped — switched off by test.skip
Skipped test: old `aggregate` syntax is backwards compatible rust/perspective-js/test/js/aggregates.spec.js:128— Skipped — switched off by test.skip
Skipped test: Arrow (chunked format) constructor rust/perspective-js/test/js/constructors.spec.js:1222— Skipped — switched off by test.skip
Skipped test: Handles inconsistent rows with same width rust/perspective-js/test/js/constructors.spec.js:1394— Skipped — switched off by test.skip
Skipped test: Handles inconsistent rows rust/perspective-js/test/js/constructors.spec.js:1410— Skipped — switched off by test.skip
Skipped test: Upgrades integer columns with values beyond max/min_int to float old rust/perspective-js/test/js/constructors.spec.js:1468— Skipped — switched off by test.skip
Skipped test: Correctly parses an RFC 2822 formatted string rust/perspective-js/test/js/constructors.spec.js:2032— Skipped — switched off by test.skip
Skipped test: Correctly parses all m-d-y formatted strings rust/perspective-js/test/js/constructors.spec.js:2044— Skipped — switched off by test.skip
Skipped test: Correctly parses a 'dd mm yyyy' formatted string rust/perspective-js/test/js/constructors.spec.js:2064— Skipped — switched off by test.skip
Skipped test: OG - Should not apply partial updates on limit tables when index wraps rust/perspective-js/test/js/constructors.spec.js:2178— Skipped — switched off by test.skip
Skipped test: returns changed rows, unique rust/perspective-js/test/js/delta.spec.js:756— Skipped — switched off by test.skip
Skipped test: returns changed rows when updated data in group by multi, hidden sort rust/perspective-js/test/js/delta.spec.js:1123— Skipped — switched off by test.skip
Skipped test: x == 1 pivoted, rolling updates rust/perspective-js/test/js/filters.spec.js:260— Skipped — switched off by test.skip
Skipped test: x > null should be an invalid filter rust/perspective-js/test/js/filters.spec.js:945— Skipped — switched off by test.skip
Skipped test: returns only grand total with group_by rust/perspective-js/test/js/group_rollup_mode.spec.js:584— Skipped — switched off by test.skip
Skipped test: is actually using the correct runtime rust/perspective-js/test/js/internal.spec.js:23— Skipped — switched off by test.skip
Skipped test: Arrow schema types are mapped correctly rust/perspective-js/test/js/internal.spec.js:32— Skipped — switched off by test.skip
Skipped test: csv loading does not leak rust/perspective-js/test/js/leaks.spec.js:150— Skipped — switched off by test.skip
Skipped test: 0 sided regex does not leak rust/perspective-js/test/js/leaks.spec.js:197— Skipped — switched off by test.skip
Skipped test: 0 sided string does not leak rust/perspective-js/test/js/leaks.spec.js:223— Skipped — switched off by test.skip
No assertions: delete an unused window column from the editor rust/perspective-viewer/test/js/windows.spec.ts:223— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: drawer width is trap-doored across editor tab switches rust/perspective-viewer/test/js/windows.spec.ts:684— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: editor > highlights ${name} rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:93— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validation > disables save for unknown symbols rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:184— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validation > disables save for type-invalid expression rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:188— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validation > disables save for invalid column references rust/perspective-viewer/test/js/viewer_config/expressions.spec.ts:194— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: delete > blocks until the underlying view is removed rust/perspective-viewer/test/js/viewer_api/delete.spec.ts:31— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: dragged sidebar width is remembered across close/reopen rust/perspective-viewer/test/js/settings_panel/settings_chrome.spec.ts:155— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: a settings sidebar right-click targets the active panel rust/perspective-viewer/test/js/multi_panel/context_menu_viewer.spec.ts:81— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: load + immediate restore holds `columns` across ${VIEWER_COUNT} viewers (${plugin}) rust/perspective-viewer/test/js/multi_panel/load_restore_race.spec.ts:39— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: unawaited load + restore({theme}) holds the host theme attribute across ${VIEWER_COUNT} viewers rust/perspective-viewer/test/js/multi_panel/theme_mirror.spec.ts:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: tab activation re-derives the host theme from the newly-active panel rust/perspective-viewer/test/js/multi_panel/theme_mirror.spec.ts:93— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: setActivePanel retargets getActivePanel rust/perspective-viewer/test/js/multi_panel/workspace.spec.ts:249— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: a pointerdown in a panel's plugin body activates that panel rust/perspective-viewer/test/js/multi_panel/workspace.spec.ts:268— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Close removes the panel via the menu rust/perspective-viewer/test/js/multi_panel/workspace.spec.ts:545— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: delete is offered at zero consumers rust/perspective-viewer/test/js/derived/new_menu.spec.ts:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: it builds when the parent arrives rust/perspective-viewer/test/js/derived/pend.spec.ts:39— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Construct a table from an indexed view mirrors replace and clear rust/perspective-js/test/js/constructors.spec.js:728— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) rust/perspective-js/test/js/delete.spec.js:17— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) rust/perspective-js/test/js/delta.spec.js:66— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: creates no View rust/perspective-js/test/js/describe.spec.js:221— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) rust/perspective-js/test/js/ports.spec.js:32— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Delete a table with pending updates rust/perspective-js/test/js/updates.spec.js:3389— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) rust/perspective-js/test/js/expressions/deltas.spec.js:26— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: a join over a derived table updates with its source rust/perspective-js/test/js/derived/chain.spec.ts:128— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment rust/perspective-viewer/src/rust/session.rs:501— /// deleted. TODO Table should be an immutable constructor parameter to — 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 rust/perspective-viewer/src/rust/session.rs:1041— // TODO check filter op — 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 rust/perspective-viewer/src/rust/utils/datetime.rs:14— //! TODO These methods should use JavaSript `Intl`. — 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 rust/perspective-viewer/src/rust/session/metadata.rs:74— /// TODO the multiple `Option` types could probably be merged since they are — 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 rust/perspective-viewer/src/rust/session/metadata.rs:217— /// TODO should expressions be `Rc`? — 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 rust/perspective-viewer/src/rust/session/metadata.rs:385— // todo: handle multi args — 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 rust/perspective-viewer/src/rust/session/replace_expression_update.rs:106— // TODO expression editing can change type, which may invalidate filters — 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 rust/perspective-viewer/src/rust/renderer/activate.rs:44— // TODO(texodus): Place at the bottom of the stack so it is rendered — 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 rust/perspective-viewer/src/rust/queries/column_locator.rs:61— // TODO This hardcodes the set of types a plugin offers a pivot a format control — 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 rust/perspective-viewer/src/rust/queries/column_values.rs:25— /// TODO Does not work with expressions yet. — 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 rust/perspective-viewer/src/rust/exprtk/cursor.rs:73— /// TODO this is alot of type backage for what could just be `num_rows()`. — 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 rust/perspective-viewer/src/rust/components/code_editor.rs:284— /// TODO this should use a portal — 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 rust/perspective-viewer/src/rust/components/status_bar.rs:313— // TODO Memoizing these would reduce some vdom diffing later on — 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 rust/perspective-viewer/src/rust/components/status_indicator.rs:32— /// TODO(texodus): remove this — 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 rust/perspective-viewer/src/rust/components/window_editor.rs:201— // TODO I should not be — 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 rust/perspective-viewer/src/rust/components/window_editor.rs:238— // TODO I should not be — 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 rust/perspective-viewer/src/rust/components/window_editor.rs:253— // TODO I should not be — 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 rust/perspective-viewer/src/rust/components/viewer/panels.rs:231— // TODO(texodus): what the ****? — 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 rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:130— /// TODO Break this into "Active", "Hover" and "Empty"? — 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 rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:342— // TODO Can't special case these - need to make this part of the — 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 rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:132— // TODO This belongs in the Features API. — 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 rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:465— // TODO This belongs in the Features API. — 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 rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:294— // TODO This is dirty and it may not work in the future. — 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 rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:364— // TODO: Move this to the Features API. — 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 rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:395— // TODO This needs to be moved to Features API. Or ... we just do this — 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.
FunctionTooLong: series-build.buildSeriesPipeline packages/viewer-charts/src/ts/charts/series/series-build.ts:420— FunctionTooLong — buildSeriesPipeline runs 522 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 422 over it, 5.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.
FunctionTooLong: perspective-server.poly.default rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:46— FunctionTooLong — default runs 270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 170 over it, 2.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.
FunctionTooLong: cartesian-build.processCartesianChunk packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:297— FunctionTooLong — processCartesianChunk runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.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.
FunctionTooLong: body.applyBodyCellStyles packages/viewer-datagrid/src/ts/style_handlers/body.ts:132— FunctionTooLong — applyBodyCellStyles runs 258 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× 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: series-render.renderBarFrame packages/viewer-charts/src/ts/charts/series/series-render.ts:383— FunctionTooLong — renderBarFrame runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.50× 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: perspective_viewer::rust::components::column_settings_sidebar::style_tab::render_leaf rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:226— FunctionTooLong — perspective_viewer::rust::components::column_settings_sidebar::style_tab::render_leaf runs 234 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 134 over it, 2.34× 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: candlestick-build.buildCandlestickPipeline packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227— FunctionTooLong — buildCandlestickPipeline runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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: index.createDataListener packages/viewer-datagrid/src/ts/data_listener/index.ts:55— FunctionTooLong — createDataListener runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× 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: index.createDataListener.dataListener packages/viewer-datagrid/src/ts/data_listener/index.ts:71— FunctionTooLong — createDataListener.dataListener runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× 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: cartesian-render.renderFacetedChromeOverlay packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970— FunctionTooLong — renderFacetedChromeOverlay runs 198 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× 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: perspective_viewer::rust::components::settings_panel::SettingsPanel rust/perspective-viewer/src/rust/components/settings_panel.rs:149— FunctionTooLong — perspective_viewer::rust::components::settings_panel::SettingsPanel runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: perspective_viewer::rust::ui::form::palette_selector::palette_selector rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:109— FunctionTooLong — perspective_viewer::rust::ui::form::palette_selector::palette_selector runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: perspective_js::rust::typed_array::decode_and_call rust/perspective-js/src/rust/typed_array.rs:117— FunctionTooLong — perspective_js::rust::typed_array::decode_and_call runs 178 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: perspective_client::rust::virtual_server::data::coerce_column rust/perspective-client/src/rust/virtual_server/data.rs:424— FunctionTooLong — perspective_client::rust::virtual_server::data::coerce_column runs 173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: last-group-by-split.lastGroupBySplit packages/viewer-charts/src/ts/data/last-group-by-split.ts:59— FunctionTooLong — lastGroupBySplit runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:148— FunctionTooLong — perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector runs 158 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: perspective_viewer::rust::components::column_settings_sidebar::style_tab::font_field::FontField rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/font_field.rs:61— FunctionTooLong — perspective_viewer::rust::components::column_settings_sidebar::style_tab::font_field::FontField runs 155 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: tree-data.processTreeChunk packages/viewer-charts/src/ts/charts/common/tree-data.ts:287— FunctionTooLong — processTreeChunk runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:43— FunctionTooLong — perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: activate.activate packages/viewer-datagrid/src/ts/plugin/activate.ts:62— FunctionTooLong — activate runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: series-render.renderFacetedBarFrame packages/viewer-charts/src/ts/charts/series/series-render.ts:906— FunctionTooLong — renderFacetedBarFrame runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: perspective_viewer::rust::agent::tools::control_schema_entries rust/perspective-viewer/src/rust/agent/tools.rs:694— FunctionTooLong — perspective_viewer::rust::agent::tools::control_schema_entries runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: heatmap-build.buildHeatmapPipeline packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:104— FunctionTooLong — buildHeatmapPipeline runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: heatmap-render.renderFacetedHeatmapChromeOverlay packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:719— FunctionTooLong — renderFacetedHeatmapChromeOverlay 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.
FunctionTooLong: perspective_viewer::rust::components::debug_panel::debug_panel rust/perspective-viewer/src/rust/components/debug_panel.rs:62— FunctionTooLong — perspective_viewer::rust::components::debug_panel::debug_panel runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
+ 16 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/viewer-charts/src/ts/charts/series/series-render.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 rust/perspective-viewer/tools.mjs: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 packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.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 packages/viewer-charts/src/ts/charts/series/series-build.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 packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.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 packages/viewer-charts/src/ts/interaction/legend-controller.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 packages/viewer-charts/src/ts/charts/series/series.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 packages/viewer-charts/src/ts/charts/chart-base.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 packages/viewer-charts/src/ts/plugin/plugin.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 packages/viewer-charts/src/ts/transport/renderer-transport.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 packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.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 packages/viewer-charts/src/ts/worker/renderer.worker.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 packages/viewer-charts/src/ts/charts/treemap/treemap-render.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 packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.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 packages/viewer-charts/src/ts/axis/categorical-axis.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 packages/viewer-charts/src/ts/charts/series/series-interact.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 packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.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 packages/viewer-charts/src/ts/charts/common/tree-data.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 rust/perspective-js/src/ts/virtual_servers/clickhouse.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 rust/perspective-js/src/ts/virtual_servers/duckdb.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 packages/viewer-charts/src/ts/theme/gradient.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 packages/viewer-charts/src/ts/axis/legend.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 packages/viewer-charts/src/ts/charts/common/category-axis-resolver.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.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 packages/viewer-charts/src/ts/charts/cartesian/cartesian.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.
Hotspot: packages/viewer-datagrid/src/ts/style_handlers/body.ts packages/viewer-datagrid/src/ts/style_handlers/body.ts:132— packages/viewer-datagrid/src/ts/style_handlers/body.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 104 in body.applyBodyCellStyles at line 132. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-datagrid/src/ts/style_handlers/body.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/series/series-build.ts packages/viewer-charts/src/ts/charts/series/series-build.ts:420— packages/viewer-charts/src/ts/charts/series/series-build.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 154 in series-build.buildSeriesPipeline at line 420. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/series/series-build.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-client/src/rust/virtual_server/server.rs rust/perspective-client/src/rust/virtual_server/server.rs:223— rust/perspective-client/src/rust/virtual_server/server.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in VirtualServer::internal_handle_request at line 223. 4 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-client/src/rust/virtual_server/server.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970— packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in cartesian-render.renderFacetedChromeOverlay at line 970. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/series/series-render.ts packages/viewer-charts/src/ts/charts/series/series-render.ts:383— packages/viewer-charts/src/ts/charts/series/series-render.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in series-render.renderBarFrame at line 383. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/series/series-render.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:43— rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels at line 43. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:493— rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in ViewQueryContext::build_query_ordered at line 493. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/components/viewer.rs rust/perspective-viewer/src/rust/components/viewer.rs:232— rust/perspective-viewer/src/rust/components/viewer.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in PerspectiveViewer::update at line 232. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/components/viewer.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/custom_elements/viewer.rs rust/perspective-viewer/src/rust/custom_elements/viewer.rs:502— rust/perspective-viewer/src/rust/custom_elements/viewer.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in PerspectiveViewerElement::load at line 502. 5 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/custom_elements/viewer.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-datagrid/src/ts/data_listener/index.ts packages/viewer-datagrid/src/ts/data_listener/index.ts:71— packages/viewer-datagrid/src/ts/data_listener/index.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in index.createDataListener.dataListener at line 71. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-datagrid/src/ts/data_listener/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/plugin/plugin.ts packages/viewer-charts/src/ts/plugin/plugin.ts:631— packages/viewer-charts/src/ts/plugin/plugin.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in HTMLPerspectiveViewerWebGLPluginElement.column_config_schema at line 631. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/plugin/plugin.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:132— rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in ConfigSelector::update at line 132. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/agent/tools.rs rust/perspective-viewer/src/rust/agent/tools.rs:694— rust/perspective-viewer/src/rust/agent/tools.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in perspective_viewer::rust::agent::tools::control_schema_entries at line 694. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/agent/tools.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-datagrid/src/ts/model/create.ts packages/viewer-datagrid/src/ts/model/create.ts:210— packages/viewer-datagrid/src/ts/model/create.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in create.createModel at line 210. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-datagrid/src/ts/model/create.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/session.rs rust/perspective-viewer/src/rust/session.rs:1246— rust/perspective-viewer/src/rust/session.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Session::prepare_view at line 1246. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/session.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-datagrid/src/ts/style_handlers/column_header.ts packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:95— packages/viewer-datagrid/src/ts/style_handlers/column_header.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in column_header.styleColumnHeaderRow at line 95. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-datagrid/src/ts/style_handlers/column_header.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227— packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in candlestick-build.buildCandlestickPipeline at line 227. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-client/src/rust/client.rs rust/perspective-client/src/rust/client.rs:579— rust/perspective-client/src/rust/client.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Client::table at line 579. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-client/src/rust/client.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs:129— rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in MainPanel::reconcile at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-js/src/ts/wasm/registry.ts rust/perspective-js/src/ts/wasm/registry.ts:241— rust/perspective-js/src/ts/wasm/registry.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in registry.register at line 241. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-js/src/ts/wasm/registry.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/tasks/pipeline.rs rust/perspective-viewer/src/rust/tasks/pipeline.rs:244— rust/perspective-viewer/src/rust/tasks/pipeline.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in perspective_viewer::rust::tasks::pipeline::run_locked at line 244. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/tasks/pipeline.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/transport/renderer-transport.ts packages/viewer-charts/src/ts/transport/renderer-transport.ts:733— packages/viewer-charts/src/ts/transport/renderer-transport.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in RendererTransport._handleRendererMsg at line 733. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/transport/renderer-transport.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:292— packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in category-axis-resolver.resolveCategoryAxis at line 292. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/viewer-charts/src/ts/charts/series/series.ts packages/viewer-charts/src/ts/charts/series/series.ts:584— packages/viewer-charts/src/ts/charts/series/series.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SeriesChart.uploadAndRender at line 584. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- packages/viewer-charts/src/ts/charts/series/series.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/perspective-viewer/src/rust/components/status_bar.rs rust/perspective-viewer/src/rust/components/status_bar.rs:187— rust/perspective-viewer/src/rust/components/status_bar.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in StatusBar::update at line 187. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:55:12 -05:00' --until='2026-11-13 17:55:12 -05:00' --full-history --no-merges -- rust/perspective-viewer/src/rust/components/status_bar.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: series/series-render.ts packages/viewer-charts/src/ts/charts/series/series-render.ts— FileTooLong — 1404 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 904 over it, 2.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_elements/viewer.rs rust/perspective-viewer/src/rust/custom_elements/viewer.rs— FileTooLong — 1091 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: PerspectiveViewerElement (5 blocks, 172-2266). The bar is 500 significant lines; this is 591 over it, 2.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: rust/session.rs rust/perspective-viewer/src/rust/session.rs— FileTooLong — 1025 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: Session (3 blocks, 424-1730). The bar is 500 significant lines; this is 525 over it, 2.05× 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: agent/tools.rs rust/perspective-viewer/src/rust/agent/tools.rs— FileTooLong — 1023 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 523 over it, 2.05× 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: perspective-viewer/tools.mjs rust/perspective-viewer/tools.mjs— FileTooLong — 969 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 469 over it, 1.94× 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: cartesian/cartesian-render.ts packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts— FileTooLong — 961 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 461 over it, 1.92× 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: renderer/plugin_config.rs rust/perspective-viewer/src/rust/renderer/plugin_config.rs— FileTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 416 over it, 1.83× 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: generic_sql_model/table_make_view.rs rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs— FileTooLong — 842 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: ViewQueryContext (2 blocks, 373-1279). The bar is 500 significant lines; this is 342 over it, 1.68× 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: virtual_server/data.rs rust/perspective-client/src/rust/virtual_server/data.rs— FileTooLong — 824 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 324 over it, 1.65× 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: rust/virtual_server.rs rust/perspective-js/src/rust/virtual_server.rs— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 317 over it, 1.63× 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: glyphs/density.ts packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts— FileTooLong — 753 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: DensityGlyph (176-1058). The bar is 500 significant lines; this is 253 over it, 1.51× 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: series/series-build.ts packages/viewer-charts/src/ts/charts/series/series-build.ts— FileTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: buildSeriesPipeline (420-1273). The bar is 500 significant lines; this is 188 over it, 1.38× 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: components/window_editor.rs rust/perspective-viewer/src/rust/components/window_editor.rs— FileTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 130 over it, 1.26× 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: column_selector/config_selector.rs rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: ConfigSelector (2 blocks, 104-825). The bar is 500 significant lines; this is 124 over it, 1.25× 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: treemap/treemap-render.ts packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts— FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× 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: rust/workspace.rs rust/perspective-viewer/src/rust/workspace.rs— FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: Workspace (3 blocks, 310-1196). The bar is 500 significant lines; this is 120 over it, 1.24× 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: heatmap/heatmap-render.ts packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts— FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 113 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: client/client_async.rs rust/perspective-python/src/client/client_async.rs— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 106 over it, 1.21× 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: interaction/legend-controller.ts packages/viewer-charts/src/ts/interaction/legend-controller.ts— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: LegendController (355-1080). The bar is 500 significant lines; this is 71 over it, 1.14× 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: server/virtual_server_sync.rs rust/perspective-python/src/server/virtual_server_sync.rs— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: PyServerHandler (2 blocks, 48-501). The bar is 500 significant lines; this is 69 over it, 1.14× 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: plugin/plugin.ts packages/viewer-charts/src/ts/plugin/plugin.ts— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), about 69% of them inside a single declaration: HTMLPerspectiveViewerWebGLPluginElement (296-1007). The bar is 500 significant lines; this is 58 over it, 1.12× 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: sunburst/sunburst-render.ts packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts— FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 57 over it, 1.11× 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: REDACTED REDACTED— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 55 over it, 1.11× 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: axis/categorical-axis.ts packages/viewer-charts/src/ts/axis/categorical-axis.ts— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× 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: rust/client.rs rust/perspective-client/src/rust/client.rs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 33 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.
+ 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×23
perspective_viewer::rust::agent::markdown::inline::scan (cognitive 81) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:60— perspective_viewer::rust::agent::markdown::inline::scan has cognitive complexity 81 (threshold 15). Drivers by points: if/else 22 (57 pts), match/switch 5 (14 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 48). 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.
perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels (cognitive 69) rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:43— perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels has cognitive complexity 69 (threshold 15). Drivers by points: if/else 23 (43 pts), loops 5 (11 pts), match/switch 8 (11 pts), boolean chains 4 (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.
perspective_viewer::rust::agent::markdown::inline::resolve (cognitive 42) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:378— perspective_viewer::rust::agent::markdown::inline::resolve has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 6, match/switch 2 (6 pts), loops 2 (4 pts) (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.
perspective_viewer::rust::ui::form::palette_selector::palette_selector (cognitive 31) rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:109— perspective_viewer::rust::ui::form::palette_selector::palette_selector has cognitive complexity 31 (threshold 15). Drivers by points: if/else 26 (29 pts), boolean chains 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.
perspective_viewer::rust::agent::tools::control_schema_entries (cognitive 27) rust/perspective-viewer/src/rust/agent/tools.rs:694— perspective_viewer::rust::agent::tools::control_schema_entries has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective_viewer::rust::tasks::pipeline::run_locked (cognitive 26) rust/perspective-viewer/src/rust/tasks/pipeline.rs:244— perspective_viewer::rust::tasks::pipeline::run_locked has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 4 (6 pts), boolean chains 3 (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.
perspective_viewer::rust::agent::markdown::inline::parse_link (cognitive 24) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:243— perspective_viewer::rust::agent::markdown::inline::parse_link has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 6 (8 pts), match/switch 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.
perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector (cognitive 24) rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:148— perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector has cognitive complexity 24 (threshold 15). Drivers by points: if/else 21, boolean chains 3. 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.
perspective_viewer::rust::renderer::state::project_bucket (cognitive 23) rust/perspective-viewer/src/rust/renderer/state.rs:165— perspective_viewer::rust::renderer::state::project_bucket has cognitive complexity 23 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (7 pts), match/switch 2 (6 pts) (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.
perspective_viewer::rust::renderer::plugin_config::materialize_overrides (cognitive 21) rust/perspective-viewer/src/rust/renderer/plugin_config.rs:1216— perspective_viewer::rust::renderer::plugin_config::materialize_overrides has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), loops 1 (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.
perspective_viewer::rust::renderer::plugin_config::normalize_values (cognitive 21) rust/perspective-viewer/src/rust/renderer/plugin_config.rs:1283— perspective_viewer::rust::renderer::plugin_config::normalize_values has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (6 pts), boolean chains 2, loops 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.
perspective_viewer::rust::agent::client::turn::run_turn (cognitive 17) rust/perspective-viewer/src/rust/agent/client/turn.rs:69— perspective_viewer::rust::agent::client::turn::run_turn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 2 (6 pts), loops 2 (3 pts), boolean chains 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.
perspective_viewer::rust::session::op_queue::overwrites (cognitive 17) rust/perspective-viewer/src/rust/session/op_queue.rs:363— perspective_viewer::rust::session::op_queue::overwrites has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. 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, 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.
perspective_viewer::rust::tasks::derive::resolve_table_ref (cognitive 17) rust/perspective-viewer/src/rust/tasks/derive.rs:43— perspective_viewer::rust::tasks::derive::resolve_table_ref has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (4 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.
perspective_viewer::rust::tasks::restore_derived::apply_derived_tables (cognitive 17) rust/perspective-viewer/src/rust/tasks/restore_derived.rs:29— perspective_viewer::rust::tasks::restore_derived::apply_derived_tables has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2, boolean chains 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.
perspective_viewer::rust::agent::docs::normalize (cognitive 16) rust/perspective-viewer/src/rust/agent/docs.rs:131— perspective_viewer::rust::agent::docs::normalize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 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.
perspective_viewer::rust::agent::markdown::block::strip_item_paragraphs (cognitive 16) rust/perspective-viewer/src/rust/agent/markdown/block.rs:292— perspective_viewer::rust::agent::markdown::block::strip_item_paragraphs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 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.
perspective_viewer::rust::agent::tools::spliced_config (cognitive 16) rust/perspective-viewer/src/rust/agent/tools.rs:126— perspective_viewer::rust::agent::tools::spliced_config has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective_viewer::rust::config::column_config_schema::resolve_layers (cognitive 16) rust/perspective-viewer/src/rust/config/column_config_schema.rs:569— perspective_viewer::rust::config::column_config_schema::resolve_layers has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (11 pts), loops 2 (3 pts), if/else 2 (nesting depth added 9). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective_viewer::rust::renderer::config_defaults::merge_object (cognitive 16) rust/perspective-viewer/src/rust/renderer/config_defaults.rs:326— perspective_viewer::rust::renderer::config_defaults::merge_object has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 2 (6 pts), loops 1 (nesting depth added 10). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MethodTooLong: VirtualServer.internal_handle_request rust/perspective-client/src/rust/virtual_server/server.rs:223— MethodTooLong — internal_handle_request runs 362 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 262 over it, 3.62× 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: ConfigSelector.update rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:132— MethodTooLong — update runs 287 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 187 over it, 2.87× 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: ColumnSelector.view rust/perspective-viewer/src/rust/components/column_selector.rs:316— MethodTooLong — view runs 247 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 147 over it, 2.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.
MethodTooLong: MainPanel.render rust/perspective-viewer/src/rust/components/main_panel/render.rs:39— MethodTooLong — render runs 229 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: WindowEditor.view rust/perspective-viewer/src/rust/components/window_editor.rs:717— MethodTooLong — view runs 211 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× 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: ConfigSelector.view rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:572— MethodTooLong — view runs 204 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× 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: StatusBar.view rust/perspective-viewer/src/rust/components/status_bar.rs:294— MethodTooLong — view runs 201 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× 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: PerspectiveViewer.render rust/perspective-viewer/src/rust/components/viewer/render.rs:36— MethodTooLong — render runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: ViewQueryContext.build_query_ordered rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:493— MethodTooLong — build_query_ordered runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: DragDropList.view rust/perspective-viewer/src/rust/components/dragdrop_list.rs:190— MethodTooLong — view runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: ActiveColumn.view rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:213— MethodTooLong — view runs 162 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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: SeriesChart.uploadAndRender packages/viewer-charts/src/ts/charts/series/series.ts:584— MethodTooLong — uploadAndRender 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: FilterColumn.view rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:208— MethodTooLong — view runs 139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: PerspectiveViewerElement.load rust/perspective-viewer/src/rust/custom_elements/viewer.rs:502— MethodTooLong — load runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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: ColumnSettingsPanel.view rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:388— MethodTooLong — view runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: VirtualDataSlice.render_to_rows rust/perspective-client/src/rust/virtual_server/data.rs:856— MethodTooLong — render_to_rows runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: VirtualDataSlice.render_to_columns_json rust/perspective-client/src/rust/virtual_server/data.rs:1042— MethodTooLong — render_to_columns_json runs 123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: ColumnSettingsPanel.update rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:238— MethodTooLong — update runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: HeatmapChart.uploadAndRender packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts:200— MethodTooLong — uploadAndRender 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.
MethodTooLong: CustomNumberFormat.update rust/perspective-viewer/src/rust/components/style_controls/number_string_format.rs:84— MethodTooLong — update runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×19
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/column-dropdown.css:16— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/column-settings-panel.css:105— `:host #column_settings_sidebar .sidebar_header_contents .sidebar_header_title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/column-style.css:204— `:host #column-style-container input.parameter` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/column-style.css:330— `:host #column-style-container details.control-group > summary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/column-style.css:23— `:host #column-style-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/empty-column.css:47— `:host #top_panel .column-invalid.pivot-column` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/filter-dropdown.css:19— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/filter-item.css:83— `:host #top_panel .rrow .input-sizer:focus-within textarea:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/function-dropdown.css:19— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/panel-tab.css:185— `.input-sizer input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/form/mirrored-textarea.css:56— `:host .mirrored-textarea > .mirrored-textarea-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/dom/checkbox.css:21— `:host input[type="checkbox"].alternate` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/dom/checkbox.css:65— `:host input[type="checkbox"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/dom/select.css:60— `:host select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/containers/context-menu.css:28— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/containers/dropdown-menu.css:43— `:host input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/ui/containers/dropdown-menu.css:22— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement rust/perspective-viewer/src/css/form/code-editor.css:117— `:host #editor #textarea_editable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/viewer-datagrid/src/css/pro.css:21— `regular-table div[tabindex]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Sync-over-async blocking packages/cli/src/js/index.js:35— `fs.readFileSync` in `convert` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/js/index.js:57— `fs.writeFileSync` in `convert` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/js/index.js:63— `fs.writeFileSync` in `convert` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/js/index.js:90— `fs.readFileSync` in `host` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:48— `execSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:159— `execSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:162— `fs.mkdirSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:187— `fs.readdirSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:203— `fs.writeFileSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/build.mjs:215— `fs.writeFileSync` in `build_all` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:406— `fs.existsSync` in `buildToolSchemas` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:437— `fs.existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:446— `fs.readFileSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:450— `fs.existsSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:451— `fs.readFileSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:477— `fs.mkdirSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:478— `fs.writeFileSync` in `buildDocsCorpus` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:1493— `fs.mkdirSync` in `buildCustomElementsManifest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking rust/perspective-viewer/tools.mjs:1494— `fs.writeFileSync` in `buildCustomElementsManifest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplicated block (8 lines × 2) rust/perspective-python/src/server/virtual_server_sync.rs:144— rust/perspective-python/src/server/virtual_server_sync.rs:144-151 | rust/perspective-python/src/server/virtual_server_sync.rs:276-283 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/server/virtual_server_sync.rs:144` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs:139— rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs:139-146 | rust/perspective-viewer/src/rust/components/column_selector/sort_column.rs:82-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:91— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:91-98 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:134-141 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&EnumFieldProps` in one and `&BoolFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/components/export_dropdown.rs:98— rust/perspective-viewer/src/rust/components/export_dropdown.rs:98-105 | rust/perspective-viewer/src/rust/components/export_dropdown.rs:109-116 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/export_dropdown.rs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/components/rows_counter.rs:52— rust/perspective-viewer/src/rust/components/rows_counter.rs:52-60 | rust/perspective-viewer/src/rust/components/rows_counter.rs:97-104 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/rows_counter.rs:52` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2075— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2075-2082 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2097-2104 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2075` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:136— rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:136-143 | rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:159-166 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-client/src/rust/virtual_server/data.rs:592— rust/perspective-client/src/rust/virtual_server/data.rs:592-599 | rust/perspective-client/src/rust/virtual_server/data.rs:604-611 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:592` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/symbol.rs:97— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/symbol.rs:97-104 | rust/perspective-viewer/src/rust/components/style_controls/number_string_format.rs:217-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/symbol.rs:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-migrate/src/plugins/charts.rs:142— rust/perspective-migrate/src/plugins/charts.rs:142-149 | rust/perspective-migrate/src/workspace/mod.rs:105-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-migrate/src/plugins/charts.rs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust/perspective-python/src/server/virtual_server_sync.rs:156— rust/perspective-python/src/server/virtual_server_sync.rs:156-163 | rust/perspective-python/src/server/virtual_server_sync.rs:288-295 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/server/virtual_server_sync.rs:156` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Boundary violation [package:relative-cross-package] packages/anywidget/build.mjs:20— packages/anywidget/build.mjs:20 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/jupyterlab/build.mjs:21— packages/jupyterlab/build.mjs:21 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/viewer-charts/build.mjs:20— packages/viewer-charts/build.mjs:20 imports webpack-glsl-minify/build/minify.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:relative-cross-package] packages/viewer-datagrid/build.mjs:17— packages/viewer-datagrid/build.mjs:17 reaches into another package with a relative path (../../rust/perspective-viewer/tools.mjs) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/event_handlers/click/edit_click.ts:13— packages/viewer-datagrid/src/ts/event_handlers/click/edit_click.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:28— packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:28 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/table_cell/boolean.ts:13— packages/viewer-datagrid/src/ts/style_handlers/table_cell/boolean.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/table_cell/cell_flash.ts:13— packages/viewer-datagrid/src/ts/style_handlers/table_cell/cell_flash.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/table_cell/datetime.ts:12— packages/viewer-datagrid/src/ts/style_handlers/table_cell/datetime.ts:12 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/table_cell/row_header.ts:13— packages/viewer-datagrid/src/ts/style_handlers/table_cell/row_header.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/viewer-datagrid/src/ts/style_handlers/types.ts:13— packages/viewer-datagrid/src/ts/style_handlers/types.ts:13 imports regular-table/dist/esm/types.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels (cyclomatic 42) rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:43— perspective_viewer::rust::tasks::sync_update_panels::sync_update_panels has cyclomatic complexity 42 (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.
perspective_viewer::rust::agent::markdown::inline::scan (cyclomatic 35) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:60— perspective_viewer::rust::agent::markdown::inline::scan has cyclomatic complexity 35 (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.
perspective_viewer::rust::ui::form::palette_selector::palette_selector (cyclomatic 29) rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:109— perspective_viewer::rust::ui::form::palette_selector::palette_selector has cyclomatic complexity 29 (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.
perspective_viewer::rust::agent::tools::control_schema_entries (cyclomatic 26) rust/perspective-viewer/src/rust/agent/tools.rs:694— perspective_viewer::rust::agent::tools::control_schema_entries has cyclomatic complexity 26 (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.
perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector (cyclomatic 25) rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:148— perspective_viewer::rust::ui::form::multi_stop_gradient_selector::multi_stop_gradient_selector 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.
perspective_viewer::rust::agent::markdown::inline::parse_link (cyclomatic 23) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:243— perspective_viewer::rust::agent::markdown::inline::parse_link has cyclomatic complexity 23 (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.
perspective_viewer::rust::tasks::pipeline::run_locked (cyclomatic 20) rust/perspective-viewer/src/rust/tasks/pipeline.rs:244— perspective_viewer::rust::tasks::pipeline::run_locked 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.
perspective_viewer::rust::agent::markdown::inline::resolve (cyclomatic 18) rust/perspective-viewer/src/rust/agent/markdown/inline.rs:378— perspective_viewer::rust::agent::markdown::inline::resolve 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.
perspective_viewer::rust::session::op_queue::overwrites (cyclomatic 18) rust/perspective-viewer/src/rust/session/op_queue.rs:363— perspective_viewer::rust::session::op_queue::overwrites has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
perspective_viewer::rust::components::status_indicator::StatusIndicator (cyclomatic 17) rust/perspective-viewer/src/rust/components/status_indicator.rs:42— perspective_viewer::rust::components::status_indicator::StatusIndicator has cyclomatic complexity 17 (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.
ClassTooLong: PerspectiveViewerElement rust/perspective-viewer/src/rust/custom_elements/viewer.rs:172— ClassTooLong — 983 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 5 blocks, lines 172-2266. The bar is 400 significant lines; this is 583 over it, 2.46× 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.
ClassTooLong: Session rust/perspective-viewer/src/rust/session.rs:420— ClassTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 72 methods, 3 blocks, lines 424-1730. The bar is 400 significant lines; this is 354 over it, 1.89× 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.
ClassTooLong: ViewQueryContext rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:373— ClassTooLong — 625 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 373-1279. The bar is 400 significant lines; this is 225 over it, 1.56× 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.
ClassTooLong: DensityGlyph packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts:176— ClassTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 172 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.
ClassTooLong: ConfigSelector rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:104— ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods, 2 blocks, lines 104-825. The bar is 400 significant lines; this is 111 over it, 1.28× 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.
ClassTooLong: JsServerHandler rust/perspective-js/src/rust/virtual_server.rs:234— ClassTooLong — 464 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 2 blocks, lines 236-852. The bar is 400 significant lines; this is 64 over it, 1.16× 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.
ClassTooLong: VirtualServer rust/perspective-client/src/rust/virtual_server/server.rs:60— ClassTooLong — 463 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 2 blocks, lines 60-717. The bar is 400 significant lines; this is 63 over it, 1.16× 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.
ClassTooLong: RendererTransport packages/viewer-charts/src/ts/transport/renderer-transport.ts:117— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 43 over it, 1.11× 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.
ClassTooLong: LegendController packages/viewer-charts/src/ts/interaction/legend-controller.ts:355— ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 34 over it, 1.09× 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.
ClassTooLong: Workspace rust/perspective-viewer/src/rust/workspace.rs:310— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 74 methods, 3 blocks, lines 310-1196. The bar is 400 significant lines; this is 32 over it, 1.08× 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: Renderer rust/perspective-viewer/src/rust/renderer.rs:231— TooManyMethods — 112 methods, declared across 3 files: rust/renderer.rs (49), renderer/dispatch.rs (32), renderer/plugin_config.rs (31). The bar is 30 methods; this is 82 over it, 3.73× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: Workspace rust/perspective-viewer/src/rust/workspace.rs:310— TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× 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: PerspectiveViewerElement rust/perspective-viewer/src/rust/custom_elements/viewer.rs:172— TooManyMethods — 73 methods, declared across 2 files: custom_elements/viewer.rs (49), agent/tools.rs (24). The bar is 30 methods; this is 43 over it, 2.43× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: Session rust/perspective-viewer/src/rust/session.rs:420— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× 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: Presentation rust/perspective-viewer/src/rust/presentation.rs:138— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: PerspectiveViewer rust/perspective-viewer/src/rust/components/viewer.rs:72— TooManyMethods — 48 methods, declared across 5 files: viewer/settings.rs (21), viewer/panels.rs (12), viewer/snapshots.rs (10), viewer/filters.rs (4), +1 more file(s). The bar is 30 methods; this is 18 over it, 1.60× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: AbstractChart packages/viewer-charts/src/ts/charts/chart-base.ts:130— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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: RendererTransport packages/viewer-charts/src/ts/transport/renderer-transport.ts:117— 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: GenericSQLVirtualServerModel rust/perspective-client/src/rust/virtual_server/generic_sql_model.rs:213— 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.
perspective_migrate::plugins::datagrid::colors (cognitive 25) rust/perspective-migrate/src/plugins/datagrid.rs:240— perspective_migrate::plugins::datagrid::colors has cognitive complexity 25 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 3 (10 pts), loops 2 (3 pts), boolean chains 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.
perspective_migrate::view::v5_7_0::canonical_names (cognitive 25) rust/perspective-migrate/src/view/v5_7_0.rs:95— perspective_migrate::view::v5_7_0::canonical_names has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 1 (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.
perspective_migrate::column_style::date_format (cognitive 24) rust/perspective-migrate/src/column_style/mod.rs:57— perspective_migrate::column_style::date_format has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (10 pts) (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.
perspective_migrate::workspace::regular_layout::area (cognitive 23) rust/perspective-migrate/src/workspace/regular_layout.rs:144— perspective_migrate::workspace::regular_layout::area has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 3 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective_migrate::view::v3_0_0::v2_aliases (cognitive 20) rust/perspective-migrate/src/view/v3_0_0.rs:32— perspective_migrate::view::v3_0_0::v2_aliases has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (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.
perspective_migrate::workspace::regular_layout::regular_layout (cognitive 20) rust/perspective-migrate/src/workspace/regular_layout.rs:20— perspective_migrate::workspace::regular_layout::regular_layout has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 3 (4 pts), boolean chains 2, loops 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.
perspective_migrate::plugins::datagrid::mode_renames (cognitive 18) rust/perspective-migrate/src/plugins/datagrid.rs:297— perspective_migrate::plugins::datagrid::mode_renames has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts), match/switch 1 (2 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×7
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) rust/perspective-python/src/client/client_async.rs:163— rust/perspective-python/src/client/client_async.rs:163-173 | rust/perspective-python/src/client/client_async.rs:175-183 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-viewer/src/rust/presentation.rs:401— rust/perspective-viewer/src/rust/presentation.rs:401-409 | rust/perspective-viewer/src/rust/presentation.rs:521-531 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-client/src/rust/view.rs:451— rust/perspective-client/src/rust/view.rs:451-459 | rust/perspective-client/src/rust/view.rs:492-502 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-viewer/src/rust/agent/tools.rs:637— rust/perspective-viewer/src/rust/agent/tools.rs:637-647 | rust/perspective-viewer/src/rust/agent/docs.rs:240-248 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:202— rust/perspective-python/perspective/virtual_servers/clickhouse.py:202-210 | rust/perspective-python/perspective/virtual_servers/duckdb.py:234-242 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-viewer/src/rust/utils/browser/request_animation_frame.rs:40— rust/perspective-viewer/src/rust/utils/browser/request_animation_frame.rs:40-48 | rust/perspective-viewer/src/rust/utils/browser/request_animation_frame.rs:85-95 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) rust/perspective-python/src/server/server_async.rs:59— rust/perspective-python/src/server/server_async.rs:59-67 | rust/perspective-python/src/server/server_sync.rs:93-101 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) rust/perspective-migrate/src/plugins/charts.rs:142— rust/perspective-migrate/src/plugins/charts.rs:142-151 | rust/perspective-migrate/src/plugins/charts.rs:176-185 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) rust/perspective-viewer/src/rust/components/viewer/wiring.rs:132— rust/perspective-viewer/src/rust/components/viewer/wiring.rs:132-141 | rust/perspective-viewer/src/rust/components/viewer/wiring.rs:194-203 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/viewer/wiring.rs:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) rust/perspective-python/src/client/client_async.rs:354— rust/perspective-python/src/client/client_async.rs:354-363 | rust/perspective-python/src/client/client_async.rs:752-761 — 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 (10 lines × 2) rust/perspective-viewer/src/rust/components/column_dropdown.rs:140— rust/perspective-viewer/src/rust/components/column_dropdown.rs:140-149 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:84-93 — before extracting anything, compare `rust/perspective-viewer/src/rust/components/column_dropdown.rs` and `rust/perspective-viewer/src/rust/components/function_dropdown.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) rust/perspective-viewer/src/rust/components/column_dropdown.rs:151— rust/perspective-viewer/src/rust/components/column_dropdown.rs:151-160 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:95-104 — before extracting anything, compare `rust/perspective-viewer/src/rust/components/column_dropdown.rs` and `rust/perspective-viewer/src/rust/components/function_dropdown.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:663— rust/perspective-js/src/rust/virtual_server.rs:663-672 | rust/perspective-js/src/rust/virtual_server.rs:759-768 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:663` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:578— REDACTED:578-587 | REDACTED:635-644 — 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 (7 lines × 2) rust/perspective-viewer/src/rust/components/column_dropdown.rs:245— rust/perspective-viewer/src/rust/components/column_dropdown.rs:245-251 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:184-190 — before extracting anything, compare `rust/perspective-viewer/src/rust/components/column_dropdown.rs` and `rust/perspective-viewer/src/rust/components/function_dropdown.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_dropdown.rs:245` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&ColumnDropDownViewProps` in one and `&FunctionDropDownViewProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) rust/perspective-viewer/src/rust/session.rs:632— rust/perspective-viewer/src/rust/session.rs:632-640 | rust/perspective-viewer/src/rust/session.rs:1716-1722 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/session.rs:1716` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) rust/perspective-viewer/src/rust/tasks/copy_export.rs:77— rust/perspective-viewer/src/rust/tasks/copy_export.rs:77-83 | rust/perspective-viewer/src/rust/tasks/copy_export.rs:98-104 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/tasks/copy_export.rs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) rust/perspective-viewer/src/rust/components/panel_menu.rs:409— rust/perspective-viewer/src/rust/components/panel_menu.rs:409-415 | rust/perspective-viewer/src/rust/components/panel_menu.rs:447-453 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/panel_menu.rs:409` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) rust/perspective-js/src/rust/table.rs:247— rust/perspective-js/src/rust/table.rs:247-253 | rust/perspective-js/src/rust/view.rs:443-449 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) rust/perspective-js/src/rust/table.rs:236— rust/perspective-js/src/rust/table.rs:236-242 | rust/perspective-js/src/rust/view.rs:419-425 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `rust/perspective-js/src/rust/view.rs:435` calls `num_columns`, `Ok`, `dimensions` and `rust/perspective-js/src/rust/table.rs:247` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:916— rust/perspective-js/src/rust/virtual_server.rs:916-922 | rust/perspective-python/src/server/virtual_server_sync.rs:583-589 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:916` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:369— rust/perspective-js/src/rust/virtual_server.rs:369-374 | rust/perspective-js/src/rust/virtual_server.rs:394-399 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:369` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:597— rust/perspective-js/src/rust/virtual_server.rs:597-602 | rust/perspective-js/src/rust/virtual_server.rs:619-624 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:597` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-python/src/server/virtual_server_sync.rs:229— rust/perspective-python/src/server/virtual_server_sync.rs:229-234 | rust/perspective-python/src/server/virtual_server_sync.rs:408-413 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/server/virtual_server_sync.rs:229` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-viewer/src/rust/presentation.rs:724— rust/perspective-viewer/src/rust/presentation.rs:724-729 | rust/perspective-viewer/src/rust/presentation.rs:757-762 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/presentation.rs:724` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-viewer/src/rust/components/column_selector/empty_column.rs:83— rust/perspective-viewer/src/rust/components/column_selector/empty_column.rs:83-89 | rust/perspective-viewer/src/rust/components/empty_row.rs:101-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) rust/perspective-python/src/client/table_data.rs:52— rust/perspective-python/src/client/table_data.rs:52-57 | rust/perspective-python/src/client/update_data.rs:67-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/client/table_data.rs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:438— rust/perspective-js/src/rust/virtual_server.rs:438-443 | rust/perspective-js/src/rust/virtual_server.rs:572-577 — 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 (5 lines × 2) rust/perspective-js/src/rust/table.rs:367— rust/perspective-js/src/rust/table.rs:367-371 | rust/perspective-js/src/rust/table.rs:396-401 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) rust/perspective-js/src/rust/typed_array.rs:234— rust/perspective-js/src/rust/typed_array.rs:234-240 | rust/perspective-js/src/rust/typed_array.rs:246-250 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/typed_array.rs:234` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:479— rust/perspective-js/src/rust/virtual_server.rs:479-483 | rust/perspective-js/src/rust/virtual_server.rs:771-775 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:479` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:688— rust/perspective-js/src/rust/virtual_server.rs:688-692 | rust/perspective-js/src/rust/virtual_server.rs:771-775 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:688` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) rust/perspective-viewer/src/rust/components/panel_menu.rs:347— rust/perspective-viewer/src/rust/components/panel_menu.rs:347-351 | rust/perspective-viewer/src/rust/components/status_bar.rs:219-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/panel_menu.rs:347` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) rust/perspective-viewer/src/rust/custom_events.rs:385— rust/perspective-viewer/src/rust/custom_events.rs:385-389 | rust/perspective-viewer/src/rust/custom_events.rs:395-399 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) rust/perspective-python/src/client/client_async.rs:462— rust/perspective-python/src/client/client_async.rs:462-466 | rust/perspective-python/src/client/client_async.rs:1068-1072 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/client/client_async.rs:462` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×6
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×6
Edited copy of a member (7 corresponding lines) rust/perspective-viewer/src/rust/agent/tools.rs:1374— rust/perspective-viewer/src/rust/agent/tools.rs:1374-1383 | rust/perspective-viewer/src/rust/agent/tools.rs:1385-1391 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust/perspective-viewer/src/rust/utils/pubsub.rs:159— rust/perspective-viewer/src/rust/utils/pubsub.rs:159-166 | rust/perspective-viewer/src/rust/utils/pubsub.rs:174-180 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust/perspective-client/src/rust/table.rs:634— rust/perspective-client/src/rust/table.rs:634-640 | rust/perspective-client/src/rust/table.rs:678-684 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust/perspective-viewer/src/rust/agent/slot.rs:79— rust/perspective-viewer/src/rust/agent/slot.rs:79-85 | rust/perspective-viewer/src/rust/agent/slot.rs:219-229 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:808— rust/perspective-js/src/rust/virtual_server.rs:808-814 | rust/perspective-python/src/server/virtual_server_sync.rs:460-466 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust/perspective-client/src/rust/table.rs:499— rust/perspective-client/src/rust/table.rs:499-505 | rust/perspective-client/src/rust/view.rs:358-364 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) rust/perspective-client/src/rust/client.rs:767— rust/perspective-client/src/rust/client.rs:767-775 | rust/perspective-client/src/rust/client.rs:839-847 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/client.rs:767` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:356— rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:356-364 | rust/perspective-viewer/src/rust/components/column_selector/inactive_column.rs:151-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:356` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:135— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:135-143 | rust/perspective-viewer/src/rust/components/plugin_tab.rs:108-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&StyleTabProps` in one and `&PluginTabProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:322— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:322-331 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:446-454 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab.rs:322` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) rust/perspective-viewer/src/rust/components/main_panel/presize.rs:61— rust/perspective-viewer/src/rust/components/main_panel/presize.rs:61-69 | rust/perspective-viewer/src/rust/tasks/presize_panels.rs:373-381 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) rust/perspective-viewer/src/rust/components/rows_counter.rs:45— rust/perspective-viewer/src/rust/components/rows_counter.rs:45-53 | rust/perspective-viewer/src/rust/components/rows_counter.rs:73-81 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/rows_counter.rs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:915— rust/perspective-js/src/rust/virtual_server.rs:915-925 | rust/perspective-python/src/server/virtual_server_sync.rs:582-592 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) rust/perspective-js/src/rust/table.rs:366— rust/perspective-js/src/rust/table.rs:366-376 | rust/perspective-js/src/rust/table.rs:395-406 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) rust/perspective-python/src/client/client_async.rs:659— rust/perspective-python/src/client/client_async.rs:659-669 | rust/perspective-python/src/client/client_async.rs:1031-1041 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) rust/perspective-viewer/src/rust/custom_events.rs:35— rust/perspective-viewer/src/rust/custom_events.rs:35-45 | rust/perspective-viewer/src/rust/custom_events.rs:69-81 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) rust/perspective-client/src/rust/config/windows.rs:251— rust/perspective-client/src/rust/config/windows.rs:251-261 | rust/perspective-client/src/rust/config/windows.rs:265-275 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) rust/perspective-js/src/rust/view.rs:338— rust/perspective-js/src/rust/view.rs:338-354 | rust/perspective-js/src/rust/view.rs:393-402 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust/perspective-client/src/rust/utils/mod.rs:103— rust/perspective-client/src/rust/utils/mod.rs:103-113 | rust/perspective-client/src/rust/utils/mod.rs:117-126 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust/perspective-viewer/src/rust/renderer/config_defaults.rs:75— rust/perspective-viewer/src/rust/renderer/config_defaults.rs:75-84 | rust/perspective-viewer/src/rust/renderer/config_defaults.rs:93-103 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust/perspective-viewer/src/rust/components/column_settings_sidebar/attributes_tab.rs:25— rust/perspective-viewer/src/rust/components/column_settings_sidebar/attributes_tab.rs:25-34 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/window_tab.rs:25-34 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:487— rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:487-496 | rust/perspective-viewer/src/rust/components/column_selector/inactive_column.rs:236-245 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) rust/perspective-js/src/rust/table.rs:235— rust/perspective-js/src/rust/table.rs:235-242 | rust/perspective-js/src/rust/view.rs:418-425 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust/perspective-python/src/client/client_async.rs:1245— rust/perspective-python/src/client/client_async.rs:1245-1252 | rust/perspective-python/src/client/client_async.rs:1277-1284 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust/perspective-python/src/server/session_sync.rs:51— rust/perspective-python/src/server/session_sync.rs:51-62 | rust/perspective-python/src/server/session_async.rs:61-68 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust/perspective-viewer/src/rust/components/column_dropdown.rs:131— rust/perspective-viewer/src/rust/components/column_dropdown.rs:131-138 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:75-82 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust/perspective-python/src/server/server_sync.rs:118— rust/perspective-python/src/server/server_sync.rs:118-125 | rust/perspective-python/src/server/session_sync.rs:68-77 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×5
Edited copy of a member (6 corresponding lines) rust/perspective-python/src/client/client_async.rs:692— rust/perspective-python/src/client/client_async.rs:692-697 | rust/perspective-python/src/client/client_async.rs:716-721 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:213— rust/perspective-python/perspective/virtual_servers/clickhouse.py:213-218 | rust/perspective-python/perspective/virtual_servers/duckdb.py:245-252 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust/perspective-js/src/rust/generic_sql_model.rs:57— rust/perspective-js/src/rust/generic_sql_model.rs:57-62 | rust/perspective-python/src/server/generic_sql_model.rs:43-48 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust/perspective-migrate/src/json.rs:28— rust/perspective-migrate/src/json.rs:28-33 | rust/perspective-migrate/src/workspace/mod.rs:70-75 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust/perspective-viewer/src/rust/tasks/edit_expression.rs:28— rust/perspective-viewer/src/rust/tasks/edit_expression.rs:28-33 | rust/perspective-viewer/src/rust/tasks/edit_window.rs:24-29 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Low cohesion: Presentation (LCOM4 12) rust/perspective-viewer/src/rust/presentation.rs:138— Presentation's methods fall into 12 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 12 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: PerspectiveViewerElement (LCOM4 10) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:172— PerspectiveViewerElement's methods fall into 10 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 10 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: Session (LCOM4 9) rust/perspective-viewer/src/rust/session.rs:420— Session's methods fall into 9 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 9 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: SessionMetadata (LCOM4 8) rust/perspective-viewer/src/rust/session/metadata.rs:36— SessionMetadata's methods fall into 8 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 8 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: WasmLogger (LCOM4 5) rust/perspective-js/src/rust/utils/console_logger.rs:125— WasmLogger'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.
Outbound HTTP without resilience rust/perspective-js/src/ts/perspective.cdn.ts:20— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience rust/perspective-js/src/ts/perspective.cdn.ts:21— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience rust/perspective-js/src/ts/perspective.cdn.ts:23— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience rust/perspective-js/src/ts/perspective.cdn.ts:30— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience rust/perspective-js/src/ts/wasm/decompress.ts:24— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
MainPanel::reconcile (cognitive 26) rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs:129— MainPanel::reconcile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 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.
MainPanel::on_layout_updated (cognitive 23) rust/perspective-viewer/src/rust/components/main_panel/update.rs:49— MainPanel::on_layout_updated has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, 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.
MainPanel::on_before_resize (cognitive 17) rust/perspective-viewer/src/rust/components/main_panel/presize.rs:77— MainPanel::on_before_resize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 7, boolean chains 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.
MainPanel::create (cognitive 17) rust/perspective-viewer/src/rust/components/main_panel.rs:257— MainPanel::create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×4
Edited copy of a member (14 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:393— rust/perspective-js/src/rust/virtual_server.rs:393-406 | rust/perspective-js/src/rust/virtual_server.rs:539-565 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) rust/perspective-client/src/rust/client.rs:446— rust/perspective-client/src/rust/client.rs:446-459 | rust/perspective-client/src/rust/client.rs:465-478 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) rust/perspective-viewer/src/rust/tasks/edit_expression.rs:64— rust/perspective-viewer/src/rust/tasks/edit_expression.rs:64-78 | rust/perspective-viewer/src/rust/tasks/edit_window.rs:40-53 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) rust/perspective-viewer/src/rust/renderer.rs:371— rust/perspective-viewer/src/rust/renderer.rs:371-384 | rust/perspective-viewer/src/rust/session.rs:456-469 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) rust/perspective-client/src/rust/virtual_server/data.rs:449— rust/perspective-client/src/rust/virtual_server/data.rs:449-461 | rust/perspective-client/src/rust/virtual_server/data.rs:614-626 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:449` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172— rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172-184 | rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:197-209 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) rust/perspective-viewer/src/rust/session/panel_state.rs:291— rust/perspective-viewer/src/rust/session/panel_state.rs:291-303 | rust/perspective-viewer/src/rust/session/panel_state.rs:307-319 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) rust/perspective-js/src/rust/typed_array.rs:257— rust/perspective-js/src/rust/typed_array.rs:257-269 | rust/perspective-js/src/rust/typed_array.rs:282-294 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/typed_array.rs:257` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
AC1 · Text alternatives· <canvas> without a text alternative · ×3
<canvas> without a text alternative packages/viewer-charts/src/ts/plugin/plugin.ts:381— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative packages/viewer-charts/src/ts/plugin/plugin.ts:382— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative packages/viewer-charts/src/ts/plugin/plugin.ts:383— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
ViewQueryContext::order_by_clauses (cognitive 98) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1102— ViewQueryContext::order_by_clauses has cognitive complexity 98 (threshold 15). Drivers by points: if/else 27 (74 pts), loops 6 (17 pts), boolean chains 7 (nesting depth added 58). 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.
ViewQueryContext::build_query_ordered (cognitive 70) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:493— ViewQueryContext::build_query_ordered has cognitive complexity 70 (threshold 15). Drivers by points: if/else 31 (55 pts), loops 3 (7 pts), boolean chains 5, match/switch 2 (3 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.
ViewQueryContext::filter_clause_sql (cognitive 19) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:979— ViewQueryContext::filter_clause_sql has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 2 (3 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
VirtualDataSlice::render_to_columns_json (cognitive 43) rust/perspective-client/src/rust/virtual_server/data.rs:1042— VirtualDataSlice::render_to_columns_json has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (39 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (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.
VirtualDataSlice::from_arrow_ipc (cognitive 31) rust/perspective-client/src/rust/virtual_server/data.rs:673— VirtualDataSlice::from_arrow_ipc has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 4 (11 pts), match/switch 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.
VirtualDataSlice::render_to_rows (cognitive 26) rust/perspective-client/src/rust/virtual_server/data.rs:856— VirtualDataSlice::render_to_rows has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 6 (8 pts), boolean chains 4, loops 2 (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.
perspective_client::rust::virtual_server::generic_sql_model::table_make_view::parse_relation_path (cognitive 26) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:291— perspective_client::rust::virtual_server::generic_sql_model::table_make_view::parse_relation_path has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (7 pts), match/switch 2 (6 pts) (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.
perspective_client::rust::virtual_server::data::coerce_column (cognitive 22) rust/perspective-client/src/rust/virtual_server/data.rs:424— perspective_client::rust::virtual_server::data::coerce_column has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective_client::rust::virtual_server::data::cast_to_int64 (cognitive 19) rust/perspective-client/src/rust/virtual_server/data.rs:283— perspective_client::rust::virtual_server::data::cast_to_int64 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (6 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Renderer::all_columns_configs_materialized (cognitive 26) rust/perspective-viewer/src/rust/renderer/plugin_config.rs:575— Renderer::all_columns_configs_materialized has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 4 (6 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.
Renderer::run_presize (cognitive 17) rust/perspective-viewer/src/rust/renderer/dispatch.rs:292— Renderer::run_presize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (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.
Renderer::update_columns_config_field (cognitive 16) rust/perspective-viewer/src/rust/renderer/plugin_config.rs:755— Renderer::update_columns_config_field has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (7 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.
Change coupling: table_make_view.rs ↔ tests.rs rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1— `rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs` and `rust/perspective-client/src/rust/virtual_server/generic_sql_model/tests.rs` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 9 shared commits counted here, the most recent 3 are `f3b99359` Fix postgres derived tables; `1afdcf86` Support DuckDB 2.0; `353c53b6` Fix column value escape in `GenericSQLModel` header — run `git show` on any of them.
Change coupling: viewer.rs ↔ split_panel.rs rust/perspective-viewer/src/rust/components/viewer.rs:1— `rust/perspective-viewer/src/rust/components/viewer.rs` and `rust/perspective-viewer/src/rust/ui/containers/split_panel.rs` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 9 shared commits counted here, the most recent 3 are `e3aae543` Address new lints (at that commit the file was still `rust/perspective-viewer/src/rust/components/containers/split_panel.rs`); `2d3ac88e` Fix expression editor bugs (at that commit the file was still `rust/perspective-viewer/src/rust/components/containers/split_panel.rs`); `8e519ae7` Upgrade to yew 0.21.0 (at that commit the file was still `rust/perspective-viewer/src/rust/components/containers/split_panel.rs`) — run `git show` on any of them.
Change coupling: column_settings_sidebar.rs ↔ viewer.rs rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:1— `rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs` and `rust/perspective-viewer/src/rust/components/viewer.rs` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 12 shared commits counted here, the most recent 3 are `ed9a6458` UI cleanup; `e3aae543` Address new lints (at that commit the file was still `rust/perspective-viewer/src/rust/components/column_settings_sidebar/sidebar.rs`); `2d3ac88e` Fix expression editor bugs (at that commit the file was still `rust/perspective-viewer/src/rust/components/column_settings_sidebar/sidebar.rs`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:368— rust/perspective-js/src/rust/virtual_server.rs:368-391 | rust/perspective-js/src/rust/virtual_server.rs:494-537 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:408— rust/perspective-js/src/rust/virtual_server.rs:408-431 | rust/perspective-js/src/rust/virtual_server.rs:571-594 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) rust/perspective-python/src/server/generic_sql_model.rs:117— rust/perspective-python/src/server/generic_sql_model.rs:117-140 | rust/perspective-python/src/server/generic_sql_model.rs:156-180 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) rust/perspective-python/src/server/server_async.rs:40— rust/perspective-python/src/server/server_async.rs:40-57 | rust/perspective-python/src/server/server_sync.rs:47-68 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) rust/perspective-viewer/src/rust/ui/form/select_enum_field.rs:42— rust/perspective-viewer/src/rust/ui/form/select_enum_field.rs:42-59 | rust/perspective-viewer/src/rust/ui/form/select_value_field.rs:41-64 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs:168— rust/perspective-python/src/server/virtual_server_sync.rs:168-185 | rust/perspective-python/src/server/virtual_server_sync.rs:301-322 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×3
Edited copies of one member (3 members, 15+ corresponding lines) rust/perspective-js/src/rust/generic_sql_model.rs:141— rust/perspective-js/src/rust/generic_sql_model.rs:141-159 | rust/perspective-js/src/rust/generic_sql_model.rs:179-198 | rust/perspective-js/src/rust/generic_sql_model.rs:209-223 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) rust/perspective-client/src/rust/view.rs:506— rust/perspective-client/src/rust/view.rs:506-520 | rust/perspective-client/src/rust/view.rs:523-538 | rust/perspective-client/src/rust/view.rs:542-557 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) rust/perspective-python/bench/runtime/perspective_benchmark.py:110— rust/perspective-python/bench/runtime/perspective_benchmark.py:110-124 | rust/perspective-python/bench/runtime/perspective_benchmark.py:137-151 | rust/perspective-python/bench/runtime/perspective_benchmark.py:166-180 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) rust/perspective-client/src/rust/table.rs:694— rust/perspective-client/src/rust/table.rs:694-706 | rust/perspective-client/src/rust/view.rs:752-764 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust/perspective-js/src/rust/utils/local_poll_loop.rs:26— rust/perspective-js/src/rust/utils/local_poll_loop.rs:26-38 | rust/perspective-js/src/rust/utils/local_poll_loop.rs:44-56 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust/perspective-viewer/src/rust/tasks/copy_export.rs:76— rust/perspective-viewer/src/rust/tasks/copy_export.rs:76-88 | rust/perspective-viewer/src/rust/tasks/copy_export.rs:97-109 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) rust/perspective-python/perspective/handlers/aiohttp.py:47— rust/perspective-python/perspective/handlers/aiohttp.py:47-51 | rust/perspective-python/perspective/handlers/starlette.py:41-45 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:239— rust/perspective-python/perspective/virtual_servers/clickhouse.py:239-243 | rust/perspective-python/perspective/virtual_servers/duckdb.py:292-296 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) rust/perspective-python/perspective/virtual_servers/duckdb.py:299— rust/perspective-python/perspective/virtual_servers/duckdb.py:299-303 | rust/perspective-python/perspective/virtual_servers/postgres.py:321-326 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) rust/perspective-js/src/rust/generic_sql_model.rs:142— rust/perspective-js/src/rust/generic_sql_model.rs:142-152 | rust/perspective-js/src/rust/generic_sql_model.rs:180-190 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/generic_sql_model.rs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:166— rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:166-176 | rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:112-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:166` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:279— rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:279-289 | rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:132-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/ui/form/multi_stop_gradient_selector.rs:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2 locations) packages/viewer-charts/src/ts/axis/categorical-axis.ts:591— packages/viewer-charts/src/ts/axis/categorical-axis.ts:591 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-y-axis.ts:191 — 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 (27 lines × 2 locations) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:549— packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:549 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:589 — 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 (27 lines × 2 locations) packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:150— packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:150 · packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:288 — 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.
Duplicated block (26 lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:259— packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:259 · packages/viewer-charts/src/ts/charts/series/series-render.ts:1160 — 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 (26 lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts:163— packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts:163 · packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts:325 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (26 lines × 2 locations) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1059— packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1059 · packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1086 — 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 (25 lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:73— packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:73 · packages/viewer-charts/src/ts/charts/series/series-render.ts:361 — 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 (25 lines × 2 locations) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:394— packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:394 · packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:541 — 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.
Duplicated block (25 lines × 2 locations) packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:18— packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:18 · packages/viewer-datagrid/src/ts/event_handlers/header_click.ts:66 — 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.
ViewQueryContext::build_query_ordered (cyclomatic 37) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:493— ViewQueryContext::build_query_ordered has cyclomatic complexity 37 (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.
ViewQueryContext::order_by_clauses (cyclomatic 31) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1102— ViewQueryContext::order_by_clauses has cyclomatic complexity 31 (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.
VirtualDataSlice::render_to_rows (cyclomatic 34) rust/perspective-client/src/rust/virtual_server/data.rs:856— VirtualDataSlice::render_to_rows has cyclomatic complexity 34 (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.
VirtualDataSlice::render_to_columns_json (cyclomatic 24) rust/perspective-client/src/rust/virtual_server/data.rs:1042— VirtualDataSlice::render_to_columns_json 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.
perspective_client::rust::virtual_server::data::coerce_column (cyclomatic 30) rust/perspective-client/src/rust/virtual_server/data.rs:424— perspective_client::rust::virtual_server::data::coerce_column has cyclomatic complexity 30 (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.
perspective_client::rust::virtual_server::generic_sql_model::table_make_view::window_sql (cyclomatic 16) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:130— perspective_client::rust::virtual_server::generic_sql_model::table_make_view::window_sql has cyclomatic complexity 16 (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.
Session::prepare_view (cyclomatic 17) rust/perspective-viewer/src/rust/session.rs:1246— Session::prepare_view has cyclomatic complexity 17 (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.
Session::commit_view (cyclomatic 16) rust/perspective-viewer/src/rust/session.rs:1377— Session::commit_view 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.
Session::prepare_view (cognitive 19) rust/perspective-viewer/src/rust/session.rs:1246— Session::prepare_view has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 6 (7 pts), boolean chains 1 (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.
Session::commit_view (cognitive 18) rust/perspective-viewer/src/rust/session.rs:1377— Session::commit_view has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, match/switch 2 (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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:892— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:892-916 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:937-961 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:253— rust/perspective-js/src/rust/virtual_server.rs:253-277 | rust/perspective-js/src/rust/virtual_server.rs:437-467 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs:135— rust/perspective-viewer/src/rust/components/column_selector/aggregate_selector.rs:135-149 | rust/perspective-viewer/src/rust/components/column_selector/sort_column.rs:75-96 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) rust/perspective-viewer/src/rust/components/main_panel.rs:418— rust/perspective-viewer/src/rust/components/main_panel.rs:418-439 | rust/perspective-viewer/src/rust/components/main_panel.rs:445-459 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) rust/perspective-client/src/rust/view.rs:627— rust/perspective-client/src/rust/view.rs:627-648 | rust/perspective-client/src/rust/view.rs:709-727 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:384— rust/perspective-python/perspective/virtual_servers/clickhouse.py:384-406 | rust/perspective-python/perspective/virtual_servers/duckdb.py:391-409 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) rust/perspective-viewer/src/rust/presentation.rs:720— rust/perspective-viewer/src/rust/presentation.rs:720-735 | rust/perspective-viewer/src/rust/presentation.rs:753-770 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs:57— rust/perspective-python/src/server/virtual_server_sync.rs:57-72 | rust/perspective-python/src/server/virtual_server_sync.rs:228-246 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1956— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1956-1970 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2074-2087 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:2096-2109 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) rust/perspective-client/src/rust/client.rs:766— rust/perspective-client/src/rust/client.rs:766-779 | rust/perspective-client/src/rust/client.rs:838-853 | rust/perspective-client/src/rust/client.rs:888-902 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) rust/perspective-python/src/client/client_async.rs:123— rust/perspective-python/src/client/client_async.rs:123-134 | rust/perspective-python/src/client/client_sync.rs:30-41 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) rust/perspective-viewer/src/rust/tasks/edit_expression.rs:81— rust/perspective-viewer/src/rust/tasks/edit_expression.rs:81-92 | rust/perspective-viewer/src/rust/tasks/edit_window.rs:142-153 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (17 lines × 2) rust/perspective-viewer/src/rust/components/column_selector.rs:258— rust/perspective-viewer/src/rust/components/column_selector.rs:258-274 | rust/perspective-viewer/src/rust/components/column_selector.rs:291-307 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector.rs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:306— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:306-322 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:516-532 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:306` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&PaletteFieldProps` in one and `&ColorFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12–13 lines × 2) rust/perspective-client/src/rust/virtual_server/data.rs:1132— rust/perspective-client/src/rust/virtual_server/data.rs:1132-1143 | rust/perspective-client/src/rust/virtual_server/data.rs:1165-1177 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:1132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) rust/perspective-js/src/rust/virtual_server.rs:380— rust/perspective-js/src/rust/virtual_server.rs:380-391 | rust/perspective-js/src/rust/virtual_server.rs:525-537 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:380` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rust/perspective-viewer/src/rust/components/column_dropdown.rs:200— rust/perspective-viewer/src/rust/components/column_dropdown.rs:200-211 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:142-153 — before extracting anything, compare `rust/perspective-viewer/src/rust/components/column_dropdown.rs` and `rust/perspective-viewer/src/rust/components/function_dropdown.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_dropdown.rs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) REDACTED:481— REDACTED:481-492 | REDACTED:552-563 — 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 (11 lines × 3) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:316— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:316-326 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:429-439 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:526-536 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&PaletteFieldProps` in one and `&GradientStopsFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 3) REDACTED:514— REDACTED:514-524 | REDACTED:536-546 | REDACTED:673-683 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) rust/perspective-viewer/src/rust/tasks/send_column_config.rs:40— rust/perspective-viewer/src/rust/tasks/send_column_config.rs:40-49 | rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:33-42 | rust/perspective-viewer/src/rust/tasks/set_edit_mode.rs:38-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/tasks/send_column_config.rs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) rust/perspective-js/src/rust/virtual_server.rs:662— rust/perspective-js/src/rust/virtual_server.rs:662-671 | rust/perspective-js/src/rust/virtual_server.rs:709-718 | rust/perspective-js/src/rust/virtual_server.rs:758-767 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:662` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) rust/perspective-viewer/src/rust/renderer/plugin_config.rs:784— rust/perspective-viewer/src/rust/renderer/plugin_config.rs:784-792 | rust/perspective-viewer/src/rust/renderer/state.rs:184-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–10 lines × 2) rust/perspective-viewer/src/rust/ui/containers/dropdown_menu.rs:62— rust/perspective-viewer/src/rust/ui/containers/dropdown_menu.rs:62-71 | rust/perspective-viewer/src/rust/ui/containers/dropdown_menu.rs:79-87 — 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 (6 lines × 4) rust/perspective-client/src/rust/virtual_server/data.rs:468— rust/perspective-client/src/rust/virtual_server/data.rs:468-473 | rust/perspective-client/src/rust/virtual_server/data.rs:476-481 | rust/perspective-client/src/rust/virtual_server/data.rs:484-489 | rust/perspective-client/src/rust/virtual_server/data.rs:492-497 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:468` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) rust/perspective-client/src/rust/virtual_server/data.rs:501— rust/perspective-client/src/rust/virtual_server/data.rs:501-506 | rust/perspective-client/src/rust/virtual_server/data.rs:509-514 | rust/perspective-client/src/rust/virtual_server/data.rs:517-522 | rust/perspective-client/src/rust/virtual_server/data.rs:525-530 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:501` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `rust/perspective-client/src/rust/virtual_server/data.rs:500` calls `iter`, `collect` and `rust/perspective-client/src/rust/virtual_server/data.rs:508` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Off the main sequence: perspective-client — perspective-client: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: @perspective-dev/viewer-charts — @perspective-dev/viewer-charts: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Duplicated block (31 lines × 2 locations) packages/viewer-charts/src/ts/axis/numeric-axis.ts:85— packages/viewer-charts/src/ts/axis/numeric-axis.ts:85 · packages/viewer-charts/src/ts/axis/numeric-axis.ts:136 — 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.
Duplicated block (31 lines × 2 locations) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:104— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:104 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:127 — 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 (20 lines × 2 locations) packages/viewer-charts/build.mjs:110— packages/viewer-charts/build.mjs:110 · packages/viewer-charts/build.mjs:151 — all 2 copies are in the same file, 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.
Duplicated block (20 lines × 2 locations) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:775— packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:775 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:798 — 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.
Duplicated block (19 lines × 2 locations) packages/anywidget/build.mjs:55— packages/anywidget/build.mjs:55 · packages/jupyterlab/build.mjs:41 — 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 (19 lines × 2 locations) packages/viewer-charts/src/ts/axis/legend.ts:262— packages/viewer-charts/src/ts/axis/legend.ts:262 · packages/viewer-charts/src/ts/axis/legend.ts:426 — 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.
Dead file (~398 LoC) packages/viewer-datagrid/src/ts/custom_elements/datagrid.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~398 LoC) packages/viewer-datagrid/src/ts/data_listener/index.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/model/create.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency '@perspective-dev/metadata' — Declared in rust/perspective-js/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@perspective-dev/metadata' — Declared in rust/perspective-viewer/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X1 · Async correctness· Task from `asyncio.create_task` is not kept · ×2
Task from `asyncio.create_task` is not kept rust/perspective-python/perspective/widget/__init__.py:236— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
Task from `asyncio.create_task` is not kept rust/perspective-python/perspective/widget/__init__.py:300— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
X1 · Async correctness· Task from `self._loop.create_task` is not kept · ×2
Task from `self._loop.create_task` is not kept rust/perspective-python/perspective/handlers/aiohttp.py:55— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
Task from `self._loop.create_task` is not kept rust/perspective-python/perspective/handlers/starlette.py:49— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/cli/src/html/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <perspective-viewer id="view1">, so there is no content here to wrap — render the <main> from the component mounted into it.
Low contrast colour pair in CSS (4.4:1) rust/perspective-viewer/src/themes/solarized.css:22— `perspective-viewer[theme="Solarized"], perspective-viewer [theme="Solarized"]` sets color: #586e75 on background-color: #eee8d5 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) rust/perspective-viewer/src/css/viewer.css:457— `& > .rl-panel::part(tab)` sets color: #ff0000 on background-color: #ffffff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard rust/perspective-viewer/src/css/viewer.css:519— `:host #main_panel_container regular-layout > .overlay` moves (`transition: top 0.1s ease-in-out,
left 0.1s ease-in-out,
width 0.1s ease-in-out,
height 0.1s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
series-build.buildSeriesPipeline (cyclomatic 154) packages/viewer-charts/src/ts/charts/series/series-build.ts:420— series-build.buildSeriesPipeline has cyclomatic complexity 154 (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.
cartesian-build.processCartesianChunk (cyclomatic 86) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:297— cartesian-build.processCartesianChunk has cyclomatic complexity 86 (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.
cartesian-render.renderFacetedChromeOverlay (cyclomatic 70) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970— cartesian-render.renderFacetedChromeOverlay has cyclomatic complexity 70 (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.
body.applyBodyCellStyles (cyclomatic 62) packages/viewer-datagrid/src/ts/style_handlers/body.ts:132— body.applyBodyCellStyles has cyclomatic complexity 62 (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 (body.applyBodyCellStyles::col_state) 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.
candlestick-build.buildCandlestickPipeline (cyclomatic 60) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227— candlestick-build.buildCandlestickPipeline has cyclomatic complexity 60 (threshold 15). Of this number, 59 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.
VirtualServer::internal_handle_request (cyclomatic 56) rust/perspective-client/src/rust/virtual_server/server.rs:223— VirtualServer::internal_handle_request has cyclomatic complexity 56 (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.
series-render.renderBarFrame (cyclomatic 53) packages/viewer-charts/src/ts/charts/series/series-render.ts:383— series-render.renderBarFrame has cyclomatic complexity 53 (threshold 15). Of this number, 52 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.
PerspectiveViewer::update (cyclomatic 49) rust/perspective-viewer/src/rust/components/viewer.rs:232— PerspectiveViewer::update has cyclomatic complexity 49 (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.
ConfigSelector::update (cyclomatic 46) rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:132— ConfigSelector::update has cyclomatic complexity 46 (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.
column_header.styleColumnHeaderRow (cyclomatic 46) packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:95— column_header.styleColumnHeaderRow has cyclomatic complexity 46 (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.
tree-data.processTreeChunk (cyclomatic 43) packages/viewer-charts/src/ts/charts/common/tree-data.ts:287— tree-data.processTreeChunk has cyclomatic complexity 43 (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.
body.applyBodyCellStyles::col_state (cyclomatic 42) packages/viewer-datagrid/src/ts/style_handlers/body.ts:158— body.applyBodyCellStyles::col_state has cyclomatic complexity 42 (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. This shape REPEATS in the file: one other method here (body.applyBodyCellStyles) 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.
index.createDataListener.dataListener (cyclomatic 40) packages/viewer-datagrid/src/ts/data_listener/index.ts:71— index.createDataListener.dataListener has cyclomatic complexity 40 (threshold 15). Of this number, 37 points are the body's own statements and 3 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.
cartesian-render.renderFacetedFrame (cyclomatic 38) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:554— cartesian-render.renderFacetedFrame has cyclomatic complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 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.
WindowEditor::update (cyclomatic 37) rust/perspective-viewer/src/rust/components/window_editor.rs:581— WindowEditor::update has cyclomatic complexity 37 (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.
last-group-by-split.lastGroupBySplit (cyclomatic 37) packages/viewer-charts/src/ts/data/last-group-by-split.ts:59— last-group-by-split.lastGroupBySplit has cyclomatic complexity 37 (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.
series-interact.hitTestAreas (cyclomatic 34) packages/viewer-charts/src/ts/charts/series/series-interact.ts:391— series-interact.hitTestAreas has cyclomatic complexity 34 (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.
CustomNumberFormat::update (cyclomatic 32) rust/perspective-viewer/src/rust/components/style_controls/number_string_format.rs:84— CustomNumberFormat::update has cyclomatic complexity 32 (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.
series-interact.handleBarHover (cyclomatic 30) packages/viewer-charts/src/ts/charts/series/series-interact.ts:66— series-interact.handleBarHover has cyclomatic complexity 30 (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.
DragDropList::view (cyclomatic 29) rust/perspective-viewer/src/rust/components/dragdrop_list.rs:190— DragDropList::view 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.
series-render.ensureCatExtents (cyclomatic 29) packages/viewer-charts/src/ts/charts/series/series-render.ts:2007— series-render.ensureCatExtents 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.
gradient.parseCssGradient (cyclomatic 28) packages/viewer-charts/src/ts/theme/gradient.ts:37— gradient.parseCssGradient 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.
category-axis-resolver.resolveCategoryAxis (cyclomatic 28) packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:292— category-axis-resolver.resolveCategoryAxis has cyclomatic complexity 28 (threshold 15). Of this number, 25 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.
series-render.renderFacetedBarChromeOverlay (cyclomatic 27) packages/viewer-charts/src/ts/charts/series/series-render.ts:1259— series-render.renderFacetedBarChromeOverlay 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.
registry.register (cyclomatic 27) rust/perspective-js/src/ts/wasm/registry.ts:241— registry.register has cyclomatic complexity 27 (threshold 15). Of this number, 25 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.
heatmap-build.buildHeatmapPipeline (cyclomatic 26) packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:104— heatmap-build.buildHeatmapPipeline has cyclomatic complexity 26 (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.
render (cyclomatic 25) packages/anywidget/src/js/index.js:80— render has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 15 function items inside it that branch (normalize_config, push_model_to_viewer, push_viewer_to_model, …). 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.
buildCustomElementsManifest (cyclomatic 25) rust/perspective-viewer/tools.mjs:1323— buildCustomElementsManifest has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to 10 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.
LegendController.hitTest (cyclomatic 24) packages/viewer-charts/src/ts/interaction/legend-controller.ts:522— LegendController.hitTest 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.
cartesian-render.renderSinglePlotFrame (cyclomatic 24) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:401— cartesian-render.renderSinglePlotFrame has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs 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.
perspective-server.poly.default (cyclomatic 24) rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:46— perspective-server.poly.default has cyclomatic complexity 24 (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.
Writer::start (cyclomatic 23) rust/perspective-viewer/src/rust/agent/markdown/mod.rs:94— Writer::start has cyclomatic complexity 23 (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.
ControlSpec::apply_default (cyclomatic 23) rust/perspective-viewer/src/rust/config/column_config_schema.rs:645— ControlSpec::apply_default has cyclomatic complexity 23 (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.
candlestick-interact.handleCandlestickHover (cyclomatic 23) packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:53— candlestick-interact.handleCandlestickHover 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.
heatmap-render.renderFacetedHeatmapChromeOverlay (cyclomatic 23) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:719— heatmap-render.renderFacetedHeatmapChromeOverlay 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.
series-render.renderFacetedBarFrame (cyclomatic 23) packages/viewer-charts/src/ts/charts/series/series-render.ts:906— series-render.renderFacetedBarFrame has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 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.
HTMLPerspectiveViewerWebGLPluginElement.column_config_schema (cyclomatic 23) packages/viewer-charts/src/ts/plugin/plugin.ts:631— HTMLPerspectiveViewerWebGLPluginElement.column_config_schema 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.
create.createModel (cyclomatic 23) packages/viewer-datagrid/src/ts/model/create.ts:210— create.createModel has cyclomatic complexity 23 (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.
perspective_js::rust::typed_array::decode_and_call (cyclomatic 22) rust/perspective-js/src/rust/typed_array.rs:117— perspective_js::rust::typed_array::decode_and_call has cyclomatic complexity 22 (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.
PolarsVirtualServerHandler.view_get_data (cyclomatic 22) REDACTED:272— PolarsVirtualServerHandler.view_get_data 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.
cartesian-render.renderCartesianFrame (cyclomatic 22) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:135— cartesian-render.renderCartesianFrame has cyclomatic complexity 22 (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.
ColumnSettingsPanel::update (cyclomatic 21) rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:238— ColumnSettingsPanel::update 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.
facet-grid.buildFacetGrid (cyclomatic 21) packages/viewer-charts/src/ts/layout/facet-grid.ts:218— facet-grid.buildFacetGrid has cyclomatic complexity 21 (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.
treemap-interact.hitTest (cyclomatic 21) packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:40— treemap-interact.hitTest 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.
ScatterGlyph.rebuildBuffers (cyclomatic 21) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:128— ScatterGlyph.rebuildBuffers 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.
RendererTransport._handleRendererMsg (cyclomatic 21) packages/viewer-charts/src/ts/transport/renderer-transport.ts:733— RendererTransport._handleRendererMsg has cyclomatic complexity 21 (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.
select_region.getMouseupListener.<returned closure> (cyclomatic 21) packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:200— select_region.getMouseupListener.<returned closure> 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.
tools.cemMembers (cyclomatic 20) rust/perspective-viewer/tools.mjs:1041— tools.cemMembers 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.
heatmap-render.renderHeatmapFrame (cyclomatic 20) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:83— heatmap-render.renderHeatmapFrame 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.
series-render.uploadBarInstances (cyclomatic 20) packages/viewer-charts/src/ts/charts/series/series-render.ts:129— series-render.uploadBarInstances has cyclomatic complexity 20 (threshold 15). Of this number, 19 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.
Client::table (cyclomatic 19) rust/perspective-client/src/rust/client.rs:579— Client::table 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.
ViewConfig::apply_update (cyclomatic 19) rust/perspective-client/src/rust/config/view_config.rs:525— ViewConfig::apply_update 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.
FilterColumnProps::update_filter_input (cyclomatic 19) rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:461— FilterColumnProps::update_filter_input 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.
PerspectiveViewerElement::load (cyclomatic 19) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:502— PerspectiveViewerElement::load 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.
tools.declarationEnd (cyclomatic 19) rust/perspective-viewer/tools.mjs:197— tools.declarationEnd 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.
cartesian-build.initCartesianPipeline (cyclomatic 19) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:102— cartesian-build.initCartesianPipeline 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.
heatmap-render.renderFacetedHeatmap (cyclomatic 19) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:558— heatmap-render.renderFacetedHeatmap 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.
series-interact.hitTestPoints (cyclomatic 19) packages/viewer-charts/src/ts/charts/series/series-interact.ts:289— series-interact.hitTestPoints 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.
series-render.renderBarTooltipCanvas (cyclomatic 19) packages/viewer-charts/src/ts/charts/series/series-render.ts:1685— series-render.renderBarTooltipCanvas 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.
SeriesChart.uploadAndRender (cyclomatic 19) packages/viewer-charts/src/ts/charts/series/series.ts:584— SeriesChart.uploadAndRender 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.
duckdb.duckdbTypeToPsp (cyclomatic 19) rust/perspective-js/src/ts/virtual_servers/duckdb.ts:166— duckdb.duckdbTypeToPsp 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.
MainPanel::reconcile (cyclomatic 18) rust/perspective-viewer/src/rust/components/main_panel/reconcile.rs:129— MainPanel::reconcile 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.
StatusBar::update (cyclomatic 18) rust/perspective-viewer/src/rust/components/status_bar.rs:187— StatusBar::update has cyclomatic complexity 18 (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.
candlestick-render.renderCandlestickFrame (cyclomatic 18) packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:91— candlestick-render.renderCandlestickFrame has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs 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.
border_model.classify_header_cell (cyclomatic 18) packages/viewer-datagrid/src/ts/style_handlers/border_model.ts:185— border_model.classify_header_cell 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.
editable.applyColumnHeaderStyles (cyclomatic 18) packages/viewer-datagrid/src/ts/style_handlers/editable.ts:24— editable.applyColumnHeaderStyles has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
ColumnsIteratorSet::active (cyclomatic 17) rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:93— ColumnsIteratorSet::active 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.
gradient.tokenizeLinearGradient (cyclomatic 17) packages/viewer-charts/src/ts/theme/gradient.ts:248— gradient.tokenizeLinearGradient 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.
cartesian-render.renderScatterLabels (cyclomatic 17) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1284— cartesian-render.renderScatterLabels 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.
heatmap-interact.renderHeatmapTooltip (cyclomatic 17) packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts:217— heatmap-interact.renderHeatmapTooltip has cyclomatic complexity 17 (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.
treemap-render.generateAndUploadTreemap (cyclomatic 17) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:306— treemap-render.generateAndUploadTreemap has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
sunburst-interact.handleSunburstClick (cyclomatic 17) packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:215— sunburst-interact.handleSunburstClick 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.
series-render.paintBarChromeOverlay (cyclomatic 17) packages/viewer-charts/src/ts/charts/series/series-render.ts:1148— series-render.paintBarChromeOverlay has cyclomatic complexity 17 (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.
color_utils.tokenizeLinearGradient (cyclomatic 17) REDACTED:304— color_utils.tokenizeLinearGradient 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.
restore.restore_grid_style (cyclomatic 17) packages/viewer-datagrid/src/ts/plugin/restore.ts:112— restore.restore_grid_style has cyclomatic complexity 17 (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.
numeric.cell_style_numeric (cyclomatic 17) packages/viewer-datagrid/src/ts/style_handlers/table_cell/numeric.ts:97— numeric.cell_style_numeric 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.
perspective_migrate::workspace::regular_layout::regular_layout (cyclomatic 16) rust/perspective-migrate/src/workspace/regular_layout.rs:20— perspective_migrate::workspace::regular_layout::regular_layout 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.
ActiveColumn::view (cyclomatic 16) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:213— ActiveColumn::view 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.
ColumnSelector::view (cyclomatic 16) rust/perspective-viewer/src/rust/components/column_selector.rs:316— ColumnSelector::view 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.
WindowDraft::validate (cyclomatic 16) rust/perspective-viewer/src/rust/components/window_editor.rs:180— WindowDraft::validate 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.
renderer.activate (cyclomatic 16) packages/jupyterlab/src/js/renderer.js:238— renderer.activate has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 321, a function literal at line 333, a function literal at line 345, …). 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.
gradient.parseCssColorStrict (cyclomatic 16) packages/viewer-charts/src/ts/theme/gradient.ts:185— gradient.parseCssColorStrict has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 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.
tile-source.parseTileSourceSpec (cyclomatic 16) packages/viewer-charts/src/ts/map/tile-source.ts:129— tile-source.parseTileSourceSpec has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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.
cartesian-render.renderSinglePlotChromeOverlay (cyclomatic 16) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:828— cartesian-render.renderSinglePlotChromeOverlay 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.
tooltip-lines.buildPointRowTooltipLines (cyclomatic 16) packages/viewer-charts/src/ts/charts/cartesian/tooltip-lines.ts:24— tooltip-lines.buildPointRowTooltipLines 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.
DensityGlyph.runSplatAndResolve (cyclomatic 16) packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts:630— DensityGlyph.runSplatAndResolve 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.
treemap-render.paintTreemapChromeOverlay (cyclomatic 16) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:480— treemap-render.paintTreemapChromeOverlay has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 505). 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.
sunburst-render.renderSunburstFrame (cyclomatic 16) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:86— sunburst-render.renderSunburstFrame 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.
series-interact.hitTestBars (cyclomatic 16) packages/viewer-charts/src/ts/charts/series/series-interact.ts:232— series-interact.hitTestBars 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.
ScatterGlyph.draw (cyclomatic 16) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:275— ScatterGlyph.draw 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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/jupyterlab packages/jupyterlab/test/jupyter/utils.mjs:133— No conventional assertion call was detected in 1 of 1 tests in `packages/jupyterlab` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
XxxComment rust/perspective-python/perspective/widget/__init__.py:304— # XXX(tom): client won't reliably send this so shouldn't rely on 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.
series-build.buildSeriesPipeline (cognitive 369) packages/viewer-charts/src/ts/charts/series/series-build.ts:420— series-build.buildSeriesPipeline has cognitive complexity 369 (threshold 15). Drivers by points: if/else 67 (209 pts), loops 35 (71 pts), ternaries 28 (69 pts), boolean chains 20 (nesting depth added 219). 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.
cartesian-build.processCartesianChunk (cognitive 173) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:297— cartesian-build.processCartesianChunk has cognitive complexity 173 (threshold 15). Drivers by points: if/else 53 (126 pts), ternaries 9 (21 pts), boolean chains 15, loops 6 (11 pts) (nesting depth added 90). 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.
cartesian-render.renderFacetedChromeOverlay (cognitive 112) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970— cartesian-render.renderFacetedChromeOverlay has cognitive complexity 112 (threshold 15). Drivers by points: ternaries 22 (50 pts), if/else 19 (37 pts), boolean chains 22, loops 2 (3 pts) (nesting depth added 47). 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.
candlestick-build.buildCandlestickPipeline (cognitive 97) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227— candlestick-build.buildCandlestickPipeline has cognitive complexity 97 (threshold 15). Drivers by points: if/else 27 (53 pts), ternaries 9 (22 pts), boolean chains 15, loops 5 (7 pts) (nesting depth added 41). Of this number, 95 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.
tree-data.processTreeChunk (cognitive 76) packages/viewer-charts/src/ts/charts/common/tree-data.ts:287— tree-data.processTreeChunk has cognitive complexity 76 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 8 (17 pts), ternaries 9 (14 pts), boolean chains 8 (nesting depth added 32). 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.
body.applyBodyCellStyles (cognitive 74) packages/viewer-datagrid/src/ts/style_handlers/body.ts:132— body.applyBodyCellStyles has cognitive complexity 74 (threshold 15). Drivers by points: if/else 25 (46 pts), boolean chains 36, ternaries 6 (8 pts), loops 2 (4 pts) (nesting depth added 25). 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. This shape REPEATS in the file: one other method here (body.applyBodyCellStyles::col_state) 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.
series-render.ensureCatExtents (cognitive 70) packages/viewer-charts/src/ts/charts/series/series-render.ts:2007— series-render.ensureCatExtents has cognitive complexity 70 (threshold 15). Drivers by points: if/else 19 (54 pts), loops 5 (8 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 40). 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.
last-group-by-split.lastGroupBySplit (cognitive 67) packages/viewer-charts/src/ts/data/last-group-by-split.ts:59— last-group-by-split.lastGroupBySplit has cognitive complexity 67 (threshold 15). Drivers by points: if/else 17 (39 pts), loops 13 (18 pts), ternaries 3 (7 pts), boolean chains 3 (nesting depth added 31). 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.
series-render.renderBarFrame (cognitive 66) packages/viewer-charts/src/ts/charts/series/series-render.ts:383— series-render.renderBarFrame has cognitive complexity 66 (threshold 15). Drivers by points: if/else 26 (37 pts), ternaries 14 (20 pts), boolean chains 9 (nesting depth added 17). Of this number, 65 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.
index.createDataListener.dataListener (cognitive 58) packages/viewer-datagrid/src/ts/data_listener/index.ts:71— index.createDataListener.dataListener has cognitive complexity 58 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 6 (14 pts), ternaries 7 (12 pts), boolean chains 11 (nesting depth added 22). Of this number, 54 points are the body's own statements and 4 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.
VirtualServer::internal_handle_request (cognitive 54) rust/perspective-client/src/rust/virtual_server/server.rs:223— VirtualServer::internal_handle_request has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (33 pts), loops 5 (12 pts), match/switch 3 (7 pts), boolean chains 2 (nesting depth added 28). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
series-interact.hitTestAreas (cognitive 51) packages/viewer-charts/src/ts/charts/series/series-interact.ts:391— series-interact.hitTestAreas has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (29 pts), ternaries 7 (11 pts), boolean chains 9, loops 2 (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.
category-axis-resolver.resolveCategoryAxis (cognitive 48) packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:292— category-axis-resolver.resolveCategoryAxis has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 5 (11 pts), ternaries 3 (7 pts), boolean chains 6 (nesting depth added 23). Of this number, 41 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.
registry.register (cognitive 47) rust/perspective-js/src/ts/wasm/registry.ts:241— registry.register has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (31 pts), loops 4 (10 pts), boolean chains 6 (nesting depth added 21). Of this number, 46 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.
ConfigSelector::update (cognitive 46) rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:132— ConfigSelector::update has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (43 pts), boolean chains 2, match/switch 1 (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
heatmap-build.buildHeatmapPipeline (cognitive 46) packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:104— heatmap-build.buildHeatmapPipeline has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (32 pts), boolean chains 5, ternaries 2 (5 pts), loops 3 (4 pts) (nesting depth added 21). 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.
buildCustomElementsManifest (cognitive 46) rust/perspective-viewer/tools.mjs:1323— buildCustomElementsManifest has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (30 pts), ternaries 3 (9 pts), other 5, loops 2 (nesting depth added 20). Of this number, 42 points are the body's own statements and 4 belong to 10 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.
cartesian-render.renderFacetedFrame (cognitive 44) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:554— cartesian-render.renderFacetedFrame has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 15, if/else 5 (9 pts), loops 2 (3 pts) (nesting depth added 12). Of this number, 36 points are the body's own statements and 8 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.
DragDropList::view (cognitive 43) rust/perspective-viewer/src/rust/components/dragdrop_list.rs:190— DragDropList::view has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (28 pts), boolean chains 15 (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.
series-render.renderFacetedBarChromeOverlay (cognitive 41) packages/viewer-charts/src/ts/charts/series/series-render.ts:1259— series-render.renderFacetedBarChromeOverlay has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 8, loops 1, ternaries 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.
tools.cemMembers (cognitive 40) rust/perspective-viewer/tools.mjs:1041— tools.cemMembers has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (26 pts), ternaries 3 (9 pts), boolean chains 4, loops 1 (nesting depth added 21). 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.
treemap-interact.hitTest (cognitive 40) packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:40— treemap-interact.hitTest has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (30 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (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.
ScatterGlyph.rebuildBuffers (cognitive 39) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:128— ScatterGlyph.rebuildBuffers has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 3 (7 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 17). 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.
ColumnsIteratorSet::active (cognitive 37) rust/perspective-viewer/src/rust/queries/columns_iter_set.rs:93— ColumnsIteratorSet::active has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 4 (10 pts), boolean chains 5 (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
perspective-server.poly.default (cognitive 37) rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:46— perspective-server.poly.default has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (22 pts), loops 6 (12 pts), boolean chains 2, ternaries 1 (nesting depth added 11). 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.
gradient.parseCssGradient (cognitive 36) packages/viewer-charts/src/ts/theme/gradient.ts:37— gradient.parseCssGradient has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (20 pts), loops 5 (7 pts), ternaries 2 (4 pts), boolean chains 3, error handling 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.
heatmap-render.renderFacetedHeatmapChromeOverlay (cognitive 35) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:719— heatmap-render.renderFacetedHeatmapChromeOverlay has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 7, ternaries 4 (7 pts), loops 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.
series-render.uploadBarInstances (cognitive 35) packages/viewer-charts/src/ts/charts/series/series-render.ts:129— series-render.uploadBarInstances has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 3 (7 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 15). Of this number, 32 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.
series-interact.handleBarHover (cognitive 34) packages/viewer-charts/src/ts/charts/series/series-interact.ts:66— series-interact.handleBarHover has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 5, ternaries 3 (4 pts), loops 2 (3 pts), match/switch 1 (2 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.
ColumnSettingsPanel::update (cognitive 32) rust/perspective-viewer/src/rust/components/column_settings_sidebar.rs:238— ColumnSettingsPanel::update has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 3 (7 pts) (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WindowEditor::update (cognitive 32) rust/perspective-viewer/src/rust/components/window_editor.rs:581— WindowEditor::update has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 8, match/switch 3 (5 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
series-interact.hitTestPoints (cognitive 32) packages/viewer-charts/src/ts/charts/series/series-interact.ts:289— series-interact.hitTestPoints has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 3 (7 pts), boolean chains 4, loops 2 (3 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.
column_header.styleColumnHeaderRow (cognitive 32) packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:95— column_header.styleColumnHeaderRow has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 21, ternaries 3 (6 pts), if/else 2 (4 pts), loops 1 (nesting depth added 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.
bar-axis.renderBarAxesChrome (cognitive 31) packages/viewer-charts/src/ts/axis/bar-axis.ts:189— bar-axis.renderBarAxesChrome has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (31 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.
tree-data.finalizeTree (cognitive 31) packages/viewer-charts/src/ts/charts/common/tree-data.ts:567— tree-data.finalizeTree has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 6 (13 pts), boolean chains 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.
heatmap-render.renderFacetedHeatmap (cognitive 31) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:558— heatmap-render.renderFacetedHeatmap has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (20 pts), if/else 4 (8 pts), loops 2, boolean chains 1 (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.
editable.applyColumnHeaderStyles (cognitive 31) packages/viewer-datagrid/src/ts/style_handlers/editable.ts:24— editable.applyColumnHeaderStyles has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 4 (9 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 13). Of this number, 23 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.
render (cognitive 31) packages/anywidget/src/js/index.js:80— render has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 6, loops 4, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 15 function items inside it that branch (normalize_config, push_model_to_viewer, push_viewer_to_model, …). 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.
Client::table (cognitive 30) rust/perspective-client/src/rust/client.rs:579— Client::table has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 7, match/switch 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.
sunburst-render.drawStaticChrome (cognitive 30) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:554— sunburst-render.drawStaticChrome has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 4 (9 pts), boolean chains 1, ternaries 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.
series-render.computeVisibleValueExtent (cognitive 30) packages/viewer-charts/src/ts/charts/series/series-render.ts:1824— series-render.computeVisibleValueExtent has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 1 (2 pts), boolean chains 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.
HTMLPerspectiveViewerWebGLPluginElement.column_config_schema (cognitive 30) packages/viewer-charts/src/ts/plugin/plugin.ts:631— HTMLPerspectiveViewerWebGLPluginElement.column_config_schema has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 7, ternaries 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.
PolarsVirtualServerHandler.view_get_data (cognitive 29) REDACTED:272— PolarsVirtualServerHandler.view_get_data has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 7, loops 3 (4 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.
LegendController.hitTest (cognitive 29) packages/viewer-charts/src/ts/interaction/legend-controller.ts:522— LegendController.hitTest has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 9 (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.
FilterColumnProps::update_filter_input (cognitive 28) rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:461— FilterColumnProps::update_filter_input has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 4 (11 pts), boolean chains 2 (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.
PerspectiveViewerElement::load (cognitive 28) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:502— PerspectiveViewerElement::load has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 4 (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.
split-groups.buildSplitGroups (cognitive 28) packages/viewer-charts/src/ts/data/split-groups.ts:35— split-groups.buildSplitGroups has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4 (6 pts), boolean chains 2 (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.
treemap-render.renderBranchLabel (cognitive 28) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:751— treemap-render.renderBranchLabel has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (6 pts), boolean chains 2 (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.
draw-areas.collectAreaStrips (cognitive 28) packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:298— draw-areas.collectAreaStrips has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (23 pts), ternaries 1 (3 pts), boolean chains 1, 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.
activate.activate (cognitive 28) packages/viewer-datagrid/src/ts/plugin/activate.ts:62— activate.activate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 11). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 2 function items inside it that branch (onSelect, a function literal at line 247). 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.
sunburst-interact.handleSunburstClick (cognitive 27) packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:215— sunburst-interact.handleSunburstClick has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 2, loops 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.
declarationEnd (cognitive 27) rust/perspective-viewer/tools.mjs:197— declarationEnd has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (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.
WindowDraft::validate (cognitive 26) rust/perspective-viewer/src/rust/components/window_editor.rs:180— WindowDraft::validate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 1 (2 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.
polars.build_split_by_grouped (cognitive 26) REDACTED:661— polars.build_split_by_grouped has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (13 pts), if/else 7 (12 pts), boolean chains 1 (nesting depth added 11). 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.
gradient.tokenizeLinearGradient (cognitive 26) packages/viewer-charts/src/ts/theme/gradient.ts:248— gradient.tokenizeLinearGradient has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, loops 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.
category-axis-resolver.resolveValueCategoryDomain (cognitive 26) packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:458— category-axis-resolver.resolveValueCategoryDomain has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 4 (5 pts), ternaries 1 (4 pts), boolean chains 1 (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.
cartesian-render.renderCartesianFrame (cognitive 26) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:135— cartesian-render.renderCartesianFrame has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 10 (11 pts), ternaries 1 (2 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.
treemap-render.paintTreemapChromeOverlay (cognitive 26) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:480— treemap-render.paintTreemapChromeOverlay has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 4 (8 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 505). 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.
series-interact.hitTestBars (cognitive 26) packages/viewer-charts/src/ts/charts/series/series-interact.ts:232— series-interact.hitTestBars has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (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.
ScatterGlyph.draw (cognitive 26) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:275— ScatterGlyph.draw has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (9 pts), boolean chains 6, loops 1 (2 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.
color_utils.tokenizeLinearGradient (cognitive 26) REDACTED:304— color_utils.tokenizeLinearGradient has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, loops 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.
CustomNumberFormat::update (cognitive 25) rust/perspective-viewer/src/rust/components/style_controls/number_string_format.rs:84— CustomNumberFormat::update has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 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.
candlestick-interact.handleCandlestickHover (cognitive 25) packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:53— candlestick-interact.handleCandlestickHover has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, ternaries 3 (5 pts), loops 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.
cartesian-render.renderSinglePlotChromeOverlay (cognitive 25) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:828— cartesian-render.renderSinglePlotChromeOverlay has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 2 (4 pts), boolean chains 3 (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.
tree-data.insertRow (cognitive 25) packages/viewer-charts/src/ts/charts/common/tree-data.ts:109— tree-data.insertRow has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (23 pts), boolean chains 1, 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.
treemap-render.generateAndUploadTreemap (cognitive 25) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:306— treemap-render.generateAndUploadTreemap has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 2, loops 2, ternaries 2 (nesting depth added 8). Of this number, 23 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.
column_header.style_selected_column (cognitive 25) packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:26— column_header.style_selected_column has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 4 (9 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 12). Of this number, 17 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.
focus.focusSelectedCell (cognitive 25) packages/viewer-datagrid/src/ts/style_handlers/focus.ts:64— focus.focusSelectedCell has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (5 pts), boolean chains 2 (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.
select_region.getMouseupListener.<returned closure> (cognitive 25) packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:200— select_region.getMouseupListener.<returned closure> has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5 (nesting depth added 11). 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.
ChunkAccumulator::push (cognitive 24) rust/perspective-viewer/src/rust/agent/client/protocol.rs:172— ChunkAccumulator::push has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (3 pts) (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.
OpQueue::drain (cognitive 24) rust/perspective-viewer/src/rust/session/op_queue.rs:260— OpQueue::drain has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (10 pts), match/switch 2 (4 pts) (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.
tools.cemCssProperties (cognitive 24) rust/perspective-viewer/tools.mjs:813— tools.cemCssProperties has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (7 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 11). Of this number, 18 points are the body's own statements and 6 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.
series-render.renderFacetedBarFrame (cognitive 24) packages/viewer-charts/src/ts/charts/series/series-render.ts:906— series-render.renderFacetedBarFrame has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (12 pts), if/else 4 (6 pts), boolean chains 5, loops 1 (nesting depth added 4). Of this number, 21 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.
normalizeChunks (cognitive 24) rust/perspective-viewer/tools.mjs:298— normalizeChunks has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (7 pts), loops 3 (4 pts), boolean chains 2 (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.
tree-interact.buildTreeTooltipLines (cognitive 23) packages/viewer-charts/src/ts/charts/common/tree-interact.ts:74— tree-interact.buildTreeTooltipLines has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, loops 2 (3 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.
ColumnSelector::view (cognitive 22) rust/perspective-viewer/src/rust/components/column_selector.rs:316— ColumnSelector::view has cognitive complexity 22 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 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.
categorical-axis.renderLeafLevel (cognitive 22) packages/viewer-charts/src/ts/axis/categorical-axis.ts:343— categorical-axis.renderLeafLevel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, loops 2, ternaries 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.
tooltip-lines.buildPointRowTooltipLines (cognitive 22) packages/viewer-charts/src/ts/charts/cartesian/tooltip-lines.ts:24— tooltip-lines.buildPointRowTooltipLines has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, loops 1, ternaries 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.
cartesian-build.initCartesianPipeline (cognitive 22) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:102— cartesian-build.initCartesianPipeline has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 9 (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.
series-render.renderBarTooltipCanvas (cognitive 22) packages/viewer-charts/src/ts/charts/series/series-render.ts:1685— series-render.renderBarTooltipCanvas has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (14 pts), if/else 6, boolean chains 2 (nesting depth added 4). 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.
border_model.classify_header_cell (cognitive 22) packages/viewer-datagrid/src/ts/style_handlers/border_model.ts:185— border_model.classify_header_cell has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (6 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.
FilterColumn::update (cognitive 21) rust/perspective-viewer/src/rust/components/column_selector/filter_column.rs:118— FilterColumn::update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
facet-grid.buildFacetGrid (cognitive 21) packages/viewer-charts/src/ts/layout/facet-grid.ts:218— facet-grid.buildFacetGrid has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (14 pts), boolean chains 5, if/else 1, 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.
treemap-render.drawStaticChrome (cognitive 21) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:594— treemap-render.drawStaticChrome has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (6 pts), loops 3 (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.
sunburst-render.renderSunburstFrame (cognitive 21) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:86— sunburst-render.renderSunburstFrame has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, ternaries 3, loops 1 (2 pts) (nesting depth added 4). 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.
SeriesChart.uploadAndRender (cognitive 21) packages/viewer-charts/src/ts/charts/series/series.ts:584— SeriesChart.uploadAndRender has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, loops 2, match/switch 1 (2 pts), ternaries 2 (nesting depth added 4). 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.
cemValueExports (cognitive 21) rust/perspective-viewer/tools.mjs:1285— cemValueExports has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), boolean chains 2, other 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.
perspective_js::rust::typed_array::decode_and_call (cognitive 20) rust/perspective-js/src/rust/typed_array.rs:117— perspective_js::rust::typed_array::decode_and_call has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 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.
DensityGlyph.runSplatAndResolve (cognitive 20) packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts:630— DensityGlyph.runSplatAndResolve has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 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.
tree-chrome.renderTreeColorLegend (cognitive 20) packages/viewer-charts/src/ts/charts/common/tree-chrome.ts:162— tree-chrome.renderTreeColorLegend has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 4 (5 pts) (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.
HeatmapChart.uploadAndRender (cognitive 20) packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts:200— HeatmapChart.uploadAndRender has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (5 pts), boolean chains 3 (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.
host-sink-dom.renderTooltipGridDom (cognitive 20) packages/viewer-charts/src/ts/interaction/host-sink-dom.ts:95— host-sink-dom.renderTooltipGridDom has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (6 pts), boolean chains 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.
body.applyBodyCellStyles::col_state (cognitive 20) packages/viewer-datagrid/src/ts/style_handlers/body.ts:158— body.applyBodyCellStyles::col_state has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, ternaries 3, if/else 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. This shape REPEATS in the file: one other method here (body.applyBodyCellStyles) 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.
consolidated.createConsolidatedStyleListener.consolidatedStyleListener (cognitive 20) packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:44— consolidated.createConsolidatedStyleListener.consolidatedStyleListener has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (6 pts), boolean chains 4 (nesting depth added 9). 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.
perspective.node.cwd_static_file_handler (cognitive 20) rust/perspective-js/src/ts/perspective.node.ts:352— perspective.node.cwd_static_file_handler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 2 (3 pts), 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.
polars.build_rollup (cognitive 19) REDACTED:421— polars.build_rollup has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (7 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.
cartesian-render.renderSinglePlotFrame (cognitive 19) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:401— cartesian-render.renderSinglePlotFrame has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), if/else 4 (nesting depth added 1). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
heatmap-render.renderHeatmapFrame (cognitive 19) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:83— heatmap-render.renderHeatmapFrame has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11, if/else 6, boolean chains 2. 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.
heatmap-interact.renderHeatmapTooltip (cognitive 19) packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts:217— heatmap-interact.renderHeatmapTooltip has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4, boolean chains 3 (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.
isEqual (cognitive 19) packages/anywidget/src/js/index.js:61— isEqual has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 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.
ViewConfig::apply_update (cognitive 18) rust/perspective-client/src/rust/config/view_config.rs:525— ViewConfig::apply_update has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 15, if/else 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.
tools.cemFindDeclaration (cognitive 18) rust/perspective-viewer/tools.mjs:1151— tools.cemFindDeclaration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 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.
label-geometry.wrapLabel (cognitive 18) packages/viewer-charts/src/ts/axis/label-geometry.ts:131— label-geometry.wrapLabel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 2 (3 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.
candlestick-render.renderCandlestickFrame (cognitive 18) packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:91— candlestick-render.renderCandlestickFrame has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, ternaries 3 (nesting depth added 1). 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: 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.
cartesian-render.renderScatterLabels (cognitive 18) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1284— cartesian-render.renderScatterLabels has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (4 pts), boolean chains 2, 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.
heatmap-render.paintHeatmapChromeOverlay (cognitive 18) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:411— heatmap-render.paintHeatmapChromeOverlay has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 2, ternaries 1 (2 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.
sunburst-interact.polarHitTest (cognitive 18) packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:106— sunburst-interact.polarHitTest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, loops 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.
column_overrides.reconcile_column_widths (cognitive 18) packages/viewer-datagrid/src/ts/model/column_overrides.ts:27— column_overrides.reconcile_column_widths has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 16 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.
cell_flash.style_cell_flash (cognitive 18) packages/viewer-datagrid/src/ts/style_handlers/table_cell/cell_flash.ts:16— cell_flash.style_cell_flash has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (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.
Layout::validate_node (cognitive 17) rust/perspective-client/src/rust/config/viewer/layout.rs:81— Layout::validate_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), boolean chains 2, match/switch 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.
Run::apply (cognitive 17) rust/perspective-migrate/src/step.rs:143— Run::apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (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.
ActiveColumn::view (cognitive 17) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:213— ActiveColumn::view has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2, boolean chains 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.
clickhouse.clickhouse_to_py (cognitive 17) rust/perspective-python/perspective/virtual_servers/clickhouse.py:349— clickhouse.clickhouse_to_py has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 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.
gradient.parseCssColorStrict (cognitive 17) packages/viewer-charts/src/ts/theme/gradient.ts:185— gradient.parseCssColorStrict has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 3 (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 belong 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.
treemap-interact.handleTreemapHover (cognitive 17) packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:122— treemap-interact.handleTreemapHover has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 6). 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 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.
sunburst-interact.handleSunburstHover (cognitive 17) packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:163— sunburst-interact.handleSunburstHover has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 6). 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 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.
series-render.drawGlyphRuns (cognitive 17) packages/viewer-charts/src/ts/charts/series/series-render.ts:764— series-render.drawGlyphRuns has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), ternaries 2 (5 pts), match/switch 1 (2 pts), 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.
column_alignment.sync_column_alignment (cognitive 17) packages/viewer-datagrid/src/ts/style_handlers/column_alignment.ts:65— column_alignment.sync_column_alignment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, loops 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.
clickhouse.clickhouseToJs (cognitive 17) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:206— clickhouse.clickhouseToJs has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (6 pts), boolean chains 1, match/switch 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.
cemCssDeclarations (cognitive 17) rust/perspective-viewer/tools.mjs:732— cemCssDeclarations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1, other 1 (nesting depth added 8). Of this number, 16 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.
SplitPanel::update (cognitive 16) rust/perspective-viewer/src/rust/ui/containers/split_panel.rs:137— SplitPanel::update has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
virtual_servers.sql_table_describe (cognitive 16) rust/perspective-python/perspective/virtual_servers/__init__.py:210— virtual_servers.sql_table_describe has cognitive complexity 16 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 3 (5 pts), loops 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.
PolarsVirtualServerHandler._build_view (cognitive 16) REDACTED:201— PolarsVirtualServerHandler._build_view has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). 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.
index.convert (cognitive 16) packages/cli/src/js/index.js:32— index.convert has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 1, error handling 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.
cartesian-interact.handleCartesianHover (cognitive 16) packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts:69— cartesian-interact.handleCartesianHover has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, ternaries 3 (nesting depth added 3). Of this number, 13 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.
heatmap-build.buildYLevelsFromNames (cognitive 16) packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:394— heatmap-build.buildYLevelsFromNames has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (4 pts), ternaries 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.
treemap-layout.collectVisibleAppend (cognitive 16) packages/viewer-charts/src/ts/charts/treemap/treemap-layout.ts:266— treemap-layout.collectVisibleAppend has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 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.
treemap-render.renderTreemapFrame (cognitive 16) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:49— treemap-render.renderTreemapFrame has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 3, ternaries 3, loops 1 (2 pts) (nesting depth added 2). 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.
series-interact.handleBarLegendClick (cognitive 16) packages/viewer-charts/src/ts/charts/series/series-interact.ts:556— series-interact.handleBarLegendClick has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 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.
AreaGlyph.draw (cognitive 16) packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:195— AreaGlyph.draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, loops 2 (3 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.
restore.restore (cognitive 16) packages/viewer-datagrid/src/ts/plugin/restore.ts:262— restore.restore has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2, boolean chains 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.
Change-coupling hub: duckdb.ts → table_make_view.rs, tests.rs, server.rs rust/perspective-js/src/ts/virtual_servers/duckdb.ts— `rust/perspective-js/src/ts/virtual_servers/duckdb.ts` changes together with 3 other files — `rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs`, `rust/perspective-client/src/rust/virtual_server/generic_sql_model/tests.rs`, `rust/perspective-client/src/rust/virtual_server/server.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (81 corresponding lines) · ×1
Edited copy of a member (81 corresponding lines) rust/perspective-viewer/src/rust/tasks/copy_export.rs:172— rust/perspective-viewer/src/rust/tasks/copy_export.rs:172-253 | rust/perspective-viewer/src/rust/tasks/copy_export.rs:262-342 — These two members are one piece of code written twice and then edited apart: 81 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 67+ corresponding lines) · ×1
Edited copies of one member (3 members, 67+ corresponding lines) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:285— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:285-351 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:388-464 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:489-560 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 67 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) REDACTED:422— REDACTED:422-468 | REDACTED:662-720 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) rust/perspective-client/src/rust/config/view_config.rs:392— rust/perspective-client/src/rust/config/view_config.rs:392-436 | rust/perspective-client/src/rust/config/view_config.rs:459-501 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) rust/perspective-python/src/client/pandas.rs:60— rust/perspective-python/src/client/pandas.rs:60-110 | rust/perspective-python/src/client/polars.rs:64-109 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) rust/perspective-viewer/src/rust/components/viewer/wiring.rs:109— rust/perspective-viewer/src/rust/components/viewer/wiring.rs:109-162 | rust/perspective-viewer/src/rust/components/viewer/wiring.rs:174-223 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) rust/perspective-python/src/client/client_async.rs:1065— rust/perspective-python/src/client/client_async.rs:1065-1108 | rust/perspective-python/src/client/client_async.rs:1144-1176 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) rust/perspective-viewer/src/rust/components/column_dropdown.rs:199— rust/perspective-viewer/src/rust/components/column_dropdown.rs:199-231 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:141-172 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:31— rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:31-60 | rust/perspective-viewer/src/rust/tasks/set_edit_mode.rs:30-69 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:260— rust/perspective-python/perspective/virtual_servers/clickhouse.py:260-279 | rust/perspective-python/perspective/virtual_servers/postgres.py:343-369 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 22+ corresponding lines) · ×1
Edited copies of one member (4 members, 22+ corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:934— rust/perspective-js/src/rust/virtual_server.rs:934-955 | rust/perspective-js/src/rust/virtual_server.rs:964-985 | rust/perspective-js/src/rust/virtual_server.rs:994-1015 | rust/perspective-js/src/rust/virtual_server.rs:1024-1045 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1445— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1445-1477 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1497-1526 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1543-1571 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) rust/perspective-js/src/rust/virtual_server.rs:295— rust/perspective-js/src/rust/virtual_server.rs:295-311 | rust/perspective-js/src/rust/virtual_server.rs:633-652 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs:601— rust/perspective-python/src/server/virtual_server_sync.rs:601-622 | rust/perspective-python/src/server/virtual_server_sync.rs:631-647 | rust/perspective-python/src/server/virtual_server_sync.rs:656-672 | rust/perspective-python/src/server/virtual_server_sync.rs:681-697 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) rust/perspective-viewer/src/rust/tasks/apply_config_defaults.rs:61— rust/perspective-viewer/src/rust/tasks/apply_config_defaults.rs:61-84 | rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:64-86 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) rust/perspective-client/src/rust/table.rs:623— rust/perspective-client/src/rust/table.rs:623-631 | rust/perspective-client/src/rust/table.rs:660-673 | rust/perspective-client/src/rust/view.rs:479-488 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) rust/perspective-python/src/server/virtual_server_sync.rs:153— rust/perspective-python/src/server/virtual_server_sync.rs:153-163 | rust/perspective-python/src/server/virtual_server_sync.rs:285-295 | rust/perspective-python/src/server/virtual_server_sync.rs:365-374 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) rust/perspective-python/src/server/generic_sql_model.rs:88— rust/perspective-python/src/server/generic_sql_model.rs:88-97 | rust/perspective-python/src/server/generic_sql_model.rs:250-259 | rust/perspective-python/src/server/generic_sql_model.rs:268-277 | rust/perspective-python/src/server/generic_sql_model.rs:286-295 | rust/perspective-python/src/server/generic_sql_model.rs:299-308 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) rust/perspective-python/src/client/client_async.rs:792— rust/perspective-python/src/client/client_async.rs:792-800 | rust/perspective-python/src/client/client_async.rs:907-914 | rust/perspective-python/src/client/client_async.rs:1189-1195 | rust/perspective-python/src/client/client_async.rs:1198-1204 | rust/perspective-python/src/client/client_async.rs:1213-1219 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) rust/perspective-python/src/client/pandas.rs:19— rust/perspective-python/src/client/pandas.rs:19-27 | rust/perspective-python/src/client/polars.rs:19-27 | rust/perspective-python/src/client/polars.rs:29-37 | rust/perspective-python/src/client/pyarrow.rs:17-25 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 8+ corresponding lines) · ×1
Edited copies of one member (5 members, 8+ corresponding lines) rust/perspective-js/src/rust/generic_sql_model.rs:112— rust/perspective-js/src/rust/generic_sql_model.rs:112-119 | rust/perspective-js/src/rust/generic_sql_model.rs:270-277 | rust/perspective-js/src/rust/generic_sql_model.rs:287-294 | rust/perspective-js/src/rust/generic_sql_model.rs:304-311 | rust/perspective-js/src/rust/generic_sql_model.rs:321-328 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) rust/perspective-client/src/rust/table.rs:710— rust/perspective-client/src/rust/table.rs:710-719 | rust/perspective-client/src/rust/table.rs:740-749 | rust/perspective-client/src/rust/table.rs:772-781 | rust/perspective-client/src/rust/table.rs:810-820 | rust/perspective-client/src/rust/view.rs:668-678 | rust/perspective-client/src/rust/view.rs:735-745 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) rust/perspective-client/src/rust/view.rs:560— rust/perspective-client/src/rust/view.rs:560-569 | rust/perspective-client/src/rust/view.rs:779-785 | rust/perspective-client/src/rust/view.rs:788-794 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:227— rust/perspective-python/perspective/virtual_servers/clickhouse.py:227-230 | rust/perspective-python/perspective/virtual_servers/duckdb.py:281-283 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) rust/perspective-python/perspective/virtual_servers/duckdb.py:310— rust/perspective-python/perspective/virtual_servers/duckdb.py:310-313 | rust/perspective-python/perspective/virtual_servers/postgres.py:337-340 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) rust/perspective-python/perspective/virtual_servers/clickhouse.py:233— rust/perspective-python/perspective/virtual_servers/clickhouse.py:233-236 | rust/perspective-python/perspective/virtual_servers/duckdb.py:286-289 | rust/perspective-python/perspective/virtual_servers/postgres.py:302-310 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (36–41 lines × 2) rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1114— rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1114-1154 | rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1187-1222 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/generic_sql_model/table_make_view.rs:1114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–24 lines × 2) rust/perspective-viewer/src/rust/components/dragdrop_list.rs:248— rust/perspective-viewer/src/rust/components/dragdrop_list.rs:248-256 | rust/perspective-viewer/src/rust/components/dragdrop_list.rs:337-360 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/dragdrop_list.rs:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) rust/perspective-python/src/client/pandas.rs:86— rust/perspective-python/src/client/pandas.rs:86-104 | rust/perspective-python/src/client/polars.rs:85-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/client/pandas.rs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 2) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/font_field.rs:95— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/font_field.rs:95-113 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:74-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/font_field.rs:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&FontFieldProps` in one and `&EnumFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15–16 lines × 2) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1448— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1448-1462 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1500-1515 — 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 (15 lines × 3) rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:289— rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:289-303 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:392-406 | rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:499-513 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_settings_sidebar/style_tab/primitive_field.rs:289` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&PaletteFieldProps` in one and `&GradientStopsFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) rust/perspective-python/src/server/generic_sql_model.rs:118— rust/perspective-python/src/server/generic_sql_model.rs:118-132 | rust/perspective-python/src/server/generic_sql_model.rs:157-171 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-python/src/server/generic_sql_model.rs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 3) rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1448— rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1448-1460 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1500-1513 | rust/perspective-viewer/src/rust/custom_elements/viewer.rs:1545-1558 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 2) rust/perspective-viewer/src/rust/components/chat_panel.rs:42— rust/perspective-viewer/src/rust/components/chat_panel.rs:42-55 | rust/perspective-viewer/src/rust/components/chat_panel.rs:205-218 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/chat_panel.rs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `rust/perspective-viewer/src/rust/components/chat_panel.rs:41` calls `use_mut_ref` and `rust/perspective-viewer/src/rust/components/chat_panel.rs:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 5) rust/perspective-client/src/rust/virtual_server/data.rs:1071— rust/perspective-client/src/rust/virtual_server/data.rs:1071-1082 | rust/perspective-client/src/rust/virtual_server/data.rs:1085-1096 | rust/perspective-client/src/rust/virtual_server/data.rs:1104-1115 | rust/perspective-client/src/rust/virtual_server/data.rs:1118-1129 | rust/perspective-client/src/rust/virtual_server/data.rs:1148-1160 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-client/src/rust/virtual_server/data.rs:1071` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:33— rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:33-42 | rust/perspective-viewer/src/rust/tasks/set_edit_mode.rs:38-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/tasks/send_plugin_config.rs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–10 lines × 14) rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:155— rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:155-163 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:224-233 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:244-252 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:264-272 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:302-310 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:329-336 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:389-397 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:408-416 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:439-447 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:458-466 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:479-487 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:500-508 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:529-537 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:552-560 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:155` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 16) rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:152— rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:152-160 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:169-177 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:185-193 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:221-229 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:241-249 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:261-269 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:326-334 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:368-376 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:386-394 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:405-413 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:436-444 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:455-463 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:476-484 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:497-505 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:526-534 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:549-557 — all 16 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:152` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:162` calls `props`, `emit` and `rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:179` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–9 lines × 5) rust/perspective-client/src/rust/virtual_server/server.rs:473— rust/perspective-client/src/rust/virtual_server/server.rs:473-481 | rust/perspective-client/src/rust/virtual_server/server.rs:488-494 | rust/perspective-client/src/rust/virtual_server/server.rs:516-522 | rust/perspective-client/src/rust/virtual_server/server.rs:535-541 | rust/perspective-client/src/rust/virtual_server/server.rs:550-558 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 5) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:196— rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:196-203 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:474-481 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:495-502 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:524-531 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:547-554 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:196` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 17) rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172— rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172-178 | rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:197-203 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:151-157 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:168-174 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:184-190 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:220-226 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:240-246 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:260-266 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:325-331 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:385-391 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:404-410 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:435-441 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:454-460 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:475-481 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:496-502 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:525-531 | rust/perspective-viewer/src/rust/components/column_selector/config_selector.rs:548-554 — there are 17 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 17 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-viewer/src/rust/components/column_selector/active_column.rs:172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) rust/perspective-js/src/rust/typed_array.rs:208— rust/perspective-js/src/rust/typed_array.rs:208-215 | rust/perspective-js/src/rust/typed_array.rs:253-260 | rust/perspective-js/src/rust/typed_array.rs:278-285 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/typed_array.rs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) rust/perspective-viewer/src/rust/components/column_dropdown.rs:185— rust/perspective-viewer/src/rust/components/column_dropdown.rs:185-193 | rust/perspective-viewer/src/rust/components/filter_dropdown.rs:191-199 | rust/perspective-viewer/src/rust/components/function_dropdown.rs:127-135 — before extracting anything, compare `rust/perspective-viewer/src/rust/components/column_dropdown.rs` and `rust/perspective-viewer/src/rust/components/function_dropdown.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) rust/perspective-python/src/client/pandas.rs:29— rust/perspective-python/src/client/pandas.rs:29-35 | rust/perspective-python/src/client/polars.rs:39-45 | rust/perspective-python/src/client/polars.rs:47-53 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 3) rust/perspective-js/src/rust/virtual_server.rs:944— rust/perspective-js/src/rust/virtual_server.rs:944-955 | rust/perspective-js/src/rust/virtual_server.rs:1004-1015 | rust/perspective-js/src/rust/virtual_server.rs:1034-1045 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust/perspective-js/src/rust/virtual_server.rs:944` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–6 lines × 3) rust/perspective-viewer/src/rust/ui/form/number_field.rs:52— rust/perspective-viewer/src/rust/ui/form/number_field.rs:52-54 | rust/perspective-viewer/src/rust/ui/form/number_range_field.rs:55-60 | rust/perspective-viewer/src/rust/ui/form/number_range_field.rs:65-70 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `props` to `&NumberFieldProps` in one and `&NumberRangeFieldProps` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) rust/perspective-js/src/rust/virtual_server.rs:409— rust/perspective-js/src/rust/virtual_server.rs:409-414 | rust/perspective-js/src/rust/virtual_server.rs:438-443 | rust/perspective-js/src/rust/virtual_server.rs:572-577 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `rust/perspective-js/src/rust/virtual_server.rs:578` calls `from_serde_ext`, `unwrap`, `clone` and `rust/perspective-js/src/rust/virtual_server.rs:415` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) rust/perspective-viewer/src/rust/components/window_editor.rs:796— rust/perspective-viewer/src/rust/components/window_editor.rs:796-800 | rust/perspective-viewer/src/rust/components/window_editor.rs:831-835 | rust/perspective-viewer/src/rust/components/window_editor.rs:881-885 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (29–32 lines × 2) REDACTED:436— REDACTED:436-464 | REDACTED:682-713 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:682` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplication concentrated across 8 sibling directories (46 clone groups) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67— 46 duplicated blocks under packages/viewer-charts/src/ts/charts/ have copies in at least two of the sibling directories candlestick, cartesian, common, heatmap, map, series (+2 more sibling(s) not listed) — 38 of them are reported below, and 8 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 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 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 46 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 8 sibling directories (16 clone groups) packages/viewer-charts/src/ts/axis/categorical-axis.ts:591— 16 duplicated blocks under packages/viewer-charts/src/ts/ have copies in at least two of the sibling directories axis, charts, interaction, map, theme, utils (+2 more sibling(s) not listed) — 11 of them are reported below, and 5 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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 5 sibling directories (6 clone groups) packages/viewer-charts/src/ts/theme/gradient.ts:211— 6 of the duplicated blocks reported below have copies in at least two of the sibling directories anywidget, jupyterlab, react, viewer-charts, viewer-datagrid under packages/. That concentration is one structural fact, not 6 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 6 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 (130 matched lines × 2 locations) · ×1
Duplicated block with local edits (130 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67— packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:67 · packages/viewer-charts/src/ts/charts/series/series-build.ts:134 — the two spans are one implementation copied and then locally edited — 750 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 (118 matched lines × 2 locations) · ×1
Duplicated block with local edits (118 matched lines × 2 locations) packages/viewer-charts/src/ts/theme/gradient.ts:211— packages/viewer-charts/src/ts/theme/gradient.ts:211 · REDACTED:265 — the two spans are one implementation copied and then locally edited — 879 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 (115 matched lines × 2 locations) · ×1
Duplicated block with local edits (115 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:131— packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:131 · packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-ohlc.ts:84 — the two spans are one implementation copied and then locally edited — 691 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 (110 matched lines × 2 locations) · ×1
Duplicated block with local edits (110 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts:39— packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts:39 · packages/viewer-charts/src/ts/charts/treemap/treemap.ts:32 — the two spans are one implementation copied and then locally edited — 623 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 (107 matched lines × 2 locations) · ×1
Duplicated block with local edits (107 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:64— packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:64 · packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.ts:94 — the two spans are one implementation copied and then locally edited — 620 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 (95 matched lines × 2 locations) · ×1
Duplicated block with local edits (95 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:160— packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:160 · packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:119 — the two spans are one implementation copied and then locally edited — 514 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 (85 matched lines × 2 locations) · ×1
Duplicated block with local edits (85 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:243— packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:243 · packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:293 — the two spans are one implementation copied and then locally edited — 451 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 (65 matched lines × 2 locations) · ×1
Duplicated block with local edits (65 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts:39— packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts:39 · packages/viewer-charts/src/ts/charts/cartesian/glyphs/points.ts:35 — the two spans are one implementation copied and then locally edited — 373 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 (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts:54— packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts:54 · packages/viewer-charts/src/ts/interaction/zoom-controller.ts:387 — the two spans are one implementation copied and then locally edited — 258 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 (47 lines × 2 locations) packages/viewer-charts/src/ts/axis/bar-axis.ts:224— packages/viewer-charts/src/ts/axis/bar-axis.ts:224 · packages/viewer-charts/src/ts/axis/bar-axis.ts:282 — 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.
Duplicated block (46 lines × 2 locations) packages/viewer-charts/src/ts/charts/series/series-render.ts:638— packages/viewer-charts/src/ts/charts/series/series-render.ts:638 · packages/viewer-charts/src/ts/charts/series/series-render.ts:987 — 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 (43 lines × 2 locations) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:480— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:480 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:435 — 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 (40 lines × 2 locations) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:36— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:36 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:37 — 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 (37 lines × 2 locations) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:368— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:368 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:294 — the 2 copies are spread across 2 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 (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts:188— packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts:188 · packages/viewer-charts/src/ts/charts/treemap/treemap-layout.ts:275 — the two spans are one implementation copied and then locally edited — 255 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 (33 lines × 2 locations) rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:540— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:540 · rust/perspective-js/src/ts/virtual_servers/duckdb.ts:496 — 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.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) rust/perspective-js/src/ts/perspective.node.ts:189— rust/perspective-js/src/ts/perspective.node.ts:189 · rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:102 — 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 (24 lines × 2 locations) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:516— packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:516 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:634 — 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.
Duplicated block (23 lines × 2 locations) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:169— packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:169 · packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:659 — 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) packages/viewer-charts/src/ts/axis/bar-axis.ts:347— packages/viewer-charts/src/ts/axis/bar-axis.ts:347 · packages/viewer-charts/src/ts/charts/series/series-render.ts:1099 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (21 lines × 2 locations) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:210— packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:210 · packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:201 — 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 (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:227— packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:227 · packages/viewer-charts/src/ts/charts/series/series-interact.ts:644 — the two spans are one implementation copied and then locally edited — 117 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.
Complex function buildSeriesPipeline (cyclomatic 164, cognitive 389) packages/viewer-charts/src/ts/charts/series/series-build.ts:420— buildSeriesPipeline has cyclomatic complexity 164 and cognitive complexity 389; 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 processCartesianChunk (cyclomatic 99, cognitive 186) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:297— processCartesianChunk has cyclomatic complexity 99 and cognitive complexity 186; 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 renderFacetedChromeOverlay (cyclomatic 74, cognitive 115) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:970— renderFacetedChromeOverlay has cyclomatic complexity 74 and cognitive complexity 115; 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 applyBodyCellStyles (cyclomatic 73, cognitive 109) packages/viewer-datagrid/src/ts/style_handlers/body.ts:132— applyBodyCellStyles has cyclomatic complexity 73 and cognitive complexity 109; 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 buildCandlestickPipeline (cyclomatic 68, cognitive 137) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:227— buildCandlestickPipeline has cyclomatic complexity 68 and cognitive complexity 137; 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 renderBarFrame (cyclomatic 54, cognitive 71) packages/viewer-charts/src/ts/charts/series/series-render.ts:383— renderBarFrame has cyclomatic complexity 54 and cognitive complexity 71; 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 styleColumnHeaderRow (cyclomatic 46, cognitive 34) packages/viewer-datagrid/src/ts/style_handlers/column_header.ts:95— styleColumnHeaderRow has cyclomatic complexity 46 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 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 processTreeChunk (cyclomatic 45, cognitive 78) packages/viewer-charts/src/ts/charts/common/tree-data.ts:287— processTreeChunk has cyclomatic complexity 45 and cognitive complexity 78; 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 44, cognitive 38) packages/viewer-datagrid/src/ts/style_handlers/body.ts:163— (anonymous) has cyclomatic complexity 44 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 dataListener (cyclomatic 40, cognitive 59) packages/viewer-datagrid/src/ts/data_listener/index.ts:71— dataListener has cyclomatic complexity 40 and cognitive complexity 59; 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 lastGroupBySplit (cyclomatic 39, cognitive 69) packages/viewer-charts/src/ts/data/last-group-by-split.ts:59— lastGroupBySplit has cyclomatic complexity 39 and cognitive complexity 69; 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 renderFacetedFrame (cyclomatic 36, cognitive 37) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:554— renderFacetedFrame has cyclomatic complexity 36 and cognitive complexity 37; 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 hitTestAreas (cyclomatic 34, cognitive 51) packages/viewer-charts/src/ts/charts/series/series-interact.ts:391— hitTestAreas has cyclomatic complexity 34 and cognitive complexity 51; 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 handleBarHover (cyclomatic 30, cognitive 34) packages/viewer-charts/src/ts/charts/series/series-interact.ts:66— handleBarHover 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 ensureCatExtents (cyclomatic 29, cognitive 70) packages/viewer-charts/src/ts/charts/series/series-render.ts:2007— ensureCatExtents has cyclomatic complexity 29 and cognitive complexity 70; 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 renderFacetedBarChromeOverlay (cyclomatic 29, cognitive 45) packages/viewer-charts/src/ts/charts/series/series-render.ts:1259— renderFacetedBarChromeOverlay has cyclomatic complexity 29 and cognitive complexity 45; 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 buildHeatmapPipeline (cyclomatic 28, cognitive 48) packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts:104— buildHeatmapPipeline has cyclomatic complexity 28 and cognitive complexity 48; 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 parseCssGradient (cyclomatic 28, cognitive 36) packages/viewer-charts/src/ts/theme/gradient.ts:37— parseCssGradient 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 cell_style_numeric (cyclomatic 28, cognitive 23) packages/viewer-datagrid/src/ts/style_handlers/table_cell/numeric.ts:97— cell_style_numeric has cyclomatic complexity 28 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 createModel (cyclomatic 28, cognitive 19) packages/viewer-datagrid/src/ts/model/create.ts:210— createModel has cyclomatic complexity 28 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 resolveCategoryAxis (cyclomatic 26, cognitive 43) packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:292— resolveCategoryAxis has cyclomatic complexity 26 and cognitive complexity 43; 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 column_config_schema (cyclomatic 26, cognitive 33) packages/viewer-charts/src/ts/plugin/plugin.ts:631— column_config_schema has cyclomatic complexity 26 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildFacetGrid (cyclomatic 26, cognitive 28) packages/viewer-charts/src/ts/layout/facet-grid.ts:218— buildFacetGrid has cyclomatic complexity 26 and cognitive complexity 28; 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 renderFacetedHeatmapChromeOverlay (cyclomatic 25, cognitive 37) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:719— renderFacetedHeatmapChromeOverlay has cyclomatic complexity 25 and cognitive complexity 37; 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 hitTest (cyclomatic 24, cognitive 29) packages/viewer-charts/src/ts/interaction/legend-controller.ts:522— hitTest has cyclomatic complexity 24 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 register (cyclomatic 23, cognitive 44) rust/perspective-js/src/ts/wasm/registry.ts:241— register has cyclomatic complexity 23 and cognitive complexity 44; 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 handleCandlestickHover (cyclomatic 23, cognitive 25) packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:53— handleCandlestickHover has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function uploadAndRender (cyclomatic 23, cognitive 25) packages/viewer-charts/src/ts/charts/series/series.ts:584— uploadAndRender has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderBarTooltipCanvas (cyclomatic 23, cognitive 23) packages/viewer-charts/src/ts/charts/series/series-render.ts:1685— renderBarTooltipCanvas has cyclomatic complexity 23 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderSinglePlotFrame (cyclomatic 23, cognitive 20) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:401— renderSinglePlotFrame has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderCartesianFrame (cyclomatic 22, cognitive 26) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:135— renderCartesianFrame has cyclomatic complexity 22 and cognitive complexity 26; 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 22, cognitive 26) packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:200— (anonymous) has cyclomatic complexity 22 and cognitive complexity 26; 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 renderFacetedBarFrame (cyclomatic 22, cognitive 24) packages/viewer-charts/src/ts/charts/series/series-render.ts:906— renderFacetedBarFrame has cyclomatic complexity 22 and cognitive complexity 24; 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 buildCustomElementsManifest (cyclomatic 21, cognitive 42) rust/perspective-viewer/tools.mjs:1323— buildCustomElementsManifest has cyclomatic complexity 21 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 hitTest (cyclomatic 21, cognitive 40) packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts:40— hitTest has cyclomatic complexity 21 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 rebuildBuffers (cyclomatic 21, cognitive 39) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts:128— rebuildBuffers has cyclomatic complexity 21 and cognitive complexity 39; 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 _handleRendererMsg (cyclomatic 21, cognitive 16) packages/viewer-charts/src/ts/transport/renderer-transport.ts:733— _handleRendererMsg has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cemMembers (cyclomatic 20, cognitive 40) rust/perspective-viewer/tools.mjs:1041— cemMembers has cyclomatic complexity 20 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 uploadBarInstances (cyclomatic 20, cognitive 33) packages/viewer-charts/src/ts/charts/series/series-render.ts:129— uploadBarInstances has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderScatterLabels (cyclomatic 20, cognitive 21) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1284— renderScatterLabels has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/viewer-charts/src/ts/charts/series/series-render.ts · ×1
packages/viewer-charts/src/ts/charts/series/series-render.ts: 1964 lines of code packages/viewer-charts/src/ts/charts/series/series-render.ts:1— packages/viewer-charts/src/ts/charts/series/series-render.ts has 1964 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· packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts · ×1
packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts: 1349 lines of code packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts:1— packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts has 1349 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· rust/perspective-viewer/tools.mjs · ×1
rust/perspective-viewer/tools.mjs: 1313 lines of code rust/perspective-viewer/tools.mjs:1— rust/perspective-viewer/tools.mjs has 1313 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· packages/viewer-charts/src/ts/charts/series/series-build.ts · ×1
packages/viewer-charts/src/ts/charts/series/series-build.ts: 1158 lines of code packages/viewer-charts/src/ts/charts/series/series-build.ts:1— packages/viewer-charts/src/ts/charts/series/series-build.ts has 1158 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· packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts · ×1
packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts: 1124 lines of code packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts:1— packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts has 1124 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· packages/viewer-charts/src/ts/charts/series/series.ts · ×1
packages/viewer-charts/src/ts/charts/series/series.ts: 964 lines of code packages/viewer-charts/src/ts/charts/series/series.ts:1— packages/viewer-charts/src/ts/charts/series/series.ts has 964 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· packages/viewer-charts/src/ts/interaction/legend-controller.ts · ×1
packages/viewer-charts/src/ts/interaction/legend-controller.ts: 951 lines of code packages/viewer-charts/src/ts/interaction/legend-controller.ts:1— packages/viewer-charts/src/ts/interaction/legend-controller.ts has 951 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· packages/viewer-charts/src/ts/charts/chart-base.ts · ×1
packages/viewer-charts/src/ts/charts/chart-base.ts: 924 lines of code packages/viewer-charts/src/ts/charts/chart-base.ts:1— packages/viewer-charts/src/ts/charts/chart-base.ts has 924 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· packages/viewer-charts/src/ts/plugin/plugin.ts · ×1
packages/viewer-charts/src/ts/plugin/plugin.ts: 917 lines of code packages/viewer-charts/src/ts/plugin/plugin.ts:1— packages/viewer-charts/src/ts/plugin/plugin.ts has 917 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· packages/viewer-charts/src/ts/transport/renderer-transport.ts · ×1
packages/viewer-charts/src/ts/transport/renderer-transport.ts: 873 lines of code packages/viewer-charts/src/ts/transport/renderer-transport.ts:1— packages/viewer-charts/src/ts/transport/renderer-transport.ts has 873 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· packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts · ×1
packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts: 818 lines of code packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts:1— packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts has 818 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· packages/viewer-charts/src/ts/worker/renderer.worker.ts · ×1
packages/viewer-charts/src/ts/worker/renderer.worker.ts: 791 lines of code packages/viewer-charts/src/ts/worker/renderer.worker.ts:1— packages/viewer-charts/src/ts/worker/renderer.worker.ts has 791 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· packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts · ×1
packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts: 774 lines of code packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts:1— packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts has 774 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· packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts · ×1
packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts: 759 lines of code packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:1— packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts has 759 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· packages/viewer-charts/src/ts/charts/series/series-interact.ts · ×1
packages/viewer-charts/src/ts/charts/series/series-interact.ts: 672 lines of code packages/viewer-charts/src/ts/charts/series/series-interact.ts:1— packages/viewer-charts/src/ts/charts/series/series-interact.ts has 672 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· packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts · ×1
packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts: 671 lines of code packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts:1— packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts has 671 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· packages/viewer-charts/src/ts/axis/categorical-axis.ts · ×1
packages/viewer-charts/src/ts/axis/categorical-axis.ts: 661 lines of code packages/viewer-charts/src/ts/axis/categorical-axis.ts:1— packages/viewer-charts/src/ts/axis/categorical-axis.ts has 661 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· packages/viewer-charts/src/ts/charts/common/tree-data.ts · ×1
packages/viewer-charts/src/ts/charts/common/tree-data.ts: 604 lines of code packages/viewer-charts/src/ts/charts/common/tree-data.ts:1— packages/viewer-charts/src/ts/charts/common/tree-data.ts has 604 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· packages/viewer-datagrid/src/ts/types.ts · ×1
packages/viewer-datagrid/src/ts/types.ts: 580 lines of code packages/viewer-datagrid/src/ts/types.ts:1— packages/viewer-datagrid/src/ts/types.ts has 580 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· rust/perspective-js/src/ts/perspective.node.ts · ×1
rust/perspective-js/src/ts/perspective.node.ts: 570 lines of code rust/perspective-js/src/ts/perspective.node.ts:1— rust/perspective-js/src/ts/perspective.node.ts has 570 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· rust/perspective-js/src/ts/virtual_servers/clickhouse.ts · ×1
rust/perspective-js/src/ts/virtual_servers/clickhouse.ts: 556 lines of code rust/perspective-js/src/ts/virtual_servers/clickhouse.ts:1— rust/perspective-js/src/ts/virtual_servers/clickhouse.ts has 556 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· packages/viewer-charts/src/ts/charts/chart.ts · ×1
packages/viewer-charts/src/ts/charts/chart.ts: 532 lines of code packages/viewer-charts/src/ts/charts/chart.ts:1— packages/viewer-charts/src/ts/charts/chart.ts has 532 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· rust/perspective-js/src/ts/virtual_servers/duckdb.ts · ×1
rust/perspective-js/src/ts/virtual_servers/duckdb.ts: 532 lines of code rust/perspective-js/src/ts/virtual_servers/duckdb.ts:1— rust/perspective-js/src/ts/virtual_servers/duckdb.ts has 532 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· packages/viewer-charts/src/ts/theme/gradient.ts · ×1
packages/viewer-charts/src/ts/theme/gradient.ts: 499 lines of code packages/viewer-charts/src/ts/theme/gradient.ts:1— packages/viewer-charts/src/ts/theme/gradient.ts has 499 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· packages/viewer-charts/src/ts/axis/legend.ts · ×1
packages/viewer-charts/src/ts/axis/legend.ts: 496 lines of code packages/viewer-charts/src/ts/axis/legend.ts:1— packages/viewer-charts/src/ts/axis/legend.ts has 496 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· rust/perspective-js/src/ts/wasm/registry.ts · ×1
rust/perspective-js/src/ts/wasm/registry.ts: 490 lines of code rust/perspective-js/src/ts/wasm/registry.ts:1— rust/perspective-js/src/ts/wasm/registry.ts has 490 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· packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts · ×1
packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts: 478 lines of code packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts:1— packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts has 478 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· packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts · ×1
packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts: 475 lines of code packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:1— packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts has 475 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· packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts · ×1
packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts: 475 lines of code packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts:1— packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts has 475 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· packages/viewer-charts/src/ts/interaction/zoom-controller.ts · ×1
packages/viewer-charts/src/ts/interaction/zoom-controller.ts: 454 lines of code packages/viewer-charts/src/ts/interaction/zoom-controller.ts:1— packages/viewer-charts/src/ts/interaction/zoom-controller.ts has 454 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· rust/perspective-js/src/ts/wasm/perspective-server.poly.ts · ×1
rust/perspective-js/src/ts/wasm/perspective-server.poly.ts: 426 lines of code rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:1— rust/perspective-js/src/ts/wasm/perspective-server.poly.ts has 426 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· packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts · ×1
packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts: 423 lines of code packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:1— packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 420 lines of code REDACTED:1— REDACTED has 420 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· packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts · ×1
packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts: 418 lines of code packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts:1— packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts has 418 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· packages/viewer-datagrid/src/ts/style_handlers/body.ts · ×1
packages/viewer-datagrid/src/ts/style_handlers/body.ts: 418 lines of code packages/viewer-datagrid/src/ts/style_handlers/body.ts:1— packages/viewer-datagrid/src/ts/style_handlers/body.ts has 418 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· packages/viewer-datagrid/src/ts/event_handlers/select_region.ts · ×1
packages/viewer-datagrid/src/ts/event_handlers/select_region.ts: 416 lines of code packages/viewer-datagrid/src/ts/event_handlers/select_region.ts:1— packages/viewer-datagrid/src/ts/event_handlers/select_region.ts has 416 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· packages/viewer-charts/src/ts/render/scheduler.ts · ×1
packages/viewer-charts/src/ts/render/scheduler.ts: 411 lines of code packages/viewer-charts/src/ts/render/scheduler.ts:1— packages/viewer-charts/src/ts/render/scheduler.ts has 411 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· packages/viewer-charts/src/ts/plugin/charts.ts · ×1
packages/viewer-charts/src/ts/plugin/charts.ts: 402 lines of code packages/viewer-charts/src/ts/plugin/charts.ts:1— packages/viewer-charts/src/ts/plugin/charts.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~2144 LoC) packages/viewer-charts/src/ts/charts/series/series-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series-interact.ts, packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1453 LoC) packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1273 LoC) packages/viewer-charts/src/ts/charts/series/series-build.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-bars.ts, packages/viewer-charts/src/ts/charts/series/series-interact.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1258 LoC) packages/viewer-charts/src/ts/charts/cartesian/glyphs/density.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts, packages/viewer-charts/src/ts/charts/map/map.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1084 LoC) packages/viewer-charts/src/ts/interaction/legend-controller.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (packages/viewer-charts/src/ts/axis/legend.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts, packages/viewer-charts/src/ts/charts/chart-base.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1064 LoC) packages/viewer-charts/src/ts/charts/series/series.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/viewer-charts/src/ts/charts/registry.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-bars.ts and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1020 LoC) packages/viewer-charts/src/ts/charts/chart-base.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts, packages/viewer-charts/src/ts/charts/common/categorical-y-chart.ts, packages/viewer-charts/src/ts/charts/common/tree-chart.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~1007 LoC) packages/viewer-charts/src/ts/plugin/plugin.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~971 LoC) packages/viewer-charts/src/ts/transport/renderer-transport.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/plugin/plugin.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~898 LoC) packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~890 LoC) packages/viewer-charts/src/ts/worker/renderer.worker.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-charts/src/ts/transport/renderer-transport.ts, packages/viewer-charts/src/ts/worker/dispatch.ts, packages/viewer-charts/src/ts/worker/session-host.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~872 LoC) packages/viewer-charts/src/ts/charts/treemap/treemap-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/treemap/treemap-interact.ts, packages/viewer-charts/src/ts/charts/treemap/treemap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~839 LoC) packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~757 LoC) packages/viewer-charts/src/ts/axis/categorical-axis.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 15 in-repo import(s) from 15 other file(s) do name it (packages/viewer-charts/src/ts/axis/bar-axis.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts and 12 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~753 LoC) packages/viewer-charts/src/ts/charts/series/series-interact.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series-render.ts, packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~750 LoC) packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~675 LoC) packages/viewer-charts/src/ts/charts/common/tree-data.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-charts/src/ts/charts/common/tree-interact.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-layout.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~572 LoC) packages/viewer-charts/src/ts/transport/protocol.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (packages/viewer-charts/src/ts/interaction/host-sink-message.ts, packages/viewer-charts/src/ts/interaction/legend-controller.ts, packages/viewer-charts/src/ts/interaction/raw-event-forwarder.ts and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~545 LoC) packages/viewer-charts/src/ts/axis/legend.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts, packages/viewer-charts/src/ts/charts/common/tree-chrome.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap-render.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~541 LoC) packages/viewer-charts/src/ts/charts/common/category-axis-resolver.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/common/tree-data.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~526 LoC) packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~523 LoC) packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 10 in-repo import(s) from 10 other file(s) do name it (packages/viewer-charts/src/ts/charts/cartesian/cartesian-build.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts and 7 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~470 LoC) packages/viewer-datagrid/src/ts/style_handlers/body.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~469 LoC) packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~466 LoC) packages/viewer-charts/src/ts/charts/candlestick/glyphs/draw-candlesticks.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/candlestick/candlestick.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~461 LoC) packages/viewer-datagrid/src/ts/event_handlers/select_region.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-datagrid/src/ts/plugin/activate.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~446 LoC) packages/viewer-charts/src/ts/render/scheduler.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/chart-base.ts, packages/viewer-charts/src/ts/worker/renderer.worker.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~444 LoC) packages/viewer-charts/src/ts/charts/heatmap/heatmap-build.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~415 LoC) packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~393 LoC) packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~388 LoC) packages/jupyterlab/src/js/renderer.js— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/jupyterlab/src/js/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~387 LoC) packages/viewer-charts/src/ts/map/tile-layer.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/map/map.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~386 LoC) packages/viewer-datagrid/src/ts/model/create.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/viewer-datagrid/src/ts/model/index.ts, packages/viewer-datagrid/src/ts/plugin/activate.ts, packages/viewer-datagrid/src/ts/plugin/column_config_schema.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~380 LoC) packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts— no import path from any entry point (47 application, 5 tooling, 297 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/viewer-charts/src/ts/charts/series/series.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: extract rust/perspective-js/src/ts/wasm/decompress.ts:19— `extract` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/clickhouse.py:344— `debug` at line 344 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/clickhouse.py:395— `error` at line 395 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/clickhouse.py:398— `debug` at line 398 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/duckdb.py:378— `warning` at line 378 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/duckdb.py:402— `error` at line 402 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/duckdb.py:405— `debug` at line 405 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging REDACTED:197— `debug` at line 197 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/postgres.py:430— `warning` at line 430 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/postgres.py:468— `error` at line 468 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-python/perspective/virtual_servers/postgres.py:471— `debug` at line 471 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/renderer.rs:784— `warn!` at line 784 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/session.rs:1095— `error!` at line 1095 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/session.rs:1624— `debug!` at line 1624 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/utils/spawn.rs:28— `error!` at line 28 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/ui/portal.rs:116— `warn!` at line 116 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/ui/containers/scroll_panel_item.rs:88— `warn!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/restore_derived.rs:97— `warn!` at line 97 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/restore_derived.rs:104— `warn!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/restore_panel.rs:233— `info!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:83— `warn!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:165— `warn!` at line 165 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/sync_update_panels.rs:228— `warn!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/tasks/table_lifecycle.rs:90— `warn!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/session/column_defaults_update.rs:56— `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging rust/perspective-viewer/src/rust/session/column_defaults_update.rs:74— `debug!` at line 74 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate rust/perspective-js/build.mjs:22— `!!process.env.PSP_DEBUG || process.argv.indexOf("--debug") >= 0` appears character-identically in 2 files — rust/perspective-js/build.mjs, rust/perspective-viewer/build.mjs. 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 packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:207— `!buf || !cache || buf.series.length === 0` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:320— `!chart._chromeCanvas || !chart._lastLayout` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts, packages/viewer-charts/src/ts/charts/series/series-render.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:254— `!chart._chromeCanvas || !chart._lastLayout || !chart._lastYDomain || !chart._lastYTicks` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts, packages/viewer-charts/src/ts/charts/series/series-render.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 packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts:520— `!chart._chromeCanvas || chart._currentRootId === NULL_NODE` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-render.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 packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts:196— `!chart._visibleNodeIds || chart._visibleNodeIds.length < store.count` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/sunburst/sunburst-layout.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-layout.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 tools/scripts/build.mjs:19— `!fs.existsSync("./.perspectiverc") && !process.env.PACKAGE` appears character-identically in 2 files — tools/scripts/build.mjs, tools/scripts/test.mjs. 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 packages/viewer-charts/src/ts/plugin/plugin.ts:905— `!this.isConnected || this.offsetParent == null` appears character-identically in 2 files — packages/viewer-charts/src/ts/plugin/plugin.ts, packages/viewer-datagrid/src/ts/custom_elements/datagrid.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 packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts:229— `aggRange !== undefined && (aggIdx < aggRange.start || aggIdx > aggRange.end)` appears character-identically in 3 files — packages/viewer-charts/src/ts/charts/series/glyphs/draw-areas.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-lines.ts, packages/viewer-charts/src/ts/charts/series/glyphs/draw-scatter.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts:328— `axisMode.numericType === "date" || axisMode.numericType === "datetime"` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-build.ts, packages/viewer-charts/src/ts/charts/series/series-build.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:240— `chart._categoryAxisMode === "numeric" && chart._numericCategoryDomain && chart._categoryPositions` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts, packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts:265— `chart._categoryAxisMode === "numeric" && chart._numericCategoryDomain && chart._lastCatTicks` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-render.ts, packages/viewer-charts/src/ts/charts/series/series-render.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 packages/viewer-charts/src/ts/charts/common/tree-chrome.ts:176— `chart._colorMode === "numeric" && chart._colorMin < chart._colorMax` appears character-identically in 3 files — packages/viewer-charts/src/ts/charts/common/tree-chrome.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-render.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 packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts:171— `chart._colorName && !chart._colorIsString` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/cartesian/glyphs/lines.ts, packages/viewer-charts/src/ts/charts/cartesian/glyphs/points.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 packages/viewer-charts/src/ts/charts/common/tree-interact.ts:46— `chart._splitBy.length > 0 && chart._facetConfig.facet_mode === "grid"` appears character-identically in 3 files — packages/viewer-charts/src/ts/charts/common/tree-interact.ts, packages/viewer-charts/src/ts/charts/sunburst/sunburst-render.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-render.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 packages/viewer-charts/src/ts/theme/gradient.ts:282— `i === 0 && (lower.startsWith("to ") || /^[-\d.]+(deg|rad|grad|turn)$/.test(lower))` appears character-identically in 2 files — packages/viewer-charts/src/ts/theme/gradient.ts, REDACTED. 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 docs/build.seo.mjs:178— `isFeature(project) && project.description` appears character-identically in 2 files — docs/build.seo.mjs, docs/src/data/projects/types.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 packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts:86— `mx < plot.x || mx > plot.x + plot.width || my < plot.y || my > plot.y + plot.height` appears character-identically in 5 files — packages/viewer-charts/src/ts/charts/candlestick/candlestick-interact.ts, packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts, packages/viewer-charts/src/ts/charts/series/series-interact.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 packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts:184— `mx >= plot.x && mx <= plot.x + plot.width && my >= plot.y && my <= plot.y + plot.height` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts, packages/viewer-charts/src/ts/worker/renderer.worker.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 packages/viewer-charts/src/ts/charts/series/series-interact.ts:568— `mx >= r.x && mx <= r.x + r.width && my >= r.y && my <= r.y + r.height` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/series/series-interact.ts, packages/viewer-charts/src/ts/interaction/legend-controller.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 packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts:175— `mx >= region.x0 && mx <= region.x1 && my >= region.y0 && my <= region.y1` appears character-identically in 2 files — packages/viewer-charts/src/ts/charts/sunburst/sunburst-interact.ts, packages/viewer-charts/src/ts/charts/treemap/treemap-interact.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 rust/perspective-python/build.mjs:73— `process.env.PSP_ARCH === "aarch64" && process.platform === "darwin"` appears character-identically in 3 files — rust/perspective-python/build.mjs, rust/perspective/build.mjs, tools/scripts/test_js.mjs. 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 rust/perspective-python/build.mjs:79— `process.env.PSP_ARCH === "aarch64" && process.platform === "linux"` appears character-identically in 3 files — rust/perspective-python/build.mjs, rust/perspective/build.mjs, tools/scripts/test_js.mjs. 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 rust/perspective-python/build.mjs:70— `process.env.PSP_ARCH === "x86_64" && process.platform === "darwin"` appears character-identically in 3 files — rust/perspective-python/build.mjs, rust/perspective/build.mjs, tools/scripts/test_js.mjs. 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 rust/perspective-python/build.mjs:77— `process.env.PSP_ARCH === "x86_64" && process.platform === "linux"` appears character-identically in 3 files — rust/perspective-python/build.mjs, rust/perspective/build.mjs, tools/scripts/test_js.mjs. 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.
Orphaned file packages/viewer-charts/src/ts/webgl/shader-registry.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 packages/viewer-charts/src/ts/interaction/spatial-grid.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 rust/perspective-viewer/src/rust/components/style_controls/number_string_format/style_section.rs: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 rust/perspective-python/src/client/proxy_session.rs: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 rust/perspective-client/src/rust/table_data.rs: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 rust/perspective-viewer/src/rust/ui/form/number_field.rs: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 rust/perspective-viewer/src/rust/components/column_settings_sidebar/attributes_tab.rs: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 packages/react/src/utils.tsx: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 rust/perspective-viewer/src/rust/config/kvpair.rs: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 rust/perspective-viewer/src/rust/ui/containers/sidebar_close_button.rs: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.
redundant comment packages/viewer-datagrid/src/ts/plugin/activate.ts:244— "viewer event listeners" repeats the code it sits on: 3 of its 3 words (viewer, event, listeners) are already in `viewer.addEventListener(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/viewer-datagrid/src/ts/style_handlers/consolidated.ts:52— "Toggle edit mode class on datagrid" repeats the code it sits on: 5 of its 5 words (toggle, edit, mode, class, datagrid) are already in `datagrid.classList.toggle("edit-mode-allowed", isEditableAllowed);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/viewer-datagrid/src/ts/types.ts:580— "Toolbar element interface" repeats the code it sits on: 3 of its 3 words (toolbar, element, interface) are already in `export interface DatagridToolbarElement extends HTMLElement`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/viewer-datagrid/src/ts/types.ts:625— "Datagrid plugin element interface for toolbar" repeats the code it sits on: 4 of its 5 words (datagrid, plugin, element, interface) are already in `export interface DatagridPluginElement extends HTMLElement`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default in catch packages/jupyterlab/test/jupyter/utils.mjs:180— `execute_all_cells` swallows every exception into `return false` — 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.
Silent fallback default in catch rust/perspective-js/src/ts/wasm/perspective-server.poly.ts:146— `default.makeOpfsBridge.load` swallows every exception into `return 0` — 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.
Silent fallback default in catch rust/perspective-js/src/ts/perspective.node.ts:227— `make_node_disk_bridge.load` swallows every exception into `return 0` — 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 273 significant file(s) lose their only recent owner: rust/perspective-viewer/src/rust/custom_elements/viewer.rs, packages/viewer-charts/src/ts/charts/series/series-render.ts, rust/perspective-client/src/rust/virtual_server/generic_sql_model/tests.rs, rust/perspective-viewer/src/rust/session.rs, rust/perspective-viewer/src/rust/agent/tools.rs, rust/perspective-client/src/rust/virtual_server/data.rs, rust/perspective-python/src/client/client_async.rs, packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts (+265 more). Pair on, review, or document these before any departure.
No ADRs found package.json:74— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `package.json` makes this repository a deployable product (line 74).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 17 project(s) overshoot their size bounds, lowering Project Cohesion to 6.9/10. The most over is `rust/perspective-viewer` (51036 LoC, 569 module-visible types across 36 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.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 10 of 544 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 544 of the 574 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/viewer-charts/src/ts/webgl/shader-registry.ts, packages/viewer-charts/src/ts/interaction/spatial-grid.ts, rust/perspective-viewer/src/rust/components/style_controls/number_string_format/style_section.rs, rust/perspective-python/src/client/proxy_session.rs, rust/perspective-client/src/rust/table_data.rs, rust/perspective-viewer/src/rust/ui/form/number_field.rs, rust/perspective-viewer/src/rust/components/column_settings_sidebar/attributes_tab.rs, packages/react/src/utils.tsx (and 2 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
Logging is not universal — Only 7/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cli`, `rust/bundle`, `rust/lint`, `rust/metadata`, `rust/perspective-js`.
No SAST REDACTED:30— No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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 dependency-update automation package.json:39— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
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 — 14/15 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 (`!`) override strict null checking — ~6.3 `!` null assertions per 1k TypeScript source lines — 348 assertion(s) across the 54875 source line(s) of the 198 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: packages/viewer-datagrid/src/ts/event_handlers/select_region.ts (64), packages/viewer-charts/src/ts/charts/series/series-render.ts (28), packages/viewer-charts/src/ts/charts/cartesian/cartesian-render.ts (26). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default on Err rust/perspective-viewer/src/rust/ui/form/palette_selector.rs:89— `swatch_centers` turns every `Err` into `vec![]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Outdated: anyhow — `anyhow` is locked at 1.0.100 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0.66"` requirement declared in rust/perspective-viewer/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: axum — `axum` is locked at 0.8.7 but 0.8.9 is the current stable release on crates.io, and it already satisfies the `">=0.8,<0.9"` requirement declared in examples/rust-axum/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p axum` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.11.0 but 1.12.1 is the current stable release on crates.io, and it already satisfies the `"1.10.1"` requirement declared in rust/perspective-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.42 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in rust/perspective-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.5.53 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.4.8"` requirement declared in rust/bundle/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.33 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in examples/rust-axum/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: getrandom — `getrandom` is locked at 0.3.4 but 0.4.3 is the current stable release on crates.io, and it already satisfies the `"0"` requirement declared in rust/perspective-client/Cargo.toml — so the lockfile is behind this repository's own declared range. This crosses a compatibility boundary. Run `cargo update -p getrandom` and commit the updated REDACTED.
Outdated: glob — `glob` is locked at 0.3.3 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3.0"` requirement declared in rust/perspective-viewer/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.14.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2.2.6"` requirement declared in rust/perspective-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: js-sys — `js-sys` is locked at 0.3.85 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.85"` requirement declared in rust/perspective-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p js-sys` and commit the updated REDACTED.
Outdated: macro_rules_attribute — `macro_rules_attribute` is locked at 0.2.2 but 0.2.3 is the current stable release on crates.io, and it already satisfies the `"0.2.2"` requirement declared in rust/perspective-python/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p macro_rules_attribute` and commit the updated REDACTED.
Outdated: rand — `rand` is locked at 0.9.1 but 0.10.3 is the current stable release on crates.io, and it already satisfies the `">=0.9,<1"` requirement declared in rust/perspective-client/Cargo.toml — so the lockfile is behind this repository's own declared range. This crosses a compatibility boundary. Run `cargo update -p rand` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in rust/perspective-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.107"` requirement declared in rust/perspective-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.52.3 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in examples/rust-axum/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: tracing-subscriber — `tracing-subscriber` is locked at 0.3.22 but 0.3.23 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in examples/rust-axum/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tracing-subscriber` and commit the updated REDACTED.
Outdated: wasm-bindgen-cli-support — `wasm-bindgen-cli-support` is locked at 0.2.108 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"*"` requirement declared in rust/bundle/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-cli-support` and commit the updated REDACTED.
Outdated: wasm-bindgen-futures — `wasm-bindgen-futures` is locked at 0.4.58 but 0.4.80 is the current stable release on crates.io, and it already satisfies the `"0.4.41"` requirement declared in rust/perspective-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-futures` and commit the updated REDACTED.
Outdated: web-sys — `web-sys` is locked at 0.3.85 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.85"` requirement declared in rust/perspective-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p web-sys` and commit the updated REDACTED.
Skipped (documented): (unnamed test) rust/perspective-js/test/js/leaks.spec.js:35— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) rust/perspective-js/test/js/leaks.spec.js:36— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) rust/perspective-js/test/js/leaks.spec.js:46— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
doc comments repeat the names rust/perspective-js/src/ts/perspective.node.ts:527— 0 of 13 documented parameters and 0 of 62 summaries in `@perspective-dev/client` only repeat the member or parameter name (e.g. "" for `on`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/viewer-charts/src/ts/charts/chart-base.ts:227— 0 of 6 documented parameters and 1 of 905 summaries in `@perspective-dev/viewer-charts` only repeat the member or parameter name (e.g. "Per-column value formatters for those same columns." for `_columnValueFormatters`). Delete the restating tags, or add what the name does not say.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 15 file(s) — `packages/viewer-charts/src/ts/charts/cartesian/cartesian-interact.ts`, `packages/viewer-charts/src/ts/charts/cartesian/cartesian.ts`, `packages/viewer-charts/src/ts/charts/chart-base.ts`, `packages/viewer-charts/src/ts/charts/heatmap/heatmap-interact.ts`, `packages/viewer-charts/src/ts/charts/heatmap/heatmap.ts`, … (+10 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1dad3-b388-7647-99d0-11ffb5298ee7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 135 · Warnings: 1117 · Recommendations: 119 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 16:11 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.