Public report of apache/texera, published 7 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.2). 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, 7 November 2026, 02:20 UTC · Survey ID cd_cc65a81b26f14933a275152b32761395
apache/texera
Measured 7 November 2026, 02:19 UTC, at code version d6c9050
CAI scoreAt riskNo change 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: 170,095 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 2.5 person-years · Weakest lens: Production Readiness, 25
Findings by how serious they are
318 critical753 serious360 minor
13 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
7 November 2026, 02:19 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 ▸
87of 87 dimensions measured by tools.
1396of 1431 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
87dimensions across 7 lenses, read from 170,095 lines of product code in 22 projects.
apache/texera is rated At risk because critical security findings are open. Its score is held back in part because seven passwords or keys sit in the current code. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 25, is the weakest lens and counts most in the score. The best first step is replacing the seven exposed passwords or keys and switching the old ones off, worth about 13 points. Documenting the recovery plan comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 52.
Eighty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixty-one known security holes in the packages the code depends on can be used by attackers, and thirty passwords or keys in the code's history and seven in the code are open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing each exposed password or key would close these risks. Passing outside input through environment variables would fix the 14 pipeline steps that put outside input straight into a shell command, and fixing the weaknesses the scanner points to would deal with the 12 security weaknesses in the code. The 31 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 170,095 lines, about €370,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
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 Production Readiness rose from 25 to 70, the lowest score rated Strong, the score would rise from 40 to about 52.
Code composition: what the lines of code are
Product code 39%Tests 61%
New since the last survey: 177 findings
These 177 critical or serious findings weren't in the previous survey, on 21 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 363 findings
These 363 critical or serious findings were in the previous survey, on 21 October 2026, and are gone from this one. The first 100 are listed here.
€120,000 to €610,000, for 2,037 to 6,461 hours of work, about 2.5 person-years for 1 to 5 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 40. 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: 170,095 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
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Raises the score by about 13 points · Low effort · REDACTED Scanning
2
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Raises the score by about 4 points · Medium effort · DR & Backup
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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 €370,000 to build again, about 2.5 person-years of work. Its weakest lens is Production Readiness, at 25 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 13 points for low effort, because it clears the 7 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
743 modules, with 1554 dependencies between them. 6 loops run through 38 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 703 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.
agent-service.src.api.workflow-api uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break agent-service.src.api.workflow-api, while a change to agent-service.src.api.workflow-api can't break agent-service.src.types.workflow.
Position
Below the diagonal: agent-service.src.api.workflow-api uses a module listed above it, which is the healthy direction.
frontend.src.app.common.type.user uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.common.type.user, while a change to frontend.src.app.common.type.user can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.common.type.user uses a module listed above it, which is the healthy direction.
frontend.src.app.dashboard.type.dashboard-entry uses frontend.src.app.hub.service.hub_service, so a change to frontend.src.app.hub.service.hub_service can break frontend.src.app.dashboard.type.dashboard-entry, while a change to frontend.src.app.dashboard.type.dashboard-entry can't break frontend.src.app.hub.service.hub_service.
Position
Below the diagonal: frontend.src.app.dashboard.type.dashboard-entry uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.workflow-result.workflow-result_service uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.service.workflow-result.workflow-result_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.service.workflow-result.workflow-result_service, while a change to frontend.src.app.workspace.service.workflow-result.workflow-result_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.service.workflow-result.workflow-result_service uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.core.executor uses org.apache.texera.amber.core.tuple, so a change to org.apache.texera.amber.core.tuple can break org.apache.texera.amber.core.executor, while a change to org.apache.texera.amber.core.executor can't break org.apache.texera.amber.core.tuple.
Position
Below the diagonal: org.apache.texera.amber.core.executor uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.core.workflow uses org.apache.texera.amber.core.tuple, so a change to org.apache.texera.amber.core.tuple can break org.apache.texera.amber.core.workflow, while a change to org.apache.texera.amber.core.workflow can't break org.apache.texera.amber.core.tuple.
Position
Below the diagonal: org.apache.texera.amber.core.workflow uses a module listed above it, which is the healthy direction.
frontend.src.app.common.service.user.user_service uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.common.service.user.user_service, while a change to frontend.src.app.common.service.user.user_service can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.common.service.user.user_service uses a module listed above it, which is the healthy direction.
frontend.src.app.common.service.user.user_service uses frontend.src.app.common.type.user, so a change to frontend.src.app.common.type.user can break frontend.src.app.common.service.user.user_service, while a change to frontend.src.app.common.service.user.user_service can't break frontend.src.app.common.type.user.
Position
Below the diagonal: frontend.src.app.common.service.user.user_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a type in agent-service.src.types.workflow.
frontend.src.app.common.service.workflow-persist.workflow-persist_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.common.service.workflow-persist.workflow-persist_service, while a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.common.service.workflow-persist.workflow-persist_service uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.common.service.workflow-persist.workflow-persist_service, while a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a type in agent-service.src.api.workflow-api.
frontend.src.app.common.service.workflow-persist.workflow-persist_service uses agent-service.src.api.workflow-api, so a change to agent-service.src.api.workflow-api can break frontend.src.app.common.service.workflow-persist.workflow-persist_service, while a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can't break agent-service.src.api.workflow-api.
Position
Below the diagonal: frontend.src.app.common.service.workflow-persist.workflow-persist_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.dataset.dataset_service uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.dashboard.service.user.dataset.dataset_service uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.dashboard.service.user.dataset.dataset_service, while a change to frontend.src.app.dashboard.service.user.dataset.dataset_service can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.dataset.dataset_service uses a module listed above it, which is the healthy direction.
frontend.src.app.dashboard.service.user.dataset.dataset_service uses frontend.src.app.common.type.user, so a change to frontend.src.app.common.type.user can break frontend.src.app.dashboard.service.user.dataset.dataset_service, while a change to frontend.src.app.dashboard.service.user.dataset.dataset_service can't break frontend.src.app.common.type.user.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.dataset.dataset_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses a type in frontend.src.app.hub.service.hub_service.
frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses frontend.src.app.hub.service.hub_service, so a change to frontend.src.app.hub.service.hub_service can break frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service, while a change to frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service can't break frontend.src.app.hub.service.hub_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses a type in frontend.src.app.dashboard.type.dashboard-entry.
frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses frontend.src.app.dashboard.type.dashboard-entry, so a change to frontend.src.app.dashboard.type.dashboard-entry can break frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service, while a change to frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service can't break frontend.src.app.dashboard.type.dashboard-entry.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.resource-registry.resource-registry_service uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, while a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, while a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a type in agent-service.src.api.workflow-api.
frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses agent-service.src.api.workflow-api, so a change to agent-service.src.api.workflow-api can break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, while a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can't break agent-service.src.api.workflow-api.
Position
Below the diagonal: frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a type in frontend.src.app.common.type.user.
frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses frontend.src.app.common.type.user, so a change to frontend.src.app.common.type.user can break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, while a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can't break frontend.src.app.common.type.user.
Position
Below the diagonal: frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.engine.architecture.common uses org.apache.texera.amber.core.workflow, so a change to org.apache.texera.amber.core.workflow can break org.apache.texera.amber.engine.architecture.common, while a change to org.apache.texera.amber.engine.architecture.common can't break org.apache.texera.amber.core.workflow.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.common uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.operator uses org.apache.texera.amber.core.tuple, so a change to org.apache.texera.amber.core.tuple can break org.apache.texera.amber.operator, while a change to org.apache.texera.amber.operator can't break org.apache.texera.amber.core.tuple.
Position
Below the diagonal: org.apache.texera.amber.operator uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.operator uses org.apache.texera.amber.operator.metadata, so a change to org.apache.texera.amber.operator.metadata can break org.apache.texera.amber.operator, while a change to org.apache.texera.amber.operator can't break org.apache.texera.amber.operator.metadata.
Position
Below the diagonal: org.apache.texera.amber.operator uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.operator uses org.apache.texera.amber.core.workflow, so a change to org.apache.texera.amber.core.workflow can break org.apache.texera.amber.operator, while a change to org.apache.texera.amber.operator can't break org.apache.texera.amber.core.workflow.
Position
Below the diagonal: org.apache.texera.amber.operator uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service uses a type in frontend.src.app.common.service.user.user_service.
frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service uses frontend.src.app.common.service.user.user_service, so a change to frontend.src.app.common.service.user.user_service can break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, while a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can't break frontend.src.app.common.service.user.user_service.
Position
Below the diagonal: frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.download.download_service uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.dashboard.service.user.download.download_service uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.dashboard.service.user.download.download_service, while a change to frontend.src.app.dashboard.service.user.download.download_service can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.download.download_service uses a module listed above it, which is the healthy direction.
frontend.src.app.dashboard.service.user.download.download_service uses agent-service.src.api.workflow-api, so a change to agent-service.src.api.workflow-api can break frontend.src.app.dashboard.service.user.download.download_service, while a change to frontend.src.app.dashboard.service.user.download.download_service can't break agent-service.src.api.workflow-api.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.download.download_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.download.download_service uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.dashboard.service.user.download.download_service uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.dashboard.service.user.download.download_service, while a change to frontend.src.app.dashboard.service.user.download.download_service can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.download.download_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.download.download_service uses a type in frontend.src.app.dashboard.service.user.dataset.dataset_service.
frontend.src.app.dashboard.service.user.download.download_service uses frontend.src.app.dashboard.service.user.dataset.dataset_service, so a change to frontend.src.app.dashboard.service.user.dataset.dataset_service can break frontend.src.app.dashboard.service.user.download.download_service, while a change to frontend.src.app.dashboard.service.user.download.download_service can't break frontend.src.app.dashboard.service.user.dataset.dataset_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.download.download_service uses a module listed above it, which is the healthy direction.
frontend.src.app.dashboard.service.user.search_service uses frontend.src.app.hub.service.hub_service, so a change to frontend.src.app.hub.service.hub_service can break frontend.src.app.dashboard.service.user.search_service, while a change to frontend.src.app.dashboard.service.user.search_service can't break frontend.src.app.hub.service.hub_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.search_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.search_service uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.dashboard.service.user.search_service uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.dashboard.service.user.search_service, while a change to frontend.src.app.dashboard.service.user.search_service can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.search_service uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a type in agent-service.src.types.workflow.
frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, while a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a type in agent-service.src.api.workflow-api.
frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses agent-service.src.api.workflow-api, so a change to agent-service.src.api.workflow-api can break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, while a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can't break agent-service.src.api.workflow-api.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, while a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, while a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a type in agent-service.src.api.backend-api.
frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses agent-service.src.api.backend-api, so a change to agent-service.src.api.backend-api can break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, while a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can't break agent-service.src.api.backend-api.
Position
Below the diagonal: frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, while a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, while a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.engine.architecture.coordinator uses org.apache.texera.amber.core.workflow, so a change to org.apache.texera.amber.core.workflow can break org.apache.texera.amber.engine.architecture.coordinator, while a change to org.apache.texera.amber.engine.architecture.coordinator can't break org.apache.texera.amber.core.workflow.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.coordinator uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in org.apache.texera.amber.engine.architecture.coordinator uses a type in org.apache.texera.amber.engine.architecture.common.
org.apache.texera.amber.engine.architecture.coordinator uses org.apache.texera.amber.engine.architecture.common, so a change to org.apache.texera.amber.engine.architecture.common can break org.apache.texera.amber.engine.architecture.coordinator, while a change to org.apache.texera.amber.engine.architecture.coordinator can't break org.apache.texera.amber.engine.architecture.common.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.coordinator uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.engine.architecture.worker uses org.apache.texera.amber.core.tuple, so a change to org.apache.texera.amber.core.tuple can break org.apache.texera.amber.engine.architecture.worker, while a change to org.apache.texera.amber.engine.architecture.worker can't break org.apache.texera.amber.core.tuple.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.worker uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.engine.architecture.worker uses org.apache.texera.amber.core.executor, so a change to org.apache.texera.amber.core.executor can break org.apache.texera.amber.engine.architecture.worker, while a change to org.apache.texera.amber.engine.architecture.worker can't break org.apache.texera.amber.core.executor.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.worker uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.engine.architecture.worker uses org.apache.texera.amber.engine.architecture.common, so a change to org.apache.texera.amber.engine.architecture.common can break org.apache.texera.amber.engine.architecture.worker, while a change to org.apache.texera.amber.engine.architecture.worker can't break org.apache.texera.amber.engine.architecture.common.
Position
Below the diagonal: org.apache.texera.amber.engine.architecture.worker uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.operator.visualization uses org.apache.texera.amber.core.tuple, so a change to org.apache.texera.amber.core.tuple can break org.apache.texera.amber.operator.visualization, while a change to org.apache.texera.amber.operator.visualization can't break org.apache.texera.amber.core.tuple.
Position
Below the diagonal: org.apache.texera.amber.operator.visualization uses a module listed above it, which is the healthy direction.
org.apache.texera.amber.operator.visualization uses org.apache.texera.amber.operator, so a change to org.apache.texera.amber.operator can break org.apache.texera.amber.operator.visualization, while a change to org.apache.texera.amber.operator.visualization can't break org.apache.texera.amber.operator.
Position
Below the diagonal: org.apache.texera.amber.operator.visualization uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, while a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, while a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, while a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, while a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, while a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.service.execute-workflow.execute-workflow_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.power-button.computing-unit-selection_component, while a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.component.power-button.computing-unit-selection_component, while a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.power-button.computing-unit-selection_component, while a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.component.power-button.computing-unit-selection_component, while a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.power-button.computing-unit-selection_component, while a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.power-button.computing-unit-selection_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in agent-service.src.api.backend-api.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses agent-service.src.api.backend-api, so a change to agent-service.src.api.backend-api can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break agent-service.src.api.backend-api.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, so a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, so a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component, while a change to frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.property-editor.operator-property-edit-frame.operator-property-edit-frame_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.component.workflow-editor.workflow-editor_component, while a change to frontend.src.app.workspace.component.workflow-editor.workflow-editor_component can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.workflow-editor.workflow-editor_component, while a change to frontend.src.app.workspace.component.workflow-editor.workflow-editor_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.workflow-editor.workflow-editor_component, while a change to frontend.src.app.workspace.component.workflow-editor.workflow-editor_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, so a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can break frontend.src.app.workspace.component.workflow-editor.workflow-editor_component, while a change to frontend.src.app.workspace.component.workflow-editor.workflow-editor_component can't break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.workflow-editor.workflow-editor_component, while a change to frontend.src.app.workspace.component.workflow-editor.workflow-editor_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-editor.workflow-editor_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in agent-service.src.types.workflow.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses agent-service.src.types.workflow, so a change to agent-service.src.types.workflow can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break agent-service.src.types.workflow.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in agent-service.src.api.workflow-api.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses agent-service.src.api.workflow-api, so a change to agent-service.src.api.workflow-api can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break agent-service.src.api.workflow-api.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.workspace.service.workflow-result.workflow-result_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.workspace.service.workflow-result.workflow-result_service, so a change to frontend.src.app.workspace.service.workflow-result.workflow-result_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.workspace.service.workflow-result.workflow-result_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.common.service.user.user_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.common.service.user.user_service, so a change to frontend.src.app.common.service.user.user_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.common.service.user.user_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, so a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.workflow-form.workflow-form_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.workflow-form.workflow-form_component, while a change to frontend.src.app.workspace.component.workflow-form.workflow-form_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workflow-form.workflow-form_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.hub.service.hub_service, so a change to frontend.src.app.hub.service.hub_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.hub.service.hub_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.workspace.service.workflow-result.workflow-result_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.workspace.service.workflow-result.workflow-result_service, so a change to frontend.src.app.workspace.service.workflow-result.workflow-result_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.workspace.service.workflow-result.workflow-result_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.common.service.user.user_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.common.service.user.user_service, so a change to frontend.src.app.common.service.user.user_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.common.service.user.user_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, so a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.workspace_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.workspace_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.workspace_component, while a change to frontend.src.app.workspace.component.workspace_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.workspace_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.common.service.gui-config_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.common.service.gui-config_service, so a change to frontend.src.app.common.service.gui-config_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.common.service.gui-config_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.common.service.notification.notification_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.common.service.notification.notification_service, so a change to frontend.src.app.common.service.notification.notification_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.common.service.notification.notification_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.common.service.user.user_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.common.service.user.user_service, so a change to frontend.src.app.common.service.user.user_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.common.service.user.user_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.common.service.workflow-persist.workflow-persist_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.common.service.workflow-persist.workflow-persist_service, so a change to frontend.src.app.common.service.workflow-persist.workflow-persist_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.common.service.workflow-persist.workflow-persist_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service, so a change to frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.workspace.service.workflow-graph.model.workflow-action_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service, so a change to frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.common.service.computing-unit.computing-unit-status.computing-unit-status_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service, so a change to frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.dashboard.service.user.workflow-version.workflow-version_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service, so a change to frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.workspace.service.compile-workflow.workflow-compiling_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.workspace.service.execute-workflow.execute-workflow_service, so a change to frontend.src.app.workspace.service.execute-workflow.execute-workflow_service can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.workspace.service.execute-workflow.execute-workflow_service.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.src.app.workspace.component.menu.menu_component uses a type in frontend.src.app.workspace.component.power-button.computing-unit-selection_component.
frontend.src.app.workspace.component.menu.menu_component uses frontend.src.app.workspace.component.power-button.computing-unit-selection_component, so a change to frontend.src.app.workspace.component.power-button.computing-unit-selection_component can break frontend.src.app.workspace.component.menu.menu_component, while a change to frontend.src.app.workspace.component.menu.menu_component can't break frontend.src.app.workspace.component.power-button.computing-unit-selection_component.
Position
Below the diagonal: frontend.src.app.workspace.component.menu.menu_component uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 51% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
159
High / Critical
A03:2025 — Software Supply Chain Failures
101
High / Critical
A07:2025 — Authentication Failures
38
High / Critical
A02:2025 — Security Misconfiguration
32
High / Critical
Roadmap
Top priorities: Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
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 — 318
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 — 753
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 — 360
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 87 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 — 87 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, 1396 of 1431 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.
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: this repository's production source spans .ts, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 99.5% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
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 7,202 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 782 test source file(s) (.scala, .py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .scala, and the scala executor ran against the .scala half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (bun:test via `npm install --ignore-scripts` (no lockfile) in agent-service/ (326 tests); vitest via `yarn install --immutable --mode=skip-build` in frontend/ (0 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/esotericsoftware/kryo5/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
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.
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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in 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. `amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala`, `frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts` 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.
AC2 Forms & labels — 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. 156 further occurrence(s) are not listed individually; the score already reflects all 196.
AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 30 further occurrence(s) are not listed individually; the score already reflects all 70.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is MacWire, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — Container texera-liquibase-liquibase-1 service "liquibase" didn't complete successfully: exit 1 service "liquibase" didn't complete successfully: exit 1; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
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.
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. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
X3 Exception handling — 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
Repo exclusion declarations: 18 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
55 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was shared-editing.interface.updateYTypeFromObject at 43. A further 1 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 UserDatasetFileRendererComponent.reloadFileContent at 28 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts (UserDatasetFileRendererComponent.reloadFileContent at 28). 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.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with shared-editing.interface.updateYTypeFromObject (cyclomatic 43), OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept (cyclomatic 39), MyJsonFormatVisitorWrapper.expectObjectFormat (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 114 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with shared-editing.interface.updateYTypeFromObject (cognitive 72), MyJsonFormatVisitorWrapper.expectObjectFormat (cognitive 65). — 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 6.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 54 serious findings✓ 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 19 FileTooLong finding(s) in God Classes — start with workflow-editor.component.ts, workflow-form.component.ts, JsonSchemaGenerator.scala. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 15 TooManyMethods finding(s) in God Classes — start with workflow-graph.ts, workflow-action.service.ts, REDACTED. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 13 ClassTooLong finding(s) in God Classes — start with workflow-editor.component.ts, workflow-form.component.ts, operator-property-edit-frame.component.ts. — One of this dimension's main actionable groups (13 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
59 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .ts (39% 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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RegexOpDesc.scala, DatasetResource.scala, ModelResource.scala. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 4 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with AccessControlResource.scala, CostBasedScheduleGenerator.scala, SyncExecutionResource.scala. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ComputingUnitMaster.scala, PveResource.scala, PythonLexerUtils.scala. — One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.5 / 10Strong✓ 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 (npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 7 module(s) off the main sequence, with abstractness counted on 20 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: Config · ×7
What to do
Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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 JsonSchemaGenerator.scala, DatasetResource.scala, ModelResource.scala. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
15636 test methods: 15580 unit, 16 integration, 0 BDD, 40 e2e. The JavaScript/TypeScript suite contributes 7202 `it`/`test` case(s) across 274 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 1217 test function(s) across 87 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 7217 test case(s) across 612 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 23 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.
1 skipped, 21 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 7202 tests. Measured on the JavaScript/TypeScript suite only — at least 782 test source file(s) (.scala, .py) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: should call doContinue for all workers if no breakpoints are hit · ×21frontend/src/app/workspace/service/operator-debug/udf-debug.service.spec.ts:353
Skipped test: should debounce the user form input to avoid emitting event too frequentlyfrontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:393
Fixed-sleep synchronisation: mid-run state is GENERATINGagent-service/src/agent/texera-agent.spec.ts:796
Mock-dominated test: warns when adding the pasted operators and links fails · ×135frontend/src/app/workspace/service/operator-menu/operator-menu.service.spec.ts:440
What to do
Resolve the 21 No assertions finding(s) in Test Quality — start with dataset.service.spec.ts (8), admin-cu-image.component.spec.ts (4), notebook-migration.service.spec.ts (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 1 Skipped test finding(s) in Test Quality — start with operator-property-edit-frame.component.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with texera-agent.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with operator-property-edit-frame.component.ts, workflow-form.component.ts, menu.component.ts. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with HuggingFaceCodegenBase.scala. — One of this dimension's main actionable groups (1 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 Factor8.9 / 10Strong✓ 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.
83 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala. Counted over 758 of the 1256 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 · ×8
Further sole-owners (lower concentration)
What to do
Resolve the 8 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (8 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
85 deducted task-comment markers across 170095 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 81 TodoComment finding(s) in Explicit Debt — start with operator-property-edit-frame.component.spec.ts (3), user-workflow.component.ts (3), ParallelCSVScanSourceOpExec.scala (3). — One of this dimension's main actionable groups (81 warning-level).
Resolve the 4 HackComment finding(s) in Explicit Debt — start with code-editor.component.ts, list-item.component.ts, card-item.component.ts. — One of this dimension's main actionable groups (4 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 232 document(s) read across 5 unit(s).
Documentation: no build, run or usage examplepyright-language-service/README.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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.
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.
doc comments repeat the namesfrontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:278
What to do
Resolve the 48 redundant comment finding(s) in Comment Value — start with workflow-editor.component.spec.ts (4), drag-drop.service.ts (4), menu.component.ts (3). — One of this dimension's main actionable groups (48 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 22 build units (Python, npm, sbt) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
34 finding(s): 0 critical, 34 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 25 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (25 issue-level).
Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
159 finding(s): 0 critical, 128 high, 30 medium, 1 low. 82 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 65 file(s) — `.github/scripts/smoke-boot.sh` (line 51, line 80), `.github/scripts/test_create_release_tarballs.sh` (lines 24–169), `amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala`, `bin/dockerfiles/snapshot/install.sh`, `bin/k8s/templates/aws/s3-credentials-secret.yaml`, … (+60 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
No action in Static Analysis (SAST) — all 82 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (82 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 52 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (36), REDACTED (9), REDACTED (3). — One of this dimension's main actionable groups (52 issue-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 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.
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 15 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 13 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 recommendation-level).
Detailed fixes: d31_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.
56 of 758 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/RandomUserAgent.java. Counted over 758 of the 1256 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with RandomUserAgent.java, SQLSourceOpExec.scala. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 54 Orphaned file finding(s) in Knowledge Freshness — start with preset-wrapper.component.ts, prompts.ts, agent-interaction.component.ts. — One of this dimension's main actionable groups (54 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with auth-guard.service.ts, user-dashboard-test-fixtures.ts. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 17 Change coupling finding(s) in Change Coupling — start with TexeraWebSocketEvent.scala (2), ConfigResource.scala, execute-workflow.service.ts. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with ComputingUnitManagingService.scala. — 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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 23 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 alternatives5.8 / 10Adequate✓ 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.
Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×2) — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:89, frontend/src/app/workspace/component/result-panel/result-panel-modal.component.html:46
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 & labels4.0 / 10Weak✓ 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.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×13) — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:46, frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:168, frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:227, …
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). (×12) — frontend/src/app/common/formly/array.type.ts:29, frontend/src/app/common/formly/array.type.ts:43, frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.html:36, …
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×8) — frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:31, frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:37, frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:43, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:32, frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:38, frontend/src/app/dashboard/component/admin/user/admin-user.component.html:214, …
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.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — frontend/src/app/dashboard/component/user/files-uploader/conflicting-file-modal-content/conflicting-file-modal-content.component.html:21
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. (×3) — frontend/src/app/dashboard/component/user/flarum/flarum.component.html:20, frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.html:25, frontend/src/app/workspace/component/visualization-panel-content/visualization-frame-content.component.html:20
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — frontend/src/app/dashboard/component/user/versions-files-browser/versions-files-browser.component.html:159
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 <texera-root>, so there is no content here to wrap — render the <main> from the component mounted into it. — frontend/src/index.html:21
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".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×18) — frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.html:60, frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:65, frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:73, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". (×9) — frontend/src/app/dashboard/component/admin/user/admin-user.component.html:206, frontend/src/app/dashboard/component/admin/user/admin-user.component.html:227, frontend/src/app/dashboard/component/admin/user/admin-user.component.html:250, …
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×6) — frontend/src/app/dashboard/component/user/filters/filters.component.html:23, frontend/src/app/dashboard/component/user/filters/filters.component.html:49, frontend/src/app/dashboard/component/user/filters/filters.component.html:74, …
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. (×2) — frontend/src/app/dashboard/component/user/list-item/list-item.component.html:26, frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.html:111
This <i> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. (×2) — frontend/src/app/dashboard/component/user/user-venv/user-venv.component.html:56, frontend/src/app/workspace/component/power-button/computing-unit-selection.component.html:117
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×3) — frontend/src/app/hub/component/landing-page/landing-page.component.html:27, frontend/src/app/hub/component/landing-page/landing-page.component.html:33, frontend/src/app/hub/component/landing-page/landing-page.component.html:39
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.
`.dataset-id-container` sets color: white on background-color: grey — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/result-exportation/result-exportation.component.scss:28
`.panel-header` sets color: white on background-color: #547baa — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/jupyter-notebook-panel/jupyter-notebook-panel.component.scss:36
`.agent-count` sets color: #8c8c8c on background-color: #f0f0f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/agent/agent-panel/agent-panel.component.scss:165
`.message-content` sets color: white on background-color: #1890ff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.scss:84
`.ellipsis-row td` sets color: #999 on background-color: #fafafa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.scss:103
`.col-type` sets color: #8c8c8c on background-color: #f0f0f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.scss:177
`i` sets color: #ef4444 on background-color: #fef2f2 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:122, frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:172
`.tag-public i` sets color: #3b82f6 on background-color: #eff6ff — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:153, frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:157
`.tag-downloadable i` sets color: #22c55e on background-color: #f0fdf4 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:158, frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:162
`.tag-framework i` sets color: #a855f7 on background-color: #faf5ff — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:163
`.tag-format i` sets color: #f59e0b on background-color: #fffbeb — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:168
`.button-group button.defaults-to-form-on` sets color: #1e90ff on background-color: #e6f7ff — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/dashboard/component/user/list-item/list-item.component.scss:178
`&:hover` sets color: #1e90ff on background-color: #cceeff — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.scss:242
`.delete-btn:hover` sets color: #ff4d4f on background-color: #fff1f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.scss:270
`&:hover` sets color: #1890ff on background-color: #f0f6ff — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:117
`.pc-topbar .wf-name` 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. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:83
`input[nz-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. — frontend/src/app/dashboard/component/user/search-bar/search-bar.component.scss:28
`.resource-name-edit-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. — frontend/src/app/dashboard/component/user/list-item/list-item.component.scss:137
`.instr .instr-bar .chev` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:225
`.wf .wf-bar .chev` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:559
`#run-button .anticon-loading` moves (`animation: loading 1.4s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/workspace/component/menu/menu.component.scss:136
`.operator-label > .text` moves (`transition: transform 0.5s 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/workspace/component/left-panel/operator-menu/operator-label/operator-label.component.scss:41
`.results-container .entity-cards .entity-card` moves (`transition: transform 0.3s ease,
box-shadow 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/hub/component/browse-section/browse-section.component.scss:49
`.advanced-settings-chevron` moves (`transition: transform 0.28s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:131
`.advanced-settings-inner` moves (`transition: opacity 0.26s ease 0.04s,
transform 0.26s ease 0.04s`) 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. — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:203
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 · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 122 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — REDACTED:95
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
`loadFromCheckpoint` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonWorkflowWorker.scala:275
`debugCommand` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:67
`evaluatePythonExpression` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:72
`retryCurrentTuple` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:77
`noOperation` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:80
`processTuple` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/ifStatement/IfOpExec.scala:48, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/split/SplitOpExec.scala:56
What to do
Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`loadFromCheckpoint` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonWorkflowWorker.scala:275
`DataProcessorRPCHandlerInitializer` has 4 unfinished members out of 5 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:42
`debugCommand` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:67
`evaluatePythonExpression` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:72
`retryCurrentTuple` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:77
`noOperation` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:80
`processTuple` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/ifStatement/IfOpExec.scala:48, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/split/SplitOpExec.scala:56
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 18 of 21 project(s) that lack one — worth up to 1.7 pts.
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 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.
Only 15/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `pyright-language-service`.
`agent-service/src/server.ts` reports through `console.*` at line 575 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:575
`agent-service/src/server.ts` reports through `console.*` at line 576 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:576
`agent-service/src/server.ts` reports through `console.*` at line 577 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:577
`agent-service/src/server.ts` reports through `console.*` at line 578 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:578
`agent-service/src/server.ts` reports through `console.*` at line 579 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:579
`agent-service/src/server.ts` reports through `console.*` at line 581 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:581
`agent-service/src/server.ts` reports through `console.*` at line 589 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:589
`agent-service/src/server.ts` reports through `console.*` at line 593 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:593
`agent-service/src/server.ts` reports through `console.*` at line 594 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:594
`agent-service/src/server.ts` reports through `console.*` at line 596 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:596
`agent-service/src/server.ts` reports through `console.*` at line 598 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:598
`agent-service/src/server.ts` reports through `console.*` at line 599 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:599
`agent-service/src/server.ts` reports through `console.*` at line 600 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:600
`agent-service/src/server.ts` reports through `console.*` at line 605 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:605
`agent-service/src/server.ts` reports through `console.*` at line 606 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:606
`agent-service/src/server.ts` reports through `console.*` at line 607 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:607
`agent-service/src/server.ts` reports through `console.*` at line 608 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:608
`agent-service/src/server.ts` reports through `console.*` at line 609 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:609
`agent-service/src/server.ts` reports through `console.*` at line 610 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:610
`agent-service/src/server.ts` reports through `console.*` at line 611 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:611
`agent-service/src/server.ts` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:612
`agent-service/src/server.ts` reports through `console.*` at line 613 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — agent-service/src/server.ts:613
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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.
`REDACTED` 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`. — REDACTED:17
What to do
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.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · 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. (×4) — agent-service/src/api/backend-api.ts:81, agent-service/src/api/compile-api.ts:61, agent-service/src/api/workflow-api.ts:54, …
`.openConnection(` 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) — amber/src/main/scala/org/apache/texera/web/resource/aiassistant/AiAssistantManager.scala:57, amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala:552, common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/model/LakeFSFileDocument.scala:137, …
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.
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
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.
Do you agree with this assessment?
R1 · Type Safety9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
32 duplicated blocks under frontend/src/app/ have copies in at least two of the sibling directories common, dashboard, hub, workspace — 17 of them are reported below, and 15 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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. — frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146
17 duplicated blocks under frontend/src/app/workspace/component/ have copies in at least two of the sibling directories agent, code-editor-dialog, dataset-file-selector, dataset-selection-modal, dataset-version-selector, hugging-face-audio-upload (+9 more sibling(s) not listed) — 7 of them are reported below, and 10 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 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. — frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:55
13 duplicated blocks under frontend/src/app/dashboard/component/user/ have copies in at least two of the sibling directories files-uploader, list-item, markdown-description, share-access, user-computing-unit, user-dataset (+5 more sibling(s) not listed) — 9 of them are reported below, and 4 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103
6 duplicated blocks under the repository root have copies in at least two of the sibling directories agent-service, frontend — 4 of them are reported below, and 2 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 6 and which does not depend on how exactly each block's copies still match. 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. — agent-service/src/agent/util/workflow-utils.ts:65
5 duplicated blocks under frontend/src/app/workspace/ have copies in at least two of the sibling directories component, service — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:392
frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:233 · frontend/src/app/dashboard/component/user/list-item/list-item.component.ts:149 — the two spans are one implementation copied and then locally edited — 1352 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. — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:233
frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103 · frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:92 — the two spans are one implementation copied and then locally edited — 1061 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. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103
frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:34 · frontend/src/app/dashboard/service/user/model/model.service.ts:29 — the two spans are one implementation copied and then locally edited — 884 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. — frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:34
frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146 · REDACTED:755 — the two spans are one implementation copied and then locally edited — 407 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. — frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146
frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:80 · frontend/src/app/dashboard/component/user/list-item/list-item.component.ts:87 — the two spans are one implementation copied and then locally edited — 371 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. — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:80
frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts:61 · frontend/src/app/dashboard/component/user/user-model/user-model-creator/user-model-creator.component.ts:66 — the two spans are one implementation copied and then locally edited — 339 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. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts:61
frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:54 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:51 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:54
frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:263 · REDACTED:856 — 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. — frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:263
frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:154 · frontend/src/app/hub/component/hub-search-result/hub-search-result.component.ts:99 — the two spans are one implementation copied and then locally edited — 288 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. — frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:154
frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:185 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:171 — 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. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:185
frontend/src/app/dashboard/service/user/download/download.service.ts:67 · frontend/src/app/dashboard/service/user/download/download.service.ts:104 — 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. — frontend/src/app/dashboard/service/user/download/download.service.ts:67
frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1441 · frontend/src/app/workspace/component/property-editor/port-property-edit-frame/port-property-edit-frame.component.ts:235 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1441
frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:130 · frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:157 — 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. — frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:130
agent-service/src/agent/tools/workflow-crud-tools.ts:156 · agent-service/src/agent/tools/workflow-crud-tools.ts:268 — the two spans are one implementation copied and then locally edited — 183 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — agent-service/src/agent/tools/workflow-crud-tools.ts:156
frontend/src/app/dashboard/service/user/resource-registry/dataset-resource.descriptor.ts:29 · frontend/src/app/dashboard/service/user/resource-registry/model-resource.descriptor.ts:30 — 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. — frontend/src/app/dashboard/service/user/resource-registry/dataset-resource.descriptor.ts:29
frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1247 · frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1272 — 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. — frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1247
frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:145 · frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:224 — 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. — frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:145
REDACTED:359 · REDACTED:380 — 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. — REDACTED:359
frontend/src/app/dashboard/type/dashboard-entry.ts:81 · frontend/src/app/dashboard/type/dashboard-entry.ts:100 — 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. — frontend/src/app/dashboard/type/dashboard-entry.ts:81
frontend/src/app/workspace/component/dataset-file-selector/dataset-file-selector.component.ts:61 · frontend/src/app/workspace/component/dataset-version-selector/dataset-version-selector.component.ts:57 — 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. — frontend/src/app/workspace/component/dataset-file-selector/dataset-file-selector.component.ts:61
frontend/src/app/workspace/service/agent/agent.service.ts:668 · frontend/src/app/workspace/service/agent/agent.service.ts:717 — 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. — frontend/src/app/workspace/service/agent/agent.service.ts:668
frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:564 · frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:589 — 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. — frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:564
frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit.component.ts:71 · frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:114 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:111 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit.component.ts:71
frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:524 · frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts: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. — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:524
frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:121 · frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:162 — 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. — frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:121
frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:450 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:503 — 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. — frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:450
agent-service/src/agent/util/workflow-utils.ts:65 · frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:247 — 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. — agent-service/src/agent/util/workflow-utils.ts:65
frontend/src/app/common/util/computing-unit.util.ts:155 · frontend/src/app/common/util/computing-unit.util.ts:173 — 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. — frontend/src/app/common/util/computing-unit.util.ts:155
frontend/src/app/dashboard/component/user/user-quota/user-quota.component.ts:123 · frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:261 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/app/dashboard/component/user/user-quota/user-quota.component.ts:123
frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:697 · frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:730 — 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. — frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:697
agent-service/src/agent/workflow-state.ts:202 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:1146 — the two spans are one implementation copied and then locally edited — 110 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. — agent-service/src/agent/workflow-state.ts:202
frontend/src/app/dashboard/component/admin/computing-unit/admin-computing-unit.component.ts:159 · frontend/src/app/dashboard/component/admin/computing-unit/cluster-capacity/admin-cluster-capacity.component.ts:152 — the two spans are one implementation copied and then locally edited — 61 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. — frontend/src/app/dashboard/component/admin/computing-unit/admin-computing-unit.component.ts:159
frontend/src/app/dashboard/component/user/user-warehouse/user-warehouse.component.ts:93 · REDACTED:266 — the two spans are one implementation copied and then locally edited — 82 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. — frontend/src/app/dashboard/component/user/user-warehouse/user-warehouse.component.ts:93
frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:483 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:537 — 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. — frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:483
frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:270 · frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:288 — 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. — frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:270
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 · 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.
updateYTypeFromObject has cyclomatic complexity 38 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/types/shared-editing.interface.ts:97
(anonymous) has cyclomatic complexity 31 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 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. — frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:928
(anonymous) has cyclomatic complexity 29 and cognitive complexity 35; 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. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1137
executeOperatorAndFormat has cyclomatic complexity 24 and cognitive complexity 35; 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. — agent-service/src/agent/tools/workflow-execution-tools.ts:353
getRunButtonBehavior has cyclomatic complexity 23 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/component/menu/menu.component.ts:436
serializeOperator has cyclomatic complexity 21 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. — agent-service/src/agent/util/context-utils.ts:218
readParameter has cyclomatic complexity 21 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. — frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:120
handleWebSocketMessage has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/service/agent/agent.service.ts:448
dropInvalidAttributeValues 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. — frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:420
getOperatorIdsFromStep has cyclomatic complexity 19 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. — agent-service/src/agent/texera-agent.ts:770
splitStatements has cyclomatic complexity 19 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. — frontend/src/app/workspace/util/loop-variable.util.ts:202
getParsedColumnStats has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:217
(anonymous) has cyclomatic complexity 18 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. — frontend/src/app/dashboard/service/user/search.service.ts:249
(anonymous) has cyclomatic complexity 17 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. — REDACTED:313
parseRUiParameters has cyclomatic complexity 17 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:147
(anonymous) has cyclomatic complexity 17 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. — REDACTED:71
execute has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — agent-service/src/agent/tools/workflow-crud-tools.ts:254
(anonymous) has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:322
createYTypeFromObject has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/types/shared-editing.interface.ts:50
areOperatorSchemasEqual has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/app/workspace/types/operator-schema.interface.ts:76
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files5.6 / 10Adequate✓ 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.
frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts has 2100 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1
frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts has 2026 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1
frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1
REDACTED has 1241 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
frontend/src/app/workspace/service/agent/agent.service.ts has 1145 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/agent/agent.service.ts:1
frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts has 1142 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:1
frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts has 1065 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:1
frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts has 1056 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:1
frontend/src/app/workspace/component/menu/menu.component.ts has 1053 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/menu/menu.component.ts:1
frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts has 927 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts:1
frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts has 748 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:1
frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts has 735 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:1
agent-service/src/agent/texera-agent.ts has 729 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — agent-service/src/agent/texera-agent.ts:1
frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts has 715 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts:1
frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts:1
frontend/src/app/workspace/service/notebook-migration/migration-llm.ts has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/notebook-migration/migration-llm.ts:1
frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:1
frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts has 615 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:1
frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts:1
frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts has 591 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:1
agent-service/src/server.ts has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — agent-service/src/server.ts:1
frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:1
frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts has 539 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:1
REDACTED has 523 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
frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts has 515 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts:1
frontend/src/app/workspace/component/result-panel/result-panel.component.ts has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/result-panel/result-panel.component.ts:1
REDACTED has 492 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
frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts:1
frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:1
frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.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. — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:1
frontend/src/app/workspace/service/report-generation/report-generation.service.ts has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/service/report-generation/report-generation.service.ts:1
frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts:1
frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts 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. — frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts:1
frontend/src/app/app.module.ts has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/app.module.ts:1
frontend/src/app/common/service/user/auth.service.ts has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/common/service/user/auth.service.ts:1
frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts:1
agent-service/src/agent/tools/workflow-execution-tools.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — agent-service/src/agent/tools/workflow-execution-tools.ts:1
frontend/src/app/workspace/component/workspace.component.ts has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/workspace/component/workspace.component.ts:1
frontend/src/app/dashboard/component/user/share-access/share-access.component.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/app/dashboard/component/user/share-access/share-access.component.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 Coverage9.7 / 10Exemplary✓ 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. (×9) — frontend/src/app/app.module.ts:1, frontend/src/jsdom-svg-polyfill.ts:1, frontend/src/app/app-routing.module.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 REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 14 application, 11 tooling and 276 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
no import path from any entry point (14 application, 11 tooling, 276 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — frontend/src/jsdom-svg-polyfill.ts
Nothing imports this binding — it is safe to review for removal. (×6) — frontend/src/app/app-routing.constant.ts:80, frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:50, frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:42, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — frontend/src/app/workspace/service/agent/agent.service.ts:141
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×2) — frontend/src/app/workspace/service/preset/preset.service.ts:72, frontend/src/app/workspace/service/workflow-graph/model/shared-model.ts:82
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:100
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×10) — frontend/src/app/workspace/component/result-panel/console-frame/console-frame.component.ts:27, frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:24, frontend/src/app/workspace/component/code-editor-dialog/workers/extension-host.worker.ts:21, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://cdn.jsdelivr.net/npm/jsoneditor@10.1.0/dist/jsoneditor.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — frontend/src/index.html:66
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.0 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`collectReferences` is exported, takes a document from its caller (line 136) and hands it to `visit`, which calls itself at line 143 (`visit`) with a piece of `value` (and at line 146) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/app/workspace/util/loop-variable-field.util.ts:143
`collectReferences` is exported, takes a document from its caller (line 136) and hands it to `visit`, which calls itself at line 236 (`visit`) with a piece of `node` (and at line 251, line 258) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/app/workspace/util/loop-variable-field.util.ts:236
`conditionalRequiredRules` is exported, takes a document from its caller (line 115) and hands it to `visit`, which calls itself at line 138 (`visit`) with a piece of `node` — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:138
`getPathsUnderOrEqualDatasetFileNode` is exported, takes a document from its caller (line 50) and hands it to `gatherPaths`, which calls itself at line 59 (`gatherPaths`) with a piece of `node` — and nowhere in `gatherPaths` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `gatherPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/app/common/type/datasetVersionFileTree.ts:59
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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 3/7 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.
`fetchOperatorMetadata` 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 })`. — agent-service/src/api/backend-api.ts:79
`compileWorkflowAsync` 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 })`. — agent-service/src/api/compile-api.ts:46
`persistWorkflow` 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 })`. — agent-service/src/api/workflow-api.ts:44
`retrieveWorkflow` 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 })`. — agent-service/src/api/workflow-api.ts:78
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 an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.0 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`this.fileURL` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustUrl` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts:366
`newHtml` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:111
`id` is text this program did not author, and it is written into a script or style context through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. (×3) — frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:225, frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:226, frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:227
`url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustResourceUrl` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — frontend/src/app/workspace/component/jupyter-notebook-panel/jupyter-notebook-panel.component.ts:72
`currentStr[i]` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:280
`char` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:290, REDACTED:292
`newHtmlString` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — frontend/src/app/workspace/component/visualization-panel-content/visualization-frame-content.component.ts:85
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — notebook-migration-service/src/main/scala/org/apache/texera/service/util/JupyterProbe.scala:47, notebook-migration-service/src/main/scala/org/apache/texera/service/util/JupyterProbe.scala:67, REDACTED:87
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — frontend/src/app/workspace/service/workflow-graph/model/shared-model.ts:155, frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.ts:86, frontend/src/app/workspace/service/form-binding/form-binding.service.ts:289, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:189, frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:191
`case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — computing-unit-managing-service/src/main/scala/org/apache/texera/service/util/ImageValidationClient.scala:277, amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:84, amber/src/main/scala/org/apache/texera/web/observability/WorkflowMetricsRecorder.scala:72
`case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpExec.scala:179, common/workflow-core/src/main/scala/org/apache/texera/amber/util/IcebergUtil.scala:249, amber/src/main/scala/org/apache/texera/web/service/LakekeeperClient.scala:192, …
`case e: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — amber/src/main/scala/org/apache/texera/web/resource/aiassistant/AiAssistantManager.scala:70
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — amber/src/main/python/core/storage/iceberg/iceberg_utils.py:306, amber/src/main/python/core/runnables/heartbeat.py:60
What to do
Swallowed exception (caught, then discarded)
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 `REDACTED` 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.
`warn` at line 80 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — file-service/src/main/scala/org/apache/texera/service/util/LakeFSExceptionHandler.scala:80
`warn` at line 310 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:310
`warn` at line 992 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:992
`warn` at line 778 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:778
`warn` at line 1198 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1198
`warn` at line 1572 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1572
`info` at line 44 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common/auth/src/main/scala/org/apache/texera/auth/RequestLoggingFilter.scala:44
`info` at line 223 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:223
`info` at line 190 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/TexeraWebApplication.scala:190
`warn` at line 119 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:119
`warn` at line 209 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:209
`warn` at line 227 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:227
`error` at line 92 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:92
`warn` at line 155 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:155
`warn` at line 162 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:162
`warn` at line 219 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:219
`warn` at line 261 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:261
`warn` at line 362 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:362
`warn` at line 377 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:377
`warn` at line 429 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:429
`debug` at line 434 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:434
`debug` at line 439 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:439
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
No build over this repository's 703 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
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 — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
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.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 40 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — Container texera-liquibase-liquibase-1 service "liquibase" didn't complete successfully: exit 1 service "liquibase" didn't complete successfully: exit 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
D14 License Compliance — Not scored — this repository's 93 pinned sbt dependency coordinate(s) were read from its 11 sbt build file(s), but Maven Central could not be asked for the licence of 80 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/esotericsoftware/kryo5/5.6.0/kryo5-5.6.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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 is measured on C# and TypeScript only; Java, JavaScript, Python, Scala not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed 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 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 — polyglot repository, one half has no runner
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 136 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P9 Domain vs controller coverage — coverage data present for 23 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×17
<input> without a programmatic label frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:46— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:168— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:227— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.html:236— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/common/component/warehouse-create-modal/warehouse-create-modal.component.html:30— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:32— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:38— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:44— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.html:39— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.html:48— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:120— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:145— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:170— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:214— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:234— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.html:99— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label frontend/src/app/dashboard/component/user/list-item/list-item.component.html:100— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×12
<button> with no accessible text frontend/src/app/common/formly/array.type.ts:29— 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).
<button> with no accessible text frontend/src/app/common/formly/array.type.ts:43— 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).
<button> with no accessible text frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.html:36— 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).
<button> with no accessible text frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.html:66— 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).
<button> with no accessible text frontend/src/app/common/formly/repeat-dnd/repeat-dnd.component.html:46— 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).
<button> with no accessible text frontend/src/app/dashboard/component/admin/execution/admin-execution.component.html:132— 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).
<button> with no accessible text frontend/src/app/dashboard/component/admin/execution/admin-execution.component.html:146— 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).
<button> with no accessible text frontend/src/app/dashboard/component/admin/execution/admin-execution.component.html:157— 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).
<button> with no accessible text frontend/src/app/dashboard/component/admin/execution/admin-execution.component.html:168— 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).
<button> with no accessible text frontend/src/app/dashboard/component/admin/user/admin-user.component.html:308— 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).
<button> with no accessible text frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.html:112— 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).
<button> with no accessible text frontend/src/app/dashboard/component/user/markdown-description/markdown-description.component.html:67— 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).
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×12
Click handler on a non-interactive <li> frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.html:162— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <li> frontend/src/app/dashboard/component/user/user-icon/user-icon.component.html:32— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/dashboard/component/user/user-venv/user-venv.component.html:51— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/agent/agent-panel/agent-panel.component.html:56— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/left-panel/left-panel.component.html:26— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/left-panel/left-panel.component.html:38— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/left-panel/left-panel.component.html:75— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/left-panel/left-panel.component.html:84— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/left-panel/left-panel.component.html:114— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/menu/coeditor-user-icon/coeditor-user-icon.component.html:32— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/menu/coeditor-user-icon/coeditor-user-icon.component.html:38— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> frontend/src/app/workspace/component/power-button/computing-unit-selection.component.html:95— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×9
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/admin/user/admin-user.component.html:206— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/admin/user/admin-user.component.html:227— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/admin/user/admin-user.component.html:250— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/user/list-item/list-item.component.html:110— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.html:66— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:73— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> frontend/src/app/dashboard/component/user/user-warehouse/user-warehouse-list-item/user-warehouse-list-item.component.html:51— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> frontend/src/app/workspace/component/agent/agent-panel/agent-registration/agent-registration.component.html:49— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> frontend/src/app/workspace/component/hugging-face/hugging-face.component.html:141— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <label> that labels no control · ×8
<label> that labels no control frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:31— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:37— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:43— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:49— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/dashboard/component/user/filters/filters.component.html:97— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/dashboard/component/user/filters/filters.component.html:131— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/dashboard/component/user/filters/filters.component.html:168— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.html:34— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <i> · ×4
Click handler on a non-interactive <i> frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.html:79— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <i> frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.html:157— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <i> frontend/src/app/workspace/component/hugging-face/hugging-face.component.html:72— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <i> frontend/src/app/workspace/component/hugging-face/hugging-face.component.html:125— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <textarea> without a programmatic label · ×3
<textarea> without a programmatic label frontend/src/app/common/service/user/registration-request-modal/registration-request-modal.component.html:50— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label frontend/src/app/dashboard/component/admin/user/admin-user.component.html:257— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/src/app/dashboard/component/user/feedback/feedback.component.html:30— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC3 · Page structure· <iframe> without a title · ×3
<iframe> without a title frontend/src/app/dashboard/component/user/flarum/flarum.component.html:20— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
<iframe> without a title frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.html:25— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
<iframe> without a title frontend/src/app/workspace/component/visualization-panel-content/visualization-frame-content.component.html:20— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×2
Hover-only interaction on <div> frontend/src/app/dashboard/component/user/list-item/list-item.component.html:26— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.html:111— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
AC4 · Keyboard semantics· Clickable role="button" that no keyboard user can reach · ×2
Clickable role="button" that no keyboard user can reach frontend/src/app/dashboard/component/user/user-venv/user-venv.component.html:56— This <i> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach frontend/src/app/workspace/component/power-button/computing-unit-selection.component.html:117— This <i> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Orphaned knowledge common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/RandomUserAgent.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Boundary-crossing change coupling: auth-guard.service.ts ↔ user-icon.component.ts frontend/src/app/common/service/user/auth-guard.service.ts:1— `frontend/src/app/common/service/user/auth-guard.service.ts` (context common) and `frontend/src/app/dashboard/component/user/user-icon/user-icon.component.ts` (context dashboard) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `831b5143` Add flags to the `gui` to control the displayed pages (#3343) (at that commit the files were still `core/gui/src/app/common/service/user/auth-guard.service.ts` and `core/gui/src/app/dashboard/component/user/user-icon/user-icon.component.ts`); `55bcd4d8` Replace all hardcoded URLs with app-routing constants (#3075) (at that commit the files were still `core/gui/src/app/common/service/user/auth-guard.service.ts` and `core/gui/src/app/dashboard/component/user/user-icon/user-icon.component.ts`); `05d741ea` Revert "Introduce the check of user system config mismatch" (#1993) (at that commit the files were still `core/new-gui/src/app/common/service/user/auth-guard.service.ts` and `core/new-gui/src/app/dashboard/user/component/user-icon/user-icon.component.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: user-dashboard-test-fixtures.ts ↔ workflow-action.service.ts frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:1— `frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts` (context dashboard) and `frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts` (context workspace) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `850fd851` feat: introduce materialized execution mode (#4158); `663c0227` Remove Operator Group (#3033) (at that commit the files were still `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts` and `core/gui/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts`); `0acb1c10` Add publish buttons to the dataset and workflow (#2835) (at that commit the files were still `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts` and `core/gui/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts`) — run `git show` on any of them.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.html:60— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <img> · ×1
Click handler on a non-interactive <img> frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:65— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Unlisted import '@ant-design/colors' frontend/src/app/workspace/component/result-panel/console-frame/console-frame.component.ts:27— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@ant-design/icons-angular' frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:24— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@codingame/monaco-vscode-api' frontend/src/app/workspace/component/code-editor-dialog/workers/extension-host.worker.ts:21— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@codingame/monaco-vscode-editor-api' frontend/src/app/workspace/component/code-editor-dialog/workers/editor.worker.ts:24— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@codingame/monaco-vscode-textmate-service-override' frontend/src/app/workspace/component/code-editor-dialog/workers/textmate.worker.ts:21— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'date-fns' frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.spec.ts:45— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'graphlib' frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts:25— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'jquery' frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.browser.spec.ts:38— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'json-schema' frontend/src/app/workspace/component/loop-variable-input/loop-variable-input.component.spec.ts:27— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'lodash' frontend/src/app/common/formly/collab-wrapper/collab-wrapper/collab-wrapper.component.ts:23— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
TodoComment frontend/src/app/workspace/service/workflow-graph/util/workflow-util.service.ts:72— // TODO: change this to drag-and-drop — 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 frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:340— // TODO: use uniform serde to calculate the portID — 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 frontend/src/app/workspace/service/validation/validation-workflow.service.spec.ts:121— // TODO: this test is incompatible with shared editing. — 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 frontend/src/app/workspace/service/operator-metadata/operator-metadata.service.ts:66— // TODO: refactor this to 2 functions: getOperatorMetadataStream() and getOperatorMetadata() — 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 frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:55— // TODO: change this declaration — 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 frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:91— // TODO: move this to another service, or redesign how 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 frontend/src/app/workspace/component/workspace.component.spec.ts:21— // TODO(coverage): this spec was set up in #5037 to render the workspace with
TodoComment frontend/src/app/workspace/component/workspace.component.spec.ts:181— // TODO(coverage): rewrite using stub child components via remove/add so 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 frontend/src/app/workspace/component/workspace.component.ts:122— // TODO: make their lifecycle better — 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 frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:71— // TODO: This is only a temporary change, will introduce another level of disable option. — 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 frontend/src/app/workspace/component/result-panel/result-panel.component.ts:350— // TODO: let the results be tied with an execution ID instead of a workflow ID — 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 frontend/src/app/workspace/component/result-panel/console-frame/console-frame.component.ts:119— // TODO: move Configuration Menu to a separate component — 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 frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:128— // TODO(coverage): tests in this spec exercise dynamic Formly form rendering; — 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 frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:281— // TODO: Temporarilly disable this unit test because PR #1924 is failing the test,
TodoComment frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:429— // // TODO: FIX 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 frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1082— // TODO: we temporarily disable this due to Yjs update causing issues in Formly. — 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 frontend/src/app/workspace/component/left-panel/time-travel/time-travel.component.ts:138— // TODO:add FULL_REPLAY here to support fault tolerance. — 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 frontend/src/app/workspace/component/dataset-selection-modal/dataset-selection-modal.component.ts:88— // TODO(dataset-prefix): require the prefix once all ml model support PRs are done. — 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 frontend/src/app/dashboard/service/user/workflow-version/workflow-version.service.ts:160— // TODO: the logic of the function will be refined later — 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 frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.spec.ts:142— // TODO: add this test case back and figure out why it failed — 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 frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:528— // @ts-ignore // TODO: fix this with notification component — 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 frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:726— // TODO: fix this with notification component — 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 frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:758— // TODO: fix this with notification component — 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 file-service/src/main/scala/org/apache/texera/service/type/LakeFSFileNode.scala:131— //TODO: To check the logic of promoting the leaf vs duplicating the leaf — 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 computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:350— // TODO: use AmberConfig here; it is only accessible in workflow-executing-service — 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.
Swallowed exception (empty catch) frontend/src/app/workspace/service/workflow-graph/model/shared-model.ts:155— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.ts:86— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/service/form-binding/form-binding.service.ts:289— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1422— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1428— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:515— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:542— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/left-panel/time-travel/time-travel.component.ts:97— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:189— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:191— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:370— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:256— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/dashboard/service/user/file-resource/multipart-upload.service.ts:259— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/src/app/common/service/computing-unit/workflow-computing-unit/workflow-computing-unit-managing.service.ts:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:659— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:824— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:906— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:927— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:1133— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) common/workflow-core/src/main/scala/org/apache/texera/service/util/S3StorageClient.scala:248— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveManager.scala:196— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) amber/src/main/python/pytexera/storage/large_binary_output_stream.py:173— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) agent-service/src/agent/texera-agent.ts:807— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
No assertions: should call doContinue for all workers if no breakpoints are hit frontend/src/app/workspace/service/operator-debug/udf-debug.service.spec.ts:353— 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: makes no HTTP call for wid 0, which would map to the shared default filename frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.spec.ts:161— 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: deleteNotebookForWorkflow makes no HTTP call frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.spec.ts:467— 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: init does not fetch for an unsaved workflow (undefined wid) frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.spec.ts:372— 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: falls back to the REST stop endpoint when no websocket is open frontend/src/app/workspace/service/agent/agent.service.spec.ts:214— 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: should not fetch media-proxy for non-media remote URLs frontend/src/app/workspace/component/result-panel/result-panel-modal.component.spec.ts:131— 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: lists versions from the endpoint matching the caller's login state frontend/src/app/dashboard/service/user/model/model.service.spec.ts:170— 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: uses the anonymous presign endpoint for a logged-out viewer frontend/src/app/dashboard/service/user/model/model.service.spec.ts:216— 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: getDataset hits /dataset/{did} when logged in frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:227— 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: getDataset hits /dataset/public/{did} when anonymous frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:232— 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: retrieveDatasetVersionSingleFile uses the public presign endpoint when anonymous frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:257— 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: retrieveDatasetVersionList hits the authenticated path when logged in frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:454— 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: retrieveDatasetVersionList hits the public path when anonymous frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:459— 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: retrieveDatasetVersionFileTree picks the authenticated path when logged in frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:477— 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: retrieveDatasetVersionFileTree picks the public path when anonymous frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:482— 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: updateDatasetDownloadable POSTs to /dataset/{did}/update/downloadable frontend/src/app/dashboard/service/user/dataset/dataset.service.spec.ts:521— 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: refuses to register an image with either field blank frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:112— 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: sends one request when Enter is pressed twice frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:157— 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: sends one request when Refresh is clicked twice frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:181— 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: sends one request when Remove is clicked twice frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.spec.ts:189— 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: is a no-op (no HTTP request) when the key is not present in the local dict frontend/src/app/common/service/user/config/user-config.service.spec.ts:157— 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.
FileTooLong: workflow-editor/workflow-editor.component.ts frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts— FileTooLong — 1239 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: WorkflowEditorComponent (121-2184). The bar is 500 significant lines; this is 739 over it, 2.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: workflow-form/workflow-form.component.ts frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts— FileTooLong — 1004 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: WorkflowFormComponent (174-2223). The bar is 500 significant lines; this is 504 over it, 2.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: jsonSchema/JsonSchemaGenerator.scala common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala— FileTooLong — 987 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: JsonSchemaGenerator (301-1690). The bar is 500 significant lines; this is 487 over it, 1.97× 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: resource/ResourceUploadService.scala file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala— FileTooLong — 982 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 482 over it, 1.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: resource/DatasetResource.scala file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala— FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: DatasetResource (264-1279). The bar is 500 significant lines; this is 396 over it, 1.79× 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: operator-property-edit-frame/operator-property-edit-frame.component.ts frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts— FileTooLong — 892 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: OperatorPropertyEditFrameComponent (184-1473). The bar is 500 significant lines; this is 392 over it, 1.78× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: resource/ModelResource.scala file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala— FileTooLong — 847 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: ModelResource (188-1212). The bar is 500 significant lines; this is 347 over it, 1.69× 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: REDACTED REDACTED— FileTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: ComputingUnitSelectionComponent (140-1425). The bar is 500 significant lines; this is 309 over it, 1.62× 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: joint-ui/joint-ui.service.ts frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts— FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: JointUIService (207-1108). The bar is 500 significant lines; this is 242 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: resource/ComputingUnitManagingResource.scala computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala— FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 179 over it, 1.36× 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: menu/menu.component.ts frontend/src/app/workspace/component/menu/menu.component.ts— FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: MenuComponent (141-1149). The bar is 500 significant lines; this is 175 over it, 1.35× 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/agent.service.ts frontend/src/app/workspace/service/agent/agent.service.ts— FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: AgentService (196-1259). The bar is 500 significant lines; this is 168 over it, 1.34× 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: resource/SyncExecutionResource.scala amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala— FileTooLong — 653 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: SyncExecutionResource (129-944). The bar is 500 significant lines; this is 153 over it, 1.31× 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: workflow/WorkflowResource.scala amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala— FileTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: WorkflowResource (337-1006). The bar is 500 significant lines; this is 151 over it, 1.30× 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: workflow/WorkflowExecutionsResource.scala amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 128 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: model/workflow-action.service.ts frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts— FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: WorkflowActionService (96-1265). The bar is 500 significant lines; this is 94 over it, 1.19× 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/texera-agent.ts agent-service/src/agent/texera-agent.ts— FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: TexeraAgent (84-849). The bar is 500 significant lines; this is 67 over it, 1.13× 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: model/workflow-graph.ts frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: WorkflowGraph (102-1185). The bar is 500 significant lines; this is 62 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: ngbd-modal-workflow-executions/workflow-execution-history.component.ts frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: WorkflowExecutionHistoryComponent (105-802). The bar is 500 significant lines; this is 37 over it, 1.07× 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×19
Change coupling: ConfigResource.scala ↔ gui-config.service.mock.ts config-service/src/main/scala/org/apache/texera/service/resource/ConfigResource.scala:1— `config-service/src/main/scala/org/apache/texera/service/resource/ConfigResource.scala` and `frontend/src/app/common/service/gui-config.service.mock.ts` change together 100% of the time (15 of the 15 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `f8c5e1a2` feat(frontend): add AI workflow fixer with LLM-powered diff panel (#8…; `dcf8217f` feat(frontend): add the warehouse dashboard tab (#8005); `782c37f9` feat(config): add form-view-enabled feature flag, default off (#8029) — run `git show` on any of them.
Change coupling: execute-workflow.service.ts ↔ mock-workflow-plan.ts frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:1— `frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts` and `frontend/src/app/workspace/service/execute-workflow/mock-workflow-plan.ts` change together 72% of the time (13 of the 18 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 13 shared commits counted here, the most recent 3 are `f88c1565` Support partial workflow execution up to an operator (#2259) (at that commit the files were still `core/new-gui/src/app/workspace/service/execute-workflow/execute-workflow.service.ts` and `core/new-gui/src/app/workspace/service/execute-workflow/mock-workflow-plan.ts`); `3555422e` Fix port descriptor (#2229) (at that commit the files were still `core/new-gui/src/app/workspace/service/execute-workflow/execute-workflow.service.ts` and `core/new-gui/src/app/workspace/service/execute-workflow/mock-workflow-plan.ts`); `5e166730` Temporarily remove operator cache feature (#2084) (at that commit the files were still `core/new-gui/src/app/workspace/service/execute-workflow/execute-workflow.service.ts` and `core/new-gui/src/app/workspace/service/execute-workflow/mock-workflow-plan.ts`) — run `git show` on any of them.
Change coupling: user-dashboard-test-fixtures.ts ↔ user-workflow.component.ts frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:1— `frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts` and `frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `850fd851` feat: introduce materialized execution mode (#4158); `663c0227` Remove Operator Group (#3033) (at that commit the files were still `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts` and `core/gui/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts`); `287caaa3` Fix Google Avatar Display Issue When Users Log In via Google (#2821) (at that commit the files were still `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts` and `core/gui/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts`) — run `git show` on any of them.
Change coupling: TexeraWebSocketEvent.scala ↔ WorkflowWebsocketResource.scala amber/src/main/scala/org/apache/texera/web/model/websocket/event/TexeraWebSocketEvent.scala:1— `amber/src/main/scala/org/apache/texera/web/model/websocket/event/TexeraWebSocketEvent.scala` and `amber/src/main/scala/org/apache/texera/web/resource/WorkflowWebsocketResource.scala` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7d7a3399` Move websocket wid registration to OnOpen (#2674) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/websocket/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/WorkflowWebsocketResource.scala`); `686dad9d` Python UDF V2 Evaluate Expression (#1333) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/WorkflowWebsocketResource.scala`); `93931e8a` [Operator Caching Step 4] Integrate Operator Caching with Backend Log… (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/WorkflowWebsocketResource.scala`) — run `git show` on any of them.
Change coupling: workflow-editor.component.ts ↔ joint-graph-wrapper.ts frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1— `frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts` and `frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts` change together 69% of the time (51 of the 74 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 51 shared commits counted here, the most recent 3 are `b8b308e9` feat(frontend): preview an operator's result when hovering it on the …; `ba2667a2` refactor(frontend): remove the dead group-highlight streams (#8687); `09220c21` chore(frontend): remove the dead link-breakpoint plumbing (#8615) — run `git show` on any of them.
Change coupling: ServletAwareConfigurator.scala ↔ UserAuthenticator.scala amber/src/main/scala/org/apache/texera/web/ServletAwareConfigurator.scala:1— `amber/src/main/scala/org/apache/texera/web/ServletAwareConfigurator.scala` and `amber/src/main/scala/org/apache/texera/web/auth/UserAuthenticator.scala` change together 67% of the time (8 of the 12 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 8 shared commits counted here, the most recent 3 are `179f177d` feat: add user registration form (#4185); `2fbe37ab` feat: add affiliation attribute to user (#4113); `7c35e427` feat: add account creation time (#3736) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/ServletAwareConfigurator.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/auth/UserAuthenticator.scala`) — run `git show` on any of them.
Change coupling: WorkflowAccessResource.scala ↔ WorkflowResource.scala amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowAccessResource.scala:1— `amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowAccessResource.scala` and `amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala` change together 64% of the time (14 of the 22 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `48356940` refactor: move workflow access and result helpers to common (#9219); `e4c44202` fix(workflow, hub): treat a workflow's owner as WRITE wherever access…; `2351cb85` feat(workflow): serve the pinned copy to public viewers (#8575) — run `git show` on any of them.
Change coupling: PythonProxyClient.scala ↔ PythonProxyServer.scala amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala:1— `amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala` and `amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyServer.scala` change together 58% of the time (7 of the 12 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `91a701b7` fix(amber): carry the loop StateFrame envelope through JVM operators …; `da53b378` Rename ControlPayload Class to Direct Control Message (DCM) (#3492) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyClient.scala` and `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyServer.scala`); `4fd03acc` Fix ChannelMarker transmission between Java and Python (#3434) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyClient.scala` and `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyServer.scala`) — run `git show` on any of them.
Change coupling: versions-list.component.ts ↔ menu.component.ts frontend/src/app/workspace/component/left-panel/versions-list/versions-list.component.ts:1— `frontend/src/app/workspace/component/left-panel/versions-list/versions-list.component.ts` and `frontend/src/app/workspace/component/menu/menu.component.ts` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `d0179832` Add support to create a copy of an earlier version of a workflow (#2990) (at that commit the files were still `core/gui/src/app/workspace/component/left-panel/versions-list/versions-list.component.ts` and `core/gui/src/app/workspace/component/menu/menu.component.ts`); `9f0d1a19` Make Left-Panel Component dragable, resizable, and collapsible (#2248) (at that commit the files were still `core/new-gui/src/app/workspace/component/left-panel/versions-list/versions-list.component.ts` and `core/new-gui/src/app/workspace/component/menu/menu.component.ts`); `9beb54ab` Move versions frame onto the left penal (#2212) (at that commit the files were still `core/new-gui/src/app/workspace/component/left-panel/versions-frame/versions-frame.component.ts` and `core/new-gui/src/app/workspace/component/navigation/navigation.component.ts`) — run `git show` on any of them.
Change coupling: joint-ui.service.ts ↔ workflow-status.service.ts frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:1— `frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts` and `frontend/src/app/workspace/service/workflow-status/workflow-status.service.ts` change together 51% of the time (19 of the 37 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 19 shared commits counted here, the most recent 3 are `51d75643` feat(frontend): restore the heat-map after a page refresh (#8552); `f9b899a5` refactor(frontend): split operator state from statistics (#8301); `76d33f64` feat(gui): Improve UI for operator port metrics (#3477) (at that commit the files were still `core/gui/src/app/workspace/service/joint-ui/joint-ui.service.ts` and `core/gui/src/app/workspace/service/workflow-status/workflow-status.service.ts`) — run `git show` on any of them.
Change coupling: ResultExportService.scala ↔ result-exportation.component.ts amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala:1— `amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala` and `frontend/src/app/workspace/component/result-exportation/result-exportation.component.ts` change together 50% of the time (7 of the 14 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4f4b3830` Add `Parquet` option in export workflow result types (#3478) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/service/ResultExportService.scala` and `core/gui/src/app/workspace/component/result-exportation/result-exportation.component.ts`); `4baee252` Fix streaming issue for single CSV export (#3350) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/service/ResultExportService.scala` and `core/gui/src/app/workspace/component/result-exportation/result-exportation.component.ts`); `9ecd32ca` Fix download operators result (#3241) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/service/ResultExportService.scala` and `core/gui/src/app/workspace/component/result-exportation/result-exportation.component.ts`) — run `git show` on any of them.
Change coupling: DatasetResource.scala ↔ dataset-file-selector.component.ts amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/dataset/DatasetResource.scala:1— `amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/dataset/DatasetResource.scala` and `frontend/src/app/workspace/component/dataset-file-selector/dataset-file-selector.component.ts` change together 50% of the time (6 of the 12 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `88b439dc` Improve selecting source file experience (#3002) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/dashboard/user/dataset/DatasetResource.scala` and `core/gui/src/app/workspace/component/input-autocomplete/input-autocomplete.component.ts`); `e90302c2` Show the previously-selected dataset and version(if any) when open th… (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/dashboard/user/dataset/DatasetResource.scala` and `core/gui/src/app/workspace/component/input-autocomplete/input-autocomplete.component.ts`); `a88a7221` Fix dataset APIs not fetching files shared by others correctly (#2754) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/dashboard/user/dataset/DatasetResource.scala` and `core/gui/src/app/workspace/component/input-autocomplete/input-autocomplete.component.ts`) — run `git show` on any of them.
Change coupling: network_receiver.py ↔ PythonProxyClient.scala amber/src/main/python/core/runnables/network_receiver.py:1— `amber/src/main/python/core/runnables/network_receiver.py` and `amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala` change together 50% of the time (6 of the 12 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `878eb8a3` feat(amber): add loop-bookkeeping columns to materialized State (dorm…; `da53b378` Rename ControlPayload Class to Direct Control Message (DCM) (#3492) (at that commit the files were still `core/amber/src/main/python/core/runnables/network_receiver.py` and `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyClient.scala`); `74da6167` Add ChannelMarker support on pyAmber (#3245) (at that commit the files were still `core/amber/src/main/python/core/runnables/network_receiver.py` and `core/amber/src/main/scala/edu/uci/ics/amber/engine/architecture/pythonworker/PythonProxyClient.scala`) — run `git show` on any of them.
Change coupling: dataset-detail.component.ts ↔ user-dataset-version-creator.component.ts frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:1— `frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts` and `frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts` change together 50% of the time (6 of the 12 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 6 shared commits counted here, the most recent 3 are `7f3bba50` feat(dataset): add dataset contributor display and editing (#6953); `a7d2adf2` feat: add custom cover image support for datasets (#4117); `77673b31` fix: private dataset can be set as downloadable (#3666) (at that commit the files were still `core/gui/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts` and `core/gui/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts`) — run `git show` on any of them.
Change coupling: TexeraWebSocketEvent.scala ↔ TexeraWebSocketRequest.scala amber/src/main/scala/org/apache/texera/web/model/websocket/event/TexeraWebSocketEvent.scala:1— `amber/src/main/scala/org/apache/texera/web/model/websocket/event/TexeraWebSocketEvent.scala` and `amber/src/main/scala/org/apache/texera/web/model/websocket/request/TexeraWebSocketRequest.scala` change together 50% of the time (5 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 — 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 5 shared commits counted here, the most recent 3 are `7d7a3399` Move websocket wid registration to OnOpen (#2674) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/websocket/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/model/websocket/request/TexeraWebSocketRequest.scala`); `686dad9d` Python UDF V2 Evaluate Expression (#1333) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/model/request/TexeraWebSocketRequest.scala`); `93931e8a` [Operator Caching Step 4] Integrate Operator Caching with Backend Log… (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/event/TexeraWebSocketEvent.scala` and `core/amber/src/main/scala/edu/uci/ics/texera/web/model/request/TexeraWebSocketRequest.scala`) — run `git show` on any of them.
Change coupling: WorkflowResource.scala ↔ user-dashboard-test-fixtures.ts amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala:1— `amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala` and `frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts` change together 50% of the time (5 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ff82fd82` fix(workflow): include coverImage in search and list API responses (#…; `0acb1c10` Add publish buttons to the dataset and workflow (#2835) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala` and `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts`); `287caaa3` Fix Google Avatar Display Issue When Users Log In via Google (#2821) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala` and `core/gui/src/app/dashboard/component/user-dashboard-test-fixtures.ts`) — run `git show` on any of them.
Change coupling: TexeraWebSocketRequest.scala ↔ app.module.ts amber/src/main/scala/org/apache/texera/web/model/websocket/request/TexeraWebSocketRequest.scala:1— `amber/src/main/scala/org/apache/texera/web/model/websocket/request/TexeraWebSocketRequest.scala` and `frontend/src/app/app.module.ts` change together 50% of the time (5 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c3154cab` Hookup frontend with backend replay framework (#2272) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/websocket/request/TexeraWebSocketRequest.scala` and `core/new-gui/src/app/app.module.ts`); `686dad9d` Python UDF V2 Evaluate Expression (#1333) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/request/TexeraWebSocketRequest.scala` and `core/new-gui/src/app/app.module.ts`); `9bb456e5` Export workflow result to User Dashboard (#1307) (at that commit the files were still `core/amber/src/main/scala/edu/uci/ics/texera/web/model/request/TexeraWebSocketRequest.scala` and `core/new-gui/src/app/app.module.ts`) — run `git show` on any of them.
Swallowed exception (caught, then discarded) notebook-migration-service/src/main/scala/org/apache/texera/service/util/JupyterProbe.scala:47— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) notebook-migration-service/src/main/scala/org/apache/texera/service/util/JupyterProbe.scala:67— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:87— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) computing-unit-managing-service/src/main/scala/org/apache/texera/service/util/ImageValidationClient.scala:277— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpExec.scala:179— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) common/workflow-core/src/main/scala/org/apache/texera/amber/util/IcebergUtil.scala:249— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/service/LakekeeperClient.scala:192— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:119— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:782— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:813— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:823— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:84— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:173— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/resource/aiassistant/AiAssistantManager.scala:70— `case e: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/scala/org/apache/texera/web/observability/WorkflowMetricsRecorder.scala:72— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/python/core/storage/iceberg/iceberg_utils.py:306— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) amber/src/main/python/core/runnables/heartbeat.py:60— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
TooManyMethods: WorkflowGraph frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:102— TooManyMethods — 93 methods. The bar is 30 methods; this is 63 over it, 3.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: WorkflowActionService frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:93— TooManyMethods — 84 methods. The bar is 30 methods; this is 54 over it, 2.80× 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: ComputingUnitSelectionComponent REDACTED:103— TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: WorkflowEditorComponent frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:106— TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× 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: WorkflowFormComponent frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:148— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: JointGraphWrapper frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts:94— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× 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: MenuComponent frontend/src/app/workspace/component/menu/menu.component.ts:105— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: AgentService frontend/src/app/workspace/service/agent/agent.service.ts:193— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: ModelResource file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:186— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: DatasetResource file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:262— 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: AgentChatComponent frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts:63— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TexeraAgent agent-service/src/agent/texera-agent.ts:84— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WorkflowExecutionHistoryComponent frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:64— 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: JointUIService frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:204— 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.
TooManyMethods: ExecuteWorkflowService frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:76— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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: WorkflowEditorComponent frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:106— ClassTooLong — 1166 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 400 significant lines; this is 766 over it, 2.92× 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: WorkflowFormComponent frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:148— ClassTooLong — 902 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 400 significant lines; this is 502 over it, 2.26× 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: OperatorPropertyEditFrameComponent frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:160— ClassTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 377 over it, 1.94× 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: ComputingUnitSelectionComponent REDACTED:103— ClassTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded), 80 methods. The bar is 400 significant lines; this is 296 over it, 1.74× 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: JointUIService frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:204— ClassTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 202 over it, 1.51× 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: MenuComponent frontend/src/app/workspace/component/menu/menu.component.ts:105— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 179 over it, 1.45× 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: SyncExecutionResource amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:126— ClassTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 166 over it, 1.42× 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: AgentService frontend/src/app/workspace/service/agent/agent.service.ts:193— ClassTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 156 over it, 1.39× 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: WorkflowActionService frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:93— ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 400 significant lines; this is 145 over it, 1.36× 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: TexeraAgent agent-service/src/agent/texera-agent.ts:84— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 119 over it, 1.30× 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: WorkflowGraph frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:102— ClassTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), 93 methods. The bar is 400 significant lines; this is 104 over it, 1.26× 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: WorkflowExecutionHistoryComponent frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:64— ClassTooLong — 456 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 56 over it, 1.14× 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: JointGraphWrapper frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts:94— ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 48 over it, 1.12× 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.
Hotspot: frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:905— frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in OperatorPropertyEditFrameComponent.setFormlyFormBinding at line 905. 2 of those changes were fix/bug commits, and the other 9 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.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: frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1130— frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in WorkflowFormComponent.applyFieldOverrides at line 1130. 7 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/workspace/component/workflow-form/workflow-form.component.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: frontend/src/app/workspace/component/menu/menu.component.ts frontend/src/app/workspace/component/menu/menu.component.ts:436— frontend/src/app/workspace/component/menu/menu.component.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in MenuComponent.getRunButtonBehavior at line 436. 4 of those changes were fix/bug commits, and the other 11 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/workspace/component/menu/menu.component.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: computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:578— computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in ComputingUnitManagingResource.createWorkflowComputingUnit at line 578. 2 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala`: 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: frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts:200— frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in UserDatasetFileRendererComponent.reloadFileContent at line 200. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.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: frontend/src/app/dashboard/service/user/search.service.ts frontend/src/app/dashboard/service/user/search.service.ts:186— frontend/src/app/dashboard/service/user/search.service.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in SearchService.extendSearchResultsWithHubActivityInfo at line 186. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/dashboard/service/user/search.service.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: agent-service/src/agent/texera-agent.ts agent-service/src/agent/texera-agent.ts:496— agent-service/src/agent/texera-agent.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in TexeraAgent.sendMessage at line 496. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- agent-service/src/agent/texera-agent.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: frontend/src/app/workspace/types/shared-editing.interface.ts frontend/src/app/workspace/types/shared-editing.interface.ts:97— frontend/src/app/workspace/types/shared-editing.interface.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in shared-editing.interface.updateYTypeFromObject at line 97. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- frontend/src/app/workspace/types/shared-editing.interface.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: REDACTED REDACTED:171— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ResultTableFrameComponent.ngOnInit at line 171. 1 of those changes was a fix/bug commit, and the other 3 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- REDACTED`: 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: amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:538— amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SyncExecutionResource.collectOperatorResult at line 538. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala`: 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: common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala:178— common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in IcebergDocument.getUsingFileSequenceOrder at line 178. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala`: 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×10
Untrusted text written into markup unescaped frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.ts:366— `this.fileURL` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustUrl` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:111— `newHtml` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:225— `id` is text this program did not author, and it is written into a script or style context through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:226— `id` is text this program did not author, and it is written into a script or style context through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:227— `id` is text this program did not author, and it is written into a script or style context through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/jupyter-notebook-panel/jupyter-notebook-panel.component.ts:72— `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustResourceUrl` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped REDACTED:280— `currentStr[i]` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:290— `char` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:292— `char` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped frontend/src/app/workspace/component/visualization-panel-content/visualization-frame-content.component.ts:85— `newHtmlString` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Outbound HTTP without resilience agent-service/src/api/backend-api.ts:81— `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 agent-service/src/api/compile-api.ts:61— `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 agent-service/src/api/workflow-api.ts:54— `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 agent-service/src/api/workflow-api.ts:82— `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 amber/src/main/scala/org/apache/texera/web/resource/aiassistant/AiAssistantManager.scala:57— `.openConnection(` 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 amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala:552— `.openConnection(` 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 common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/model/LakeFSFileDocument.scala:137— `.openConnection(` 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/URLFetchUtil.scala:30— `.openConnection(` 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 REDACTED:188— `.openConnection(` 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.
R4 · Test Coverage· No test reaches this file · ×9
No test reaches this file frontend/src/app/app.module.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 frontend/src/jsdom-svg-polyfill.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 frontend/src/app/app-routing.module.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 REDACTED: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 notebook-migration-service/src/main/resources/custom.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file pyright-language-service/src/main.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 notebook-migration-service/src/main/resources/custom-preload.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/main.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 pyright-language-service/src/language-server-runner.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.
Duplicated block (7 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:101— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:101-107 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/unneststring/UnnestStringOpDesc.scala:152-161 — 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:101` 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 (7 lines × 2) file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:552— file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:552-558 | file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:603-609 — 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 `file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:552` 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) file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:345— file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:345-351 | file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:415-421 — 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 `file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:345` 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) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/sort/SortOpDesc.scala:80— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/sort/SortOpDesc.scala:80-86 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/sortPartitions/SortPartitionsOpDesc.scala:88-94 — 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 (7 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:80— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:80-86 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:204-210 — 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) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLConnUtil.scala:37— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLConnUtil.scala:37-43 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/postgresql/PostgreSQLConnUtil.scala:37-43 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLConnUtil.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/postgresql/PostgreSQLConnUtil.scala` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLConnUtil.scala:37` 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 (7 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/source/PythonUDFSourceOpDescV2.scala:136— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/source/PythonUDFSourceOpDescV2.scala:136-142 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFSourceOpDesc.scala:109-115 — 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 (7 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/ternaryContour/TernaryContourOpDesc.scala:96— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/ternaryContour/TernaryContourOpDesc.scala:96-103 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/windRoseChart/WindRoseChartOpDesc.scala:70-76 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:225— `.instr .instr-bar .chev` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:559— `.wf .wf-bar .chev` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/workspace/component/menu/menu.component.scss:136— `#run-button .anticon-loading` moves (`animation: loading 1.4s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/workspace/component/left-panel/operator-menu/operator-label/operator-label.component.scss:41— `.operator-label > .text` moves (`transition: transform 0.5s 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/hub/component/browse-section/browse-section.component.scss:49— `.results-container .entity-cards .entity-card` moves (`transition: transform 0.3s ease,
box-shadow 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:131— `.advanced-settings-chevron` moves (`transition: transform 0.28s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:203— `.advanced-settings-inner` moves (`transition: opacity 0.26s ease 0.04s,
transform 0.26s ease 0.04s`) 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.
Off the main sequence: Config — Config: abstractness 0.00, instability 0.00, distance 1.00 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: DAO — DAO: abstractness 0.00, instability 0.00, distance 1.00 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: Util — Util: abstractness 0.00, instability 0.00, distance 1.00 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: PyBuilder — PyBuilder: abstractness 0.17, instability 0.00, distance 0.83 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: Auth — Auth: abstractness 0.00, instability 0.20, distance 0.80 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: Observability — Observability: abstractness 0.12, instability 0.13, distance 0.76 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: Resource — Resource: abstractness 0.00, instability 0.25, distance 0.75 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Unfinished stub — body is `???` amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonWorkflowWorker.scala:275— `loadFromCheckpoint` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:67— `debugCommand` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:72— `evaluatePythonExpression` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:77— `retryCurrentTuple` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:80— `noOperation` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/ifStatement/IfOpExec.scala:48— `processTuple` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is `???` common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/split/SplitOpExec.scala:56— `processTuple` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonWorkflowWorker.scala:275— `loadFromCheckpoint` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:67— `debugCommand` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:72— `evaluatePythonExpression` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:77— `retryCurrentTuple` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:80— `noOperation` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/ifStatement/IfOpExec.scala:48— `processTuple` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is ??? / NotImplementedError common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/split/SplitOpExec.scala:56— `processTuple` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface.
AC4 · Keyboard semantics· Anchor without href · ×6
Anchor without href frontend/src/app/dashboard/component/user/filters/filters.component.html:23— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href frontend/src/app/dashboard/component/user/filters/filters.component.html:49— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href frontend/src/app/dashboard/component/user/filters/filters.component.html:74— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href frontend/src/app/dashboard/component/user/filters/filters.component.html:108— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href frontend/src/app/dashboard/component/user/filters/filters.component.html:142— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href frontend/src/app/dashboard/component/user/sort-button/sort-button.component.html:20— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
MethodTooLong: OperatorPropertyEditFrameComponent.setFormlyFormBinding frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:905— MethodTooLong — setFormlyFormBinding runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× 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: JointUIService.getCustomOperatorStyleAttrs frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:734— MethodTooLong — getCustomOperatorStyleAttrs 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.
MethodTooLong: TexeraAgent.sendMessage agent-service/src/agent/texera-agent.ts:496— MethodTooLong — sendMessage runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: MultipartUploadService.multipartUpload frontend/src/app/dashboard/service/user/file-resource/multipart-upload.service.ts:57— MethodTooLong — multipartUpload runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
MethodTooLong: WorkflowFormComponent.ngOnInit frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:329— MethodTooLong — ngOnInit runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.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: MenuComponent.getRunButtonBehavior frontend/src/app/workspace/component/menu/menu.component.ts:436— MethodTooLong — getRunButtonBehavior runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.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.
Low cohesion: JsonSchemaGenerator (LCOM4 6) common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:301— JsonSchemaGenerator's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DatasetResource (LCOM4 5) file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:262— DatasetResource's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ModelResource (LCOM4 5) file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:186— ModelResource's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AsyncRPCClient (LCOM4 4) amber/src/main/scala/org/apache/texera/amber/engine/common/rpc/AsyncRPCClient.scala:130— AsyncRPCClient's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SklearnMLOperatorDescriptor (LCOM4 4) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/base/SklearnAdvancedBaseDesc.scala:95— SklearnMLOperatorDescriptor's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (19 lines × 2 locations) REDACTED:359— REDACTED:359 · REDACTED:380 — 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) frontend/src/app/dashboard/type/dashboard-entry.ts:81— frontend/src/app/dashboard/type/dashboard-entry.ts:81 · frontend/src/app/dashboard/type/dashboard-entry.ts:100 — 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 (19 lines × 2 locations) frontend/src/app/workspace/component/dataset-file-selector/dataset-file-selector.component.ts:61— frontend/src/app/workspace/component/dataset-file-selector/dataset-file-selector.component.ts:61 · frontend/src/app/workspace/component/dataset-version-selector/dataset-version-selector.component.ts:57 — 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) frontend/src/app/workspace/service/agent/agent.service.ts:668— frontend/src/app/workspace/service/agent/agent.service.ts:668 · frontend/src/app/workspace/service/agent/agent.service.ts:717 — 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) frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:564— frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:564 · frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:589 — 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.
Low contrast colour pair in CSS (3.0:1) frontend/src/app/workspace/component/agent/agent-panel/agent-panel.component.scss:165— `.agent-count` sets color: #8c8c8c on background-color: #f0f0f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.scss:177— `.col-type` sets color: #8c8c8c on background-color: #f0f0f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.scss:270— `.delete-btn:hover` sets color: #ff4d4f on background-color: #fff1f0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.scss:117— `&:hover` sets color: #1890ff on background-color: #f0f6ff — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:122— `i` sets color: #ef4444 on background-color: #fef2f2 — 3.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 (3.4:1) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:153— `.tag-public i` sets color: #3b82f6 on background-color: #eff6ff — 3.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 (3.4:1) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:157— `.tag-public i` sets color: #3b82f6 on background-color: #eff6ff — 3.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 (3.4:1) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:172— `i` sets color: #ef4444 on background-color: #fef2f2 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
HackComment frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:159— // hacky solution to reset view after view is rendered. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment frontend/src/app/dashboard/component/user/list-item/list-item.component.ts:384— // hacky fix to display view correctly — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:440— // hacky fix to display view correctly — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment amber/src/main/scala/org/apache/texera/web/resource/WorkflowWebsocketResource.scala:66— // hack to refresh frontend run button state — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Duplicated block (21 lines × 2) access-control-service/src/main/scala/org/apache/texera/service/resource/AccessControlResource.scala:381— access-control-service/src/main/scala/org/apache/texera/service/resource/AccessControlResource.scala:381-401 | access-control-service/src/main/scala/org/apache/texera/service/resource/AccessControlResource.scala:448-468 — 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 `access-control-service/src/main/scala/org/apache/texera/service/resource/AccessControlResource.scala:381` 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 (21 lines × 2) amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:496— amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:496-516 | amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:635-655 — 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 `amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:496` 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 (21 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:637— amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:637-657 | amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:673-693 — 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 (21 lines × 2) file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:462— file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:462-482 | file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:777-797 — 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 `file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:462` 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 (11 lines × 2) amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:153— amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:153-163 | amber/src/main/scala/org/apache/texera/web/TexeraWebApplication.scala:121-131 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `amber/src/main/scala/org/apache/texera/web/TexeraWebApplication.scala:136` calls `register` and `amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:167` 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 (11 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:110— amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:110-120 | amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:148-158 — 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 `amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:110` 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 (11 lines × 2) common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:108— common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:108-118 | common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:130-140 — 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 `common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:108` 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) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/set/difference/DifferenceOpDesc.scala:35— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/set/difference/DifferenceOpDesc.scala:35-45 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/set/intersect/IntersectOpDesc.scala:34-44 — 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 (8 lines × 2) amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:409— amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:409-417 | amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:583-590 — 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 `amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala: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 (8 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/dashboard/admin/execution/AdminExecutionResource.scala:104— amber/src/main/scala/org/apache/texera/web/resource/dashboard/admin/execution/AdminExecutionResource.scala:104-111 | amber/src/main/scala/org/apache/texera/web/resource/dashboard/admin/execution/AdminExecutionResource.scala:145-152 — 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 `amber/src/main/scala/org/apache/texera/web/resource/dashboard/admin/execution/AdminExecutionResource.scala:104` 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) common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:306— common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:306-313 | common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:347-354 — 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 `common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala: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.
Duplicated block (8 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:115— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:115-122 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:106-113 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:115` 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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap frontend/src/app/workspace/util/loop-variable-field.util.ts:143— `collectReferences` is exported, takes a document from its caller (line 136) and hands it to `visit`, which calls itself at line 143 (`visit`) with a piece of `value` (and at line 146) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap frontend/src/app/workspace/util/loop-variable-field.util.ts:236— `collectReferences` is exported, takes a document from its caller (line 136) and hands it to `visit`, which calls itself at line 236 (`visit`) with a piece of `node` (and at line 251, line 258) — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:138— `conditionalRequiredRules` is exported, takes a document from its caller (line 115) and hands it to `visit`, which calls itself at line 138 (`visit`) with a piece of `node` — and nowhere in `visit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap frontend/src/app/common/type/datasetVersionFileTree.ts:59— `getPathsUnderOrEqualDatasetFileNode` is exported, takes a document from its caller (line 50) and hands it to `gatherPaths`, which calls itself at line 59 (`gatherPaths`) with a piece of `node` — and nowhere in `gatherPaths` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `gatherPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X2 · Cancellation propagation· Async function without AbortSignal · ×4
Async function without AbortSignal: fetchOperatorMetadata agent-service/src/api/backend-api.ts:79— `fetchOperatorMetadata` 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 })`.
Async function without AbortSignal: compileWorkflowAsync agent-service/src/api/compile-api.ts:46— `compileWorkflowAsync` 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 })`.
Async function without AbortSignal: persistWorkflow agent-service/src/api/workflow-api.ts:44— `persistWorkflow` 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 })`.
Async function without AbortSignal: retrieveWorkflow agent-service/src/api/workflow-api.ts:78— `retrieveWorkflow` 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 })`.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×3
Link used as a button (placeholder href) frontend/src/app/hub/component/landing-page/landing-page.component.html:27— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Link used as a button (placeholder href) frontend/src/app/hub/component/landing-page/landing-page.component.html:33— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Link used as a button (placeholder href) frontend/src/app/hub/component/landing-page/landing-page.component.html:39— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement frontend/src/app/workspace/component/workflow-form/workflow-form.component.scss:83— `.pc-topbar .wf-name` 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 frontend/src/app/dashboard/component/user/search-bar/search-bar.component.scss:28— `input[nz-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 frontend/src/app/dashboard/component/user/list-item/list-item.component.scss:137— `.resource-name-edit-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.
Duplicated block (6 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:101— amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:101-106 | amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:140-145 — 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 `amber/src/main/scala/org/apache/texera/web/resource/pythonvirtualenvironment/PveResource.scala:101` 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) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/bulletChart/BulletChartOpDesc.scala:103— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/bulletChart/BulletChartOpDesc.scala:103-108 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/bulletChart/BulletChartOpDesc.scala:252-257 — 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 × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:191— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:191-196 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:172-177 — 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 (18 lines × 2 locations) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:524— frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:524 · frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts: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.
Duplicated block (18 lines × 2 locations) frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:121— frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:121 · frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:162 — 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 (18 lines × 2 locations) frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:450— frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:450 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:503 — 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 (17 lines × 2 locations) agent-service/src/agent/util/workflow-utils.ts:65— agent-service/src/agent/util/workflow-utils.ts:65 · frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:247 — 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 (17 lines × 2 locations) frontend/src/app/common/util/computing-unit.util.ts:155— frontend/src/app/common/util/computing-unit.util.ts:155 · frontend/src/app/common/util/computing-unit.util.ts:173 — 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 (17 lines × 2 locations) frontend/src/app/dashboard/component/user/user-quota/user-quota.component.ts:123— frontend/src/app/dashboard/component/user/user-quota/user-quota.component.ts:123 · frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:261 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×3
Duplicated block with local edits (15 matched lines × 2 locations) agent-service/src/agent/workflow-state.ts:202— agent-service/src/agent/workflow-state.ts:202 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:1146 — the two spans are one implementation copied and then locally edited — 110 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (15 matched lines × 2 locations) frontend/src/app/dashboard/component/admin/computing-unit/admin-computing-unit.component.ts:159— frontend/src/app/dashboard/component/admin/computing-unit/admin-computing-unit.component.ts:159 · frontend/src/app/dashboard/component/admin/computing-unit/cluster-capacity/admin-cluster-capacity.component.ts:152 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (15 matched lines × 2 locations) frontend/src/app/dashboard/component/user/user-warehouse/user-warehouse.component.ts:93— frontend/src/app/dashboard/component/user/user-warehouse/user-warehouse.component.ts:93 · REDACTED:266 — the two spans are one implementation copied and then locally edited — 82 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.
AC1 · Text alternatives· <video> without a captions track · ×2
<video> without a captions track frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.html:89— Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
<video> without a captions track frontend/src/app/workspace/component/result-panel/result-panel-modal.component.html:46— Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark frontend/src/app/dashboard/component/user/files-uploader/conflicting-file-modal-content/conflicting-file-modal-content.component.html:21— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark frontend/src/index.html:21— 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 <texera-root>, so there is no content here to wrap — render the <main> from the component mounted into it.
Low contrast colour pair in CSS (2.7:1) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.scss:103— `.ellipsis-row td` sets color: #999 on background-color: #fafafa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.7:1) frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.scss:242— `&:hover` sets color: #1e90ff on background-color: #cceeff — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.2:1) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:158— `.tag-downloadable i` sets color: #22c55e on background-color: #f0fdf4 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.2:1) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.scss:162— `.tag-downloadable i` sets color: #22c55e on background-color: #f0fdf4 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Duplicated block (20 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:334— amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:334-353 | amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:567-586 — 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 `amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:334` 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 (20 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/DualInputPortsPythonUDFOpDescV2.scala:123— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/DualInputPortsPythonUDFOpDescV2.scala:123-142 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:138-157 — 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 (17 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:70— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:70-86 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/json/JSONLScanSourceOpDesc.scala:220-236 — 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:70` 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, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:66` calls `forall`, `Option` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/json/JSONLScanSourceOpDesc.scala:218` 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 (17 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:177— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:177-193 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:164-180 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 2) amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:209— amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:209-223 | amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:251-265 — 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 `amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:209` 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. 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 (15 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpDesc.scala:114— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpDesc.scala:114-128 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLSourceOpDesc.scala:39-53 — 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 (8–10 lines × 2) common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:220— common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:220-229 | file-service/src/main/scala/org/apache/texera/service/resource/DatasetResource.scala:1138-1145 — 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 `common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:220` 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–10 lines × 2) common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:263— common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:263-272 | file-service/src/main/scala/org/apache/texera/service/resource/ModelResource.scala:1173-1180 — 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 `common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/FileResolver.scala:263` 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.
R10 · Code Duplication· Duplicated block with local edits (59 matched lines × 2 locations) · ×2
Duplicated block with local edits (59 matched lines × 2 locations) frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:80— frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:80 · frontend/src/app/dashboard/component/user/list-item/list-item.component.ts:87 — the two spans are one implementation copied and then locally edited — 371 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (59 matched lines × 2 locations) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts:61— frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-version-creator/user-dataset-version-creator.component.ts:61 · frontend/src/app/dashboard/component/user/user-model/user-model-creator/user-model-creator.component.ts:66 — the two spans are one implementation copied and then locally edited — 339 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 (34 lines × 2 locations) frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:185— frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:185 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:171 — 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 (34 lines × 2 locations) frontend/src/app/dashboard/service/user/download/download.service.ts:67— frontend/src/app/dashboard/service/user/download/download.service.ts:67 · frontend/src/app/dashboard/service/user/download/download.service.ts:104 — 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 (24 lines × 2 locations) frontend/src/app/dashboard/service/user/resource-registry/dataset-resource.descriptor.ts:29— frontend/src/app/dashboard/service/user/resource-registry/dataset-resource.descriptor.ts:29 · frontend/src/app/dashboard/service/user/resource-registry/model-resource.descriptor.ts:30 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1247— frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1247 · frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1272 — 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.
AC3 · Page structure· Heading level jumps from h3 to h6 · ×1
Heading level jumps from h3 to h6 frontend/src/app/dashboard/component/user/versions-files-browser/versions-files-browser.component.html:159— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (3.9:1) frontend/src/app/workspace/component/result-exportation/result-exportation.component.scss:28— `.dataset-id-container` sets color: white on background-color: grey — 3.9: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.4:1) frontend/src/app/workspace/component/jupyter-notebook-panel/jupyter-notebook-panel.component.scss:36— `.panel-header` sets color: white on background-color: #547baa — 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 (3.2:1) frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.scss:84— `.message-content` sets color: white on background-color: #1890ff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:163— `.tag-framework i` sets color: #a855f7 on background-color: #faf5ff — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.scss:168— `.tag-format i` sets color: #f59e0b on background-color: #fffbeb — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.9:1) frontend/src/app/dashboard/component/user/list-item/list-item.component.scss:178— `.button-group button.defaults-to-form-on` sets color: #1e90ff on background-color: #e6f7ff — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
shared-editing.interface.updateYTypeFromObject (cyclomatic 43) frontend/src/app/workspace/types/shared-editing.interface.ts:97— shared-editing.interface.updateYTypeFromObject has cyclomatic complexity 43 (threshold 15). Of this number, 38 points are the body's own statements and 5 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.
OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept (cyclomatic 39) frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:925— OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept has cyclomatic complexity 39 (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.
MyJsonFormatVisitorWrapper.expectObjectFormat (cyclomatic 31) common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1049— MyJsonFormatVisitorWrapper.expectObjectFormat has cyclomatic complexity 31 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
ResourceUploadService.initUpload (cyclomatic 31) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:702— ResourceUploadService.initUpload has cyclomatic complexity 31 (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.
RegexOpDesc.unicodeCase (cyclomatic 29) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:125— RegexOpDesc.unicodeCase 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.
SearchService.extendSearchResultsWithHubActivityInfo (cyclomatic 27) frontend/src/app/dashboard/service/user/search.service.ts:186— SearchService.extendSearchResultsWithHubActivityInfo has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 12 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 249, 199, 208). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ResourceUploadService.uploadPart (cyclomatic 26) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:1235— ResourceUploadService.uploadPart has cyclomatic complexity 26 (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.
concat_license_binary.parse (cyclomatic 26) bin/licensing/concat_license_binary.py:117— concat_license_binary.parse 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.
IcebergDocument.getUsingFileSequenceOrder (cyclomatic 25) common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala:178— IcebergDocument.getUsingFileSequenceOrder 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.
LocalDevApp._dispatch (cyclomatic 25) bin/local-dev/tui.py:1388— LocalDevApp._dispatch has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollaborationResource.myOnMsg (cyclomatic 24) amber/src/main/scala/org/apache/texera/web/resource/CollaborationResource.scala:58— CollaborationResource.myOnMsg 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.
TexeraAgent.sendMessage (cyclomatic 24) agent-service/src/agent/texera-agent.ts:496— TexeraAgent.sendMessage has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 578, 548). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ComputingUnitManagingResource.createWorkflowComputingUnit (cyclomatic 23) computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:578— ComputingUnitManagingResource.createWorkflowComputingUnit 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.
workflow-execution-tools.executeOperatorAndFormat (cyclomatic 23) agent-service/src/agent/tools/workflow-execution-tools.ts:353— workflow-execution-tools.executeOperatorAndFormat 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.
WorkflowCompilingService.dropInvalidAttributeValues (cyclomatic 23) frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:420— WorkflowCompilingService.dropInvalidAttributeValues has cyclomatic complexity 23 (threshold 15). Of this number, 20 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.
MenuComponent.getRunButtonBehavior (cyclomatic 23) frontend/src/app/workspace/component/menu/menu.component.ts:436— MenuComponent.getRunButtonBehavior 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.
DPThread.runDPThreadMainLogic (cyclomatic 22) amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DPThread.scala:134— DPThread.runDPThreadMainLogic 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.
context-utils.serializeOperator (cyclomatic 21) agent-service/src/agent/util/context-utils.ts:218— context-utils.serializeOperator 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.
AgentService.handleWebSocketMessage (cyclomatic 21) frontend/src/app/workspace/service/agent/agent.service.ts:448— AgentService.handleWebSocketMessage has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
SyncExecutionResource.collectOperatorResult (cyclomatic 20) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:538— SyncExecutionResource.collectOperatorResult has cyclomatic complexity 20 (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.
AggregateOpDesc.aggExprScalar (cyclomatic 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala:210— AggregateOpDesc.aggExprScalar has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (AggregateOpDesc.aggExprGroupby) 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.
AggregateOpDesc.aggExprGroupby (cyclomatic 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala:251— AggregateOpDesc.aggExprGroupby has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (AggregateOpDesc.aggExprScalar) 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.
MultipartUploadService.multipartUpload (cyclomatic 20) frontend/src/app/dashboard/service/user/file-resource/multipart-upload.service.ts:57— MultipartUploadService.multipartUpload has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 89, 208, 86, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
loop-variable.util.splitStatements (cyclomatic 20) frontend/src/app/workspace/util/loop-variable.util.ts:202— loop-variable.util.splitStatements has cyclomatic complexity 20 (threshold 15). Of this number, 19 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.
SyncExecutionResource.executeWorkflowSync (cyclomatic 19) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:135— SyncExecutionResource.executeWorkflowSync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
PythonLexerUtils.updateTripleQuotedStringState (cyclomatic 19) common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:50— PythonLexerUtils.updateTripleQuotedStringState 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.
IntervalJoinOpExec.processNumValue (cyclomatic 19) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/intervalJoin/IntervalJoinOpExec.scala:140— IntervalJoinOpExec.processNumValue 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.
check_binary_deps.report (cyclomatic 19) bin/licensing/check_binary_deps.py:393— check_binary_deps.report 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.
TexeraAgent.getOperatorIdsFromStep (cyclomatic 19) agent-service/src/agent/texera-agent.ts:770— TexeraAgent.getOperatorIdsFromStep 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.
hugging-face-field-bindings.applyHuggingFaceFieldBindings (cyclomatic 19) frontend/src/app/workspace/util/hugging-face-field-bindings.ts:116— hugging-face-field-bindings.applyHuggingFaceFieldBindings has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
r-ui-udf-parameters-parser.readParameter (cyclomatic 19) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:120— r-ui-udf-parameters-parser.readParameter 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.
FileScanSourceOpDesc.generateStandaloneCode (cyclomatic 18) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:83— FileScanSourceOpDesc.generateStandaloneCode 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.
ExecutorManager._explain_operator_count (cyclomatic 18) amber/src/main/python/core/architecture/managers/executor_manager.py:172— ExecutorManager._explain_operator_count 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.
concat_license_binary.merge (cyclomatic 18) bin/licensing/concat_license_binary.py:202— concat_license_binary.merge has cyclomatic complexity 18 (threshold 15). 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.
search-filter-parameters.searchTestEntries (cyclomatic 18) frontend/src/app/dashboard/type/search-filter-parameters.ts:83— search-filter-parameters.searchTestEntries 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.
loop-variable-field.util.applyLoopVariableField (cyclomatic 18) frontend/src/app/workspace/util/loop-variable-field.util.ts:290— loop-variable-field.util.applyLoopVariableField has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 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.
ResultTableFrameComponent.ngOnInit (cyclomatic 18) REDACTED:171— ResultTableFrameComponent.ngOnInit has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 189, 211, 175, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WorkflowFormComponent.applyFieldOverrides::walk (cyclomatic 18) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1137— WorkflowFormComponent.applyFieldOverrides::walk 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.
ArrowUtils.setTexeraTuple (cyclomatic 17) common/workflow-core/src/main/scala/org/apache/texera/amber/util/ArrowUtils.scala:276— ArrowUtils.setTexeraTuple 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.
shared-editing.interface.createYTypeFromObject (cyclomatic 17) frontend/src/app/workspace/types/shared-editing.interface.ts:50— shared-editing.interface.createYTypeFromObject has cyclomatic complexity 17 (threshold 15). 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, 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.
FiltersComponent.updateDropdownMenus (cyclomatic 17) REDACTED:304— FiltersComponent.updateDropdownMenus has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 313). 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.
loop-block.util.enclosingLoopStarts (cyclomatic 17) frontend/src/app/workspace/util/loop-block.util.ts:51— loop-block.util.enclosingLoopStarts has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 85, 109, 57, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AgentInteractionComponent.getParsedColumnStats (cyclomatic 17) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:217— AgentInteractionComponent.getParsedColumnStats has cyclomatic complexity 17 (threshold 15). 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, 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.
r-ui-udf-parameters-parser.parseRUiParameters (cyclomatic 17) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:147— r-ui-udf-parameters-parser.parseRUiParameters 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.
formly-utils.createValueRulesValidator.<returned closure> (cyclomatic 17) REDACTED:71— formly-utils.createValueRulesValidator.<returned closure> 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.
QueryWorkerStatisticsHandler.coordinatorInitiateQueryStatistics (cyclomatic 16) amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/promisehandlers/QueryWorkerStatisticsHandler.scala:80— QueryWorkerStatisticsHandler.coordinatorInitiateQueryStatistics 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.
CostBasedScheduleGenerator.bottomUpSearch (cyclomatic 16) amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:387— CostBasedScheduleGenerator.bottomUpSearch 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.
HuggingFaceInferenceOpDesc.generatePythonCode (cyclomatic 16) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/HuggingFaceInferenceOpDesc.scala:200— HuggingFaceInferenceOpDesc.generatePythonCode 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.
SQLSourceOpDesc.querySchema (cyclomatic 16) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpDesc.scala:140— SQLSourceOpDesc.querySchema 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.
workflow-crud-tools.createAddOperatorTool (cyclomatic 16) agent-service/src/agent/tools/workflow-crud-tools.ts:104— workflow-crud-tools.createAddOperatorTool has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 138). 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.
workflow-crud-tools.createModifyOperatorTool (cyclomatic 16) agent-service/src/agent/tools/workflow-crud-tools.ts:228— workflow-crud-tools.createModifyOperatorTool has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 254). 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.
operator-schema.interface.areOperatorSchemasEqual (cyclomatic 16) frontend/src/app/workspace/types/operator-schema.interface.ts:76— operator-schema.interface.areOperatorSchemasEqual 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.
WorkflowEditorComponent._handleKeyboardAction (cyclomatic 16) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:317— WorkflowEditorComponent._handleKeyboardAction has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 322). 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.
WorkflowFormComponent.renderField (cyclomatic 16) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:959— WorkflowFormComponent.renderField has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CollabWrapperComponent.setUpYTextEditor (cyclomatic 16) frontend/src/app/common/formly/collab-wrapper/collab-wrapper/collab-wrapper.component.ts:91— CollabWrapperComponent.setUpYTextEditor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 111, 92). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Skipped test: should debounce the user form input to avoid emitting event too frequently frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:393— Skipped — switched off by it.skip
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: mid-run state is GENERATING agent-service/src/agent/texera-agent.spec.ts:796— This test starts work it did not wait for (`p`, still running when the sleep starts) and then orders itself against it with `new Promise(r => setTimeout(r, 5))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Repeated repair: common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala:47— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is HuggingFaceCodegenBase.render at line 47), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(workflow-operator): degrade instead of raising on malformed chat responses (#8617)”; “fix(workflow-operator): carry structured task context into chat fallback payloads (#7798)”; “fix(workflow-operator): validate zero-shot-image-classification labels before running (#7585)”; “fix(workflow-operator): report a clear error when a configured HF image/audio column is missing (#7299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 23:55:13 +00:00' --until='2026-11-06 23:55:13 +00:00' --full-history --no-merges -- common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala`: 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.
shared-editing.interface.updateYTypeFromObject (cognitive 72) frontend/src/app/workspace/types/shared-editing.interface.ts:97— shared-editing.interface.updateYTypeFromObject has cognitive complexity 72 (threshold 15). Drivers by points: if/else 24 (51 pts), loops 6 (14 pts), boolean chains 4, ternaries 1 (2 pts), match/switch 1 (nesting depth added 36). Of this number, 61 points are the body's own statements and 11 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.
MyJsonFormatVisitorWrapper.expectObjectFormat (cognitive 65) common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1049— MyJsonFormatVisitorWrapper.expectObjectFormat has cognitive complexity 65 (threshold 15). Drivers by points: if/else 21 (46 pts), boolean chains 13, match/switch 2 (6 pts) (nesting depth added 29). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
RegexOpDesc.unicodeCase (cognitive 59) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:125— RegexOpDesc.unicodeCase has cognitive complexity 59 (threshold 15). Drivers by points: if/else 23 (44 pts), boolean chains 7, loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 26). 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.
concat_license_binary.parse (cognitive 50) bin/licensing/concat_license_binary.py:117— concat_license_binary.parse has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 6 (11 pts), boolean chains 9 (nesting depth added 24). 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.
concat_license_binary.merge (cognitive 50) bin/licensing/concat_license_binary.py:202— concat_license_binary.merge has cognitive complexity 50 (threshold 15). Drivers by points: loops 10 (25 pts), if/else 6 (24 pts), boolean chains 1 (nesting depth added 33). 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.
CollabWrapperComponent.setUpYTextEditor (cognitive 46) frontend/src/app/common/formly/collab-wrapper/collab-wrapper/collab-wrapper.component.ts:91— CollabWrapperComponent.setUpYTextEditor has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (38 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 26). None of this is in the body itself: all 46 points belong to 2 function literals inside it that branch (lines 111, 92). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ResourceUploadService.initUpload (cognitive 44) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:702— ResourceUploadService.initUpload has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (19 pts), error handling 6 (14 pts), boolean chains 6, match/switch 2 (5 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.
CollaborationResource.myOnMsg (cognitive 39) amber/src/main/scala/org/apache/texera/web/resource/CollaborationResource.scala:58— CollaborationResource.myOnMsg has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (25 pts), match/switch 3 (5 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 19). 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.
SyncExecutionResource.collectOperatorResult (cognitive 39) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:538— SyncExecutionResource.collectOperatorResult has cognitive complexity 39 (threshold 15). Drivers by points: loops 5 (18 pts), if/else 7 (13 pts), boolean chains 5, error handling 2, match/switch 1 (nesting depth added 19). 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.
DPThread.runDPThreadMainLogic (cognitive 37) amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DPThread.scala:134— DPThread.runDPThreadMainLogic has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 20). 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.
ArrowUtils.setTexeraTuple (cognitive 37) common/workflow-core/src/main/scala/org/apache/texera/amber/util/ArrowUtils.scala:276— ArrowUtils.setTexeraTuple has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (31 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_binary_deps.report (cognitive 36) bin/licensing/check_binary_deps.py:393— check_binary_deps.report has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 5 (12 pts), ternaries 3, 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.
TexeraAgent.sendMessage (cognitive 36) agent-service/src/agent/texera-agent.ts:496— TexeraAgent.sendMessage has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 8, error handling 3 (6 pts), ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 14). Most of this is not in the body itself: 10 of the 36 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 578, 548). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SharedModelChangeHandler.handleOperatorDeep (cognitive 36) frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts:283— SharedModelChangeHandler.handleOperatorDeep has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (33 pts), loops 1 (3 pts) (nesting depth added 18). None of this is in the body itself: all 36 points belong to one function literal inside it that branches (line 285). 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.
FiltersComponent.updateDropdownMenus (cognitive 36) REDACTED:304— FiltersComponent.updateDropdownMenus has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 24). None of this is in the body itself: all 36 points belong to one function literal inside it that branches (line 313). 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.
WorkflowVersionService.getWorkflowsDifference (cognitive 35) frontend/src/app/dashboard/service/user/workflow-version/workflow-version.service.ts:161— WorkflowVersionService.getWorkflowsDifference has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (24 pts), loops 5 (11 pts) (nesting depth added 23). Of this number, 32 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ComputingUnitManagingResource.createWorkflowComputingUnit (cognitive 34) computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:578— ComputingUnitManagingResource.createWorkflowComputingUnit has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (24 pts), error handling 3 (6 pts), boolean chains 2, match/switch 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.
workflow-execution-tools.executeOperatorAndFormat (cognitive 34) agent-service/src/agent/tools/workflow-execution-tools.ts:353— workflow-execution-tools.executeOperatorAndFormat has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 3 (6 pts), loops 2 (5 pts), boolean chains 4, error handling 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.
context-utils.serializeOperator (cognitive 34) agent-service/src/agent/util/context-utils.ts:218— context-utils.serializeOperator has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (8 pts), boolean chains 5, loops 2 (5 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.
WorkflowEditorComponent.handleHighlightMouseInput (cognitive 33) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1031— WorkflowEditorComponent.handleHighlightMouseInput has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (7 pts), boolean chains 1 (nesting depth added 18). None of this is in the body itself: all 33 points belong to 3 function literals inside it that branch (lines 1070, 1045, 1039). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RegexOpDesc.unicodeBoundaries (cognitive 31) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:189— RegexOpDesc.unicodeBoundaries has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 7, 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.
FileScanSourceOpDesc.generateStandaloneCode (cognitive 31) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:83— FileScanSourceOpDesc.generateStandaloneCode has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 2, match/switch 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.
AgentService.handleWebSocketMessage (cognitive 31) frontend/src/app/workspace/service/agent/agent.service.ts:448— AgentService.handleWebSocketMessage has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 5, match/switch 1 (nesting depth added 13). Of this number, 30 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
r-ui-udf-parameters-parser.parseRUiParameters (cognitive 31) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:147— r-ui-udf-parameters-parser.parseRUiParameters has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 3, loops 2 (3 pts) (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.
OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept (cognitive 31) frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:925— OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16, boolean chains 15. 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. This shape REPEATS in the file: one other method here (OperatorPropertyEditFrameComponent.setFormlyFormBinding) 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.
HuggingFaceInferenceOpDesc.generatePythonCode (cognitive 29) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/HuggingFaceInferenceOpDesc.scala:200— HuggingFaceInferenceOpDesc.generatePythonCode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 28, boolean chains 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.
ExecutorManager._explain_operator_count (cognitive 29) amber/src/main/python/core/architecture/managers/executor_manager.py:172— ExecutorManager._explain_operator_count has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 4 (8 pts), loops 2 (4 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.
LocalDevApp._dispatch (cognitive 29) bin/local-dev/tui.py:1388— LocalDevApp._dispatch has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 3, ternaries 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.
CostBasedScheduleGenerator.bottomUpSearch (cognitive 28) amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:387— CostBasedScheduleGenerator.bottomUpSearch has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 2 (6 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.
ResourceUploadService.uploadPart (cognitive 28) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:1235— ResourceUploadService.uploadPart has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 4, error handling 2, match/switch 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.
QueryWorkerStatisticsHandler.coordinatorInitiateQueryStatistics (cognitive 27) amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/promisehandlers/QueryWorkerStatisticsHandler.scala:80— QueryWorkerStatisticsHandler.coordinatorInitiateQueryStatistics has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 2 (4 pts), boolean chains 2, 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.
IcebergDocument.getUsingFileSequenceOrder (cognitive 27) common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/result/iceberg/IcebergDocument.scala:178— IcebergDocument.getUsingFileSequenceOrder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 4 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). 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.
IntervalJoinOpExec.processNumValue (cognitive 27) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/intervalJoin/IntervalJoinOpExec.scala:140— IntervalJoinOpExec.processNumValue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 7 (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.
AsterixDBSourceOpExec.produceTuple (cognitive 27) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpExec.scala:63— AsterixDBSourceOpExec.produceTuple has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TexeraAgent.getOperatorIdsFromStep (cognitive 26) agent-service/src/agent/texera-agent.ts:770— TexeraAgent.getOperatorIdsFromStep has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 8, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentInteractionComponent.getParsedColumnStats (cognitive 26) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:217— AgentInteractionComponent.getParsedColumnStats has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, ternaries 2 (5 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 10). Of this number, 25 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.
JSONUtils.JSONToMap (cognitive 25) common/workflow-core/src/main/scala/org/apache/texera/amber/util/JSONUtils.scala:106— JSONUtils.JSONToMap has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (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.
check_binary_deps.parse_prose (cognitive 25) bin/licensing/check_binary_deps.py:200— check_binary_deps.parse_prose has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (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.
SearchService.extendSearchResultsWithHubActivityInfo (cognitive 25) frontend/src/app/dashboard/service/user/search.service.ts:186— SearchService.extendSearchResultsWithHubActivityInfo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, ternaries 7, boolean chains 6. Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 249, 199, 208). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
loop-variable.util.splitStatements (cognitive 25) frontend/src/app/workspace/util/loop-variable.util.ts:202— loop-variable.util.splitStatements has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 6). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkflowCompilingService.dropInvalidAttributeValues (cognitive 25) frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:420— WorkflowCompilingService.dropInvalidAttributeValues has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 8). Of this number, 18 points are the body's own statements and 7 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.
WorkflowFormComponent.applyFieldOverrides::walk (cognitive 25) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1137— WorkflowFormComponent.applyFieldOverrides::walk has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (6 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PythonLexerUtils.updateTripleQuotedStringState (cognitive 24) common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala:50— PythonLexerUtils.updateTripleQuotedStringState has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, match/switch 1 (2 pts), 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.
CollaborationResource.myOnClose (cognitive 23) amber/src/main/scala/org/apache/texera/web/resource/CollaborationResource.scala:172— CollaborationResource.myOnClose has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 1 (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.
StableMergeSortOpExec.compareBySortKeys (cognitive 23) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/sort/StableMergeSortOpExec.scala:202— StableMergeSortOpExec.compareBySortKeys has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 2, 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.
SQLSourceOpExec.produceTuple (cognitive 23) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:52— SQLSourceOpExec.produceTuple has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (16 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Tuple.cast_to_schema (cognitive 23) REDACTED:308— Tuple.cast_to_schema has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 5, error handling 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.
tui._parse_sbt_deps (cognitive 23) bin/local-dev/tui.py:109— tui._parse_sbt_deps has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), ternaries 2 (6 pts), boolean chains 1, error handling 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.
SyncExecutionResource.executeWorkflowSync (cognitive 22) amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala:135— SyncExecutionResource.executeWorkflowSync has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, error handling 3 (5 pts), boolean chains 4, match/switch 2 (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.
FileScanOpDesc.generateStandaloneCode (cognitive 22) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:97— FileScanOpDesc.generateStandaloneCode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 2, match/switch 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.
SQLSourceOpExec.getNextQuery (cognitive 22) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:449— SQLSourceOpExec.getNextQuery has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 3 (9 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.
collect-licenses.walk (cognitive 22) agent-service/bin/collect-licenses.ts:58— collect-licenses.walk has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (4 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.
CoeditorPresenceService.updateCoeditorHighlightedOperators (cognitive 22) frontend/src/app/workspace/service/workflow-graph/model/coeditor-presence.service.ts:241— CoeditorPresenceService.updateCoeditorHighlightedOperators has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (6 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.
r-ui-udf-parameters-parser.readParameter (cognitive 22) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:120— r-ui-udf-parameters-parser.readParameter has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, ternaries 4, 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.
BufferedBlockReader.readLine (cognitive 21) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/BufferedBlockReader.java:52— BufferedBlockReader.readLine has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocalDevApp._tick_state (cognitive 21) bin/local-dev/tui.py:1193— LocalDevApp._tick_state has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
result-formatting.jsonToTableFormat (cognitive 21) agent-service/src/agent/tools/result-formatting.ts:140— result-formatting.jsonToTableFormat has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 162). 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.
ResultTableFrameComponent.ngOnInit (cognitive 21) REDACTED:171— ResultTableFrameComponent.ngOnInit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 6, loops 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 211, 189, 175, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
r-ui-udf-parameters-parser.tokenize (cognitive 21) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:66— r-ui-udf-parameters-parser.tokenize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (3 pts), boolean chains 1, 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.
CostBasedScheduleGenerator.topDownSearch (cognitive 20) amber/src/main/scala/org/apache/texera/amber/engine/architecture/scheduling/CostBasedScheduleGenerator.scala:550— CostBasedScheduleGenerator.topDownSearch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AggregateOpDesc.aggExprScalar (cognitive 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala:210— AggregateOpDesc.aggExprScalar has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 5 (9 pts), boolean chains 2 (nesting depth added 5). 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. This shape REPEATS in the file: one other method here (AggregateOpDesc.aggExprGroupby) 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.
AggregateOpDesc.aggExprGroupby (cognitive 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala:251— AggregateOpDesc.aggExprGroupby has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 5 (9 pts), boolean chains 2 (nesting depth added 5). 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. This shape REPEATS in the file: one other method here (AggregateOpDesc.aggExprScalar) 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.
FileScanUtils.createTuplesFromFile (cognitive 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanUtils.scala:70— FileScanUtils.createTuplesFromFile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 2 (4 pts), loops 1 (3 pts) (nesting depth added 6). 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.
PythonUDFOpDescV2.getPhysicalOp (cognitive 20) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:104— PythonUDFOpDescV2.getPhysicalOp has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 1 (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.
workflow-crud-tools.createModifyOperatorTool (cognitive 20) agent-service/src/agent/tools/workflow-crud-tools.ts:228— workflow-crud-tools.createModifyOperatorTool has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (5 pts), loops 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 5). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 254). 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.
SharedModelChangeHandler.handlePortEvent (cognitive 20) frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts:370— SharedModelChangeHandler.handlePortEvent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultipartUploadService.multipartUpload (cognitive 20) frontend/src/app/dashboard/service/user/file-resource/multipart-upload.service.ts:57— MultipartUploadService.multipartUpload has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 6, boolean chains 2, error handling 1 (nesting depth added 1). None of this is in the body itself: all 20 points belong to 8 function literals inside it that branch (lines 89, 208, 86, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CoeditorPresenceService.observeUserState (cognitive 20) frontend/src/app/workspace/service/workflow-graph/model/coeditor-presence.service.ts:101— CoeditorPresenceService.observeUserState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5, boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 117, 109). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FilesUploaderComponent.addSelection (cognitive 20) frontend/src/app/dashboard/component/user/files-uploader/files-uploader.component.ts:356— FilesUploaderComponent.addSelection has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 4 (6 pts), boolean chains 2 (nesting depth added 8). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 358). 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.
AccessControlResource.extractTokenFromBody (cognitive 19) access-control-service/src/main/scala/org/apache/texera/service/resource/AccessControlResource.scala:220— AccessControlResource.extractTokenFromBody has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, error handling 1, 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.
ClientActor.receive (cognitive 19) amber/src/main/scala/org/apache/texera/amber/engine/common/client/ClientActor.scala:100— ClientActor.receive has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 5 (8 pts) (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.
ExecutionResultService.attachToExecution (cognitive 19) amber/src/main/scala/org/apache/texera/web/service/ExecutionResultService.scala:272— ExecutionResultService.attachToExecution has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StagedFileCleanupJob.runCleanupOnce (cognitive 19) file-service/src/main/scala/org/apache/texera/service/util/StagedFileCleanupJob.scala:138— StagedFileCleanupJob.runCleanupOnce has cognitive complexity 19 (threshold 15). Drivers by points: error handling 6 (9 pts), if/else 4 (7 pts), boolean chains 2, match/switch 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.
WorkflowToPythonTranslator.splitOffLiterals (cognitive 19) workflow-compiling-service/src/main/scala/org/apache/texera/amber/translator/WorkflowToPythonTranslator.scala:391— WorkflowToPythonTranslator.splitOffLiterals has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 1, 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.
release_branches.parse (cognitive 19) .github/scripts/release_branches.py:49— release_branches.parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InternalQueue.put (cognitive 19) amber/src/main/python/core/models/internal_queue.py:76— InternalQueue.put has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MainLoop._process_ecm (cognitive 19) amber/src/main/python/core/runnables/main_loop.py:677— MainLoop._process_ecm has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
concat_license_binary.emit (cognitive 19) bin/licensing/concat_license_binary.py:257— concat_license_binary.emit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 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.
generate_notice_binary.artifact_label (cognitive 19) bin/licensing/generate_notice_binary.py:117— generate_notice_binary.artifact_label has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 2 (3 pts), error handling 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.
ResultPanelComponent.rerenderResultPanel (cognitive 19) frontend/src/app/workspace/component/result-panel/result-panel.component.ts:348— ResultPanelComponent.rerenderResultPanel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StateReferenceBinding.write (cognitive 18) common/workflow-core/src/main/scala/org/apache/texera/amber/core/executor/StateReferenceBinding.scala:63— StateReferenceBinding.write has cognitive complexity 18 (threshold 15). Drivers by points: error handling 2 (6 pts), loops 4 (6 pts), if/else 3 (5 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.
TupleUtils.convertTuplesToJson (cognitive 18) common/workflow-core/src/main/scala/org/apache/texera/amber/core/tuple/TupleUtils.scala:62— TupleUtils.convertTuplesToJson has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (6 pts), boolean chains 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.
SklearnMLOperatorDescriptor.paramConstants (cognitive 18) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/base/SklearnAdvancedBaseDesc.scala:241— SklearnMLOperatorDescriptor.paramConstants has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 2 (6 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.
DualInputPortsPythonUDFOpDescV2.getPhysicalOp (cognitive 18) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/DualInputPortsPythonUDFOpDescV2.scala:105— DualInputPortsPythonUDFOpDescV2.getPhysicalOp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (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.
WorkflowToPythonTranslator.translate (cognitive 18) workflow-compiling-service/src/main/scala/org/apache/texera/amber/translator/WorkflowToPythonTranslator.scala:48— WorkflowToPythonTranslator.translate has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (9 pts), if/else 7 (8 pts), loops 1 (nesting depth added 4). 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.
workflow-crud-tools.createAddOperatorTool (cognitive 18) agent-service/src/agent/tools/workflow-crud-tools.ts:104— workflow-crud-tools.createAddOperatorTool has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (5 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 138). 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.
shared-editing.interface.createYTypeFromObject (cognitive 18) frontend/src/app/workspace/types/shared-editing.interface.ts:50— shared-editing.interface.createYTypeFromObject has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 8). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
loop-variable.util.extractLoopVariables (cognitive 18) frontend/src/app/workspace/util/loop-variable.util.ts:119— loop-variable.util.extractLoopVariables has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 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.
WorkflowResultExportService.performExport (cognitive 18) frontend/src/app/workspace/service/workflow-result-export/workflow-result-export.service.ts:243— WorkflowResultExportService.performExport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 3). Of this number, 12 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
script-segmentation.segmentScript (cognitive 18) frontend/src/app/workspace/service/notebook-migration/script-segmentation.ts:145— script-segmentation.segmentScript has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 6 (7 pts), boolean chains 2 (nesting depth added 5). 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 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.
MachineLearningScorerOpDesc.validateScoredColumns (cognitive 17) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/Scorer/MachineLearningScorerOpDesc.scala:137— MachineLearningScorerOpDesc.validateScoredColumns 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.
SQLSourceOpExec.initBatchColumnBoundaries (cognitive 17) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:498— SQLSourceOpExec.initBatchColumnBoundaries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 6). 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.
ComputingUnitHelpers.kubernetesStatusAndReason (cognitive 17) computing-unit-managing-service/src/main/scala/org/apache/texera/service/util/ComputingUnitHelpers.scala:164— ComputingUnitHelpers.kubernetesStatusAndReason has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 3). 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.
ResourceUploadService.uploadOneFile (cognitive 17) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:555— ResourceUploadService.uploadOneFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 2 (4 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
result-formatting.formatOperatorResult (cognitive 17) agent-service/src/agent/tools/result-formatting.ts:57— result-formatting.formatOperatorResult has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 77). 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.
loop-block.util.enclosingLoopStarts (cognitive 17) frontend/src/app/workspace/util/loop-block.util.ts:51— loop-block.util.enclosingLoopStarts has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (5 pts), boolean chains 3, loops 3 (nesting depth added 4). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 85, 57, 98, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ValidationWorkflowService.validateOperatorConnection (cognitive 17) frontend/src/app/workspace/service/validation/validation-workflow.service.ts:348— ValidationWorkflowService.validateOperatorConnection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (nesting depth added 6). 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.
WorkflowVersionService.unhighlightOpVersionDiff (cognitive 17) frontend/src/app/dashboard/service/user/workflow-version/workflow-version.service.ts:270— WorkflowVersionService.unhighlightOpVersionDiff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (4 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.
WorkflowEditorComponent._handleKeyboardAction (cognitive 17) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:317— WorkflowEditorComponent._handleKeyboardAction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7 (nesting depth added 5). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 322). 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.
hugging-face-field-bindings.applyHuggingFaceFieldBindings (cognitive 17) frontend/src/app/workspace/util/hugging-face-field-bindings.ts:116— hugging-face-field-bindings.applyHuggingFaceFieldBindings has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 6. Of this number, 13 points are the body's own statements and 4 belong to 4 function literals inside it that branch. 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.
OperatorPropertyEditFrameComponent.setFormlyFormBinding (cognitive 17) frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:905— OperatorPropertyEditFrameComponent.setFormlyFormBinding has cognitive complexity 17 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 20, loops 1 (2 pts), ternaries 1 (nesting depth added 9). 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. This shape REPEATS in the file: one other method here (OperatorPropertyEditFrameComponent.setFormlyFormBinding::jsonSchemaMapIntercept) 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.
formly-utils.createValueRulesValidator.<returned closure> (cognitive 17) REDACTED:71— formly-utils.createValueRulesValidator.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6 (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.
JavaUDFOpDesc.getPhysicalOp (cognitive 16) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:74— JavaUDFOpDesc.getPhysicalOp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (3 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.
RUDFOpDesc.getPhysicalOp (cognitive 16) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:77— RUDFOpDesc.getPhysicalOp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (3 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.
TypeAnnotationVisitor.process_function (cognitive 16) amber/src/main/scala/org/apache/texera/web/resource/aiassistant/type_annotation_visitor.py:48— TypeAnnotationVisitor.process_function has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, loops 2 (3 pts) (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.
check_binary_deps.main (cognitive 16) bin/licensing/check_binary_deps.py:564— check_binary_deps.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 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.
LocalDevApp._refresh_table (cognitive 16) bin/local-dev/tui.py:1140— LocalDevApp._refresh_table has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, ternaries 1 (3 pts), 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.
workflow-crud-tools.resolveInputLinks (cognitive 16) agent-service/src/agent/tools/workflow-crud-tools.ts:64— workflow-crud-tools.resolveInputLinks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.buildApp (cognitive 16) agent-service/src/server.ts:437— server.buildApp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
search-filter-parameters.searchTestEntries (cognitive 16) frontend/src/app/dashboard/type/search-filter-parameters.ts:83— search-filter-parameters.searchTestEntries has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 7. 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.
SharedModelChangeHandler.handleCommentBoxDeep (cognitive 16) frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts:473— SharedModelChangeHandler.handleCommentBoxDeep has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 475). 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.
DragDropService.findClosestOperators (cognitive 16) frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:223— DragDropService.findClosestOperators has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 16 points belong to 2 function items inside it that branch (a function literal at line 266, greatestDistance). 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.
loop-variable-field.util.coerceOrReference (cognitive 16) frontend/src/app/workspace/util/loop-variable-field.util.ts:89— loop-variable-field.util.coerceOrReference has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 3, boolean chains 1, match/switch 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.
loop-variable-field.util.inheritNoLoopVariable (cognitive 16) frontend/src/app/workspace/util/loop-variable-field.util.ts:213— loop-variable-field.util.inheritNoLoopVariable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2, boolean chains 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (visit, markedRef). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
WorkflowVersionService.highlightOpVersionDiff (cognitive 16) frontend/src/app/dashboard/service/user/workflow-version/workflow-version.service.ts:125— WorkflowVersionService.highlightOpVersionDiff has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (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.
WorkflowEditorComponent.handleOperatorChatButton (cognitive 16) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1972— WorkflowEditorComponent.handleOperatorChatButton has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 1978, 2023, 2041, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CoeditorPresenceService.updateCoeditorOpenAndCloseCode (cognitive 16) frontend/src/app/workspace/service/workflow-graph/model/coeditor-presence.service.ts:313— CoeditorPresenceService.updateCoeditorOpenAndCloseCode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2 (nesting depth added 8). 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.
python-ui-udf-parameters-parser.insertIntoBody (cognitive 16) frontend/src/app/workspace/service/code-editor/python-ui-udf-parameters-parser.ts:176— python-ui-udf-parameters-parser.insertIntoBody has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 3 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
r-ui-udf-parameters-parser.computeRParameterInsertion (cognitive 16) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:184— r-ui-udf-parameters-parser.computeRParameterInsertion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, 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.
FunctionTooLong: shared-editing.interface.updateYTypeFromObject frontend/src/app/workspace/types/shared-editing.interface.ts:97— FunctionTooLong — updateYTypeFromObject runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Change coupling clique: ComputingUnitManagingService.scala, ConfigService.scala, WorkflowCompilingService.scala computing-unit-managing-service/src/main/scala/org/apache/texera/service/ComputingUnitManagingService.scala— 3 files — `computing-unit-managing-service/src/main/scala/org/apache/texera/service/ComputingUnitManagingService.scala`, `config-service/src/main/scala/org/apache/texera/service/ConfigService.scala`, `workflow-compiling-service/src/main/scala/org/apache/texera/service/WorkflowCompilingService.scala` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Near-duplicate member pair (26 shared lines) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:84— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:84-122 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:74-113 — These two members are variants of one another: 26 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:68— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:68-82 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:58-72 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/URLFetcherOpDesc.scala:74-90 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:65-86 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:62-82 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:62-78 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:186-202 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/text/TextInputSourceOpDesc.scala:50-64 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/postgresql/PostgreSQLSourceOpDesc.scala:51-65 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dummy/DummyOpDesc.scala:40— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dummy/DummyOpDesc.scala:40-73 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:139-172 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:181-214 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:139-170 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (37–45 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:207— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:207-251 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:124-160 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:207` 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 (33–35 lines × 2) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:997— file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:997-1031 | file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:1178-1210 — 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 `file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:997` 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 (24–28 lines × 2) amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:210— amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:210-233 | amber/src/main/scala/org/apache/texera/web/TexeraWebApplication.scala:173-200 — 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 `amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:210` 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 (24 lines × 4) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dummy/DummyOpDesc.scala:41— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dummy/DummyOpDesc.scala:41-64 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:140-163 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:182-205 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:140-163 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dummy/DummyOpDesc.scala:41` 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–20 lines × 3) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:162— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:162-180 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:96-113 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:92-111 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:118— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:118-136 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:90-108 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 before the matched lines, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:115` calls `injectUiParameters` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:87` 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 (17–18 lines × 2) REDACTED:423— REDACTED:423-439 | REDACTED:500-517 — 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:423` 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 (16 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:93— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:93-108 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpExec.scala:93-108 — 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpExec.scala:93` 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 (15 lines × 9) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:68— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:68-82 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:58-72 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/URLFetcherOpDesc.scala:75-89 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:71-85 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:67-81 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:63-77 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala:187-201 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/text/TextInputSourceOpDesc.scala:50-64 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/postgresql/PostgreSQLSourceOpDesc.scala:51-65 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:67` calls `forall`, `Option` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/fetcher/URLFetcherOpDesc.scala:74` 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 (14 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:79— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:79-92 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:82-95 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:79` 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–14 lines × 2) REDACTED:233— REDACTED:233-246 | REDACTED:298-308 — 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:233` 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 × 3) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:89— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala:89-101 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:176-188 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:163-175 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/CSVScanSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csv/ParallelCSVScanSourceOpDesc.scala:172` calls `mkString` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/csvOld/CSVOldScanSourceOpDesc.scala:159` 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 × 2) amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala:154— amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala:154-165 | amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala:228-240 — 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 `amber/src/main/scala/org/apache/texera/amber/engine/architecture/pythonworker/PythonProxyClient.scala:154` 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) common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:728— common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:728-740 | common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:788-800 — 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 `common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:728` 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–12 lines × 2) common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:251— common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:251-262 | common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:272-280 — 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 `common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PhysicalPlan.scala:251` 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 (12 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:88— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:88-99 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:79-90 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 (9–10 lines × 3) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:86— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:86-95 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:117-125 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:89-97 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala: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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:115` calls `injectUiParameters` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:84` 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.
Duplicated block (10 lines × 3) REDACTED:312— REDACTED:312-321 | REDACTED:421-430 | REDACTED:498-507 — 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 `REDACTED:312` 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 after the matched lines, `REDACTED:322` calls `get` and `REDACTED:432` 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 (7–10 lines × 2) file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:454— file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:454-460 | file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:538-547 — 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 `file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala:454` 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 (7 lines × 3) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:78— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:78-84 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:108-114 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/r/RUDFOpDesc.scala:81-87 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUDFOpDescV2.scala:115` calls `injectUiParameters` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/java/JavaUDFOpDesc.scala:86` 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.
Duplicated block (6 lines × 4) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:89— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:89-94 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:105-110 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:80-85 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala:96-101 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterSearchSourceOpDesc.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/apis/twitter/v2/TwitterFullArchiveSearchSourceOpDesc.scala:89` 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) amber/src/main/scala/org/apache/texera/web/resource/dashboard/WorkflowSearchQueryBuilder.scala:93— amber/src/main/scala/org/apache/texera/web/resource/dashboard/WorkflowSearchQueryBuilder.scala:93-97 | amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowResource.scala:292-296 — 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 `amber/src/main/scala/org/apache/texera/web/resource/dashboard/WorkflowSearchQueryBuilder.scala:93` 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 × 3) access-control-service/src/main/scala/org/apache/texera/service/AccessControlService.scala:40— access-control-service/src/main/scala/org/apache/texera/service/AccessControlService.scala:40-56 | config-service/src/main/scala/org/apache/texera/service/ConfigService.scala:37-53 | notebook-migration-service/src/main/scala/org/apache/texera/service/NotebookMigrationService.scala:43-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (14 lines × 6) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/SpecializedFilterOpDesc.scala:43— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/SpecializedFilterOpDesc.scala:43-56 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/keywordSearch/KeywordSearchOpDesc.scala:66-79 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/randomksampling/RandomKSamplingOpDesc.scala:40-53 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:54-67 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/reservoirsampling/ReservoirSamplingOpDesc.scala:39-52 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/substringSearch/SubstringSearchOpDesc.scala:66-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/SpecializedFilterOpDesc.scala:43` 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) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/keywordSearch/KeywordSearchOpDesc.scala:82— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/keywordSearch/KeywordSearchOpDesc.scala:82-89 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala:70-77 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/substringSearch/SubstringSearchOpDesc.scala:82-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (35 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/IcicleChart/IcicleChartOpDesc.scala:129— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/IcicleChart/IcicleChartOpDesc.scala:129-163 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/hierarchychart/HierarchyChartOpDesc.scala:134-168 — before extracting anything, compare `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/IcicleChart/IcicleChartOpDesc.scala` and `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/visualization/hierarchychart/HierarchyChartOpDesc.scala` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (70 lines × 3) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/KNNTrainer/SklearnAdvancedKNNParameters.java:1— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/KNNTrainer/SklearnAdvancedKNNParameters.java:1-70 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVCTrainer/SklearnAdvancedSVCParameters.java:1-76 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVRTrainer/SklearnAdvancedSVRParameters.java:1-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/KNNTrainer/SklearnAdvancedKNNParameters.java:1` 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 (76 lines × 2) common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVCTrainer/SklearnAdvancedSVCParameters.java:1— common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVCTrainer/SklearnAdvancedSVCParameters.java:1-76 | common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVRTrainer/SklearnAdvancedSVRParameters.java:1-77 — 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 `common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/SVCTrainer/SklearnAdvancedSVCParameters.java:1` 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.
Skeleton type — most members are unfinished amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/DataProcessorRPCHandlerInitializer.scala:42— `DataProcessorRPCHandlerInitializer` has 4 unfinished members out of 5 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 4 sibling directories (32 clone groups) frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146— 32 duplicated blocks under frontend/src/app/ have copies in at least two of the sibling directories common, dashboard, hub, workspace — 17 of them are reported below, and 15 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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 15 sibling directories (17 clone groups) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:55— 17 duplicated blocks under frontend/src/app/workspace/component/ have copies in at least two of the sibling directories agent, code-editor-dialog, dataset-file-selector, dataset-selection-modal, dataset-version-selector, hugging-face-audio-upload (+9 more sibling(s) not listed) — 7 of them are reported below, and 10 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 11 sibling directories (13 clone groups) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103— 13 duplicated blocks under frontend/src/app/dashboard/component/user/ have copies in at least two of the sibling directories files-uploader, list-item, markdown-description, share-access, user-computing-unit, user-dataset (+5 more sibling(s) not listed) — 9 of them are reported below, and 4 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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 2 sibling directories (6 clone groups) agent-service/src/agent/util/workflow-utils.ts:65— 6 duplicated blocks under the repository root have copies in at least two of the sibling directories agent-service, frontend — 4 of them are reported below, and 2 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 6 and which does not depend on how exactly each block's copies still match. 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.
Duplication concentrated across 2 sibling directories (5 clone groups) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:392— 5 duplicated blocks under frontend/src/app/workspace/ have copies in at least two of the sibling directories component, service — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 (198 matched lines × 2 locations) · ×1
Duplicated block with local edits (198 matched lines × 2 locations) frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:233— frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:233 · frontend/src/app/dashboard/component/user/list-item/list-item.component.ts:149 — the two spans are one implementation copied and then locally edited — 1352 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 (179 matched lines × 2 locations) · ×1
Duplicated block with local edits (179 matched lines × 2 locations) frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103— frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:103 · frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:92 — the two spans are one implementation copied and then locally edited — 1061 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 (127 matched lines × 2 locations) · ×1
Duplicated block with local edits (127 matched lines × 2 locations) frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:34— frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:34 · frontend/src/app/dashboard/service/user/model/model.service.ts:29 — the two spans are one implementation copied and then locally edited — 884 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 (68 matched lines × 2 locations) · ×1
Duplicated block with local edits (68 matched lines × 2 locations) frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146— frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:146 · REDACTED:755 — the two spans are one implementation copied and then locally edited — 407 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (51 lines × 2 locations) frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:54— frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:54 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:51 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (41 lines × 2 locations) frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:263— frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:263 · REDACTED:856 — 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 (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:154— frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:154 · frontend/src/app/hub/component/hub-search-result/hub-search-result.component.ts:99 — the two spans are one implementation copied and then locally edited — 288 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 (32 lines × 2 locations) frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1441— frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1441 · frontend/src/app/workspace/component/property-editor/port-property-edit-frame/port-property-edit-frame.component.ts:235 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (26 lines × 2 locations) frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:130— frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:130 · frontend/src/app/dashboard/component/user-dashboard-test-fixtures.ts:157 — 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.
R10 · Code Duplication· Duplicated block with local edits (24 matched lines × 2 locations) · ×1
Duplicated block with local edits (24 matched lines × 2 locations) agent-service/src/agent/tools/workflow-crud-tools.ts:156— agent-service/src/agent/tools/workflow-crud-tools.ts:156 · agent-service/src/agent/tools/workflow-crud-tools.ts:268 — the two spans are one implementation copied and then locally edited — 183 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:145— frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:145 · frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:224 — 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 (18 lines × 3 locations) frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit.component.ts:71— frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit.component.ts:71 · frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:114 · frontend/src/app/dashboard/component/user/user-model/user-model.component.ts:111 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 2 locations) frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:697— frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:697 · frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:730 — 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 (15 lines × 2 locations) frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:483— frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:483 · frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:537 — 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 (14 lines × 2 locations) frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:270— frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:270 · frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:288 — 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.
Complex function updateYTypeFromObject (cyclomatic 38, cognitive 62) frontend/src/app/workspace/types/shared-editing.interface.ts:97— updateYTypeFromObject has cyclomatic complexity 38 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 25) frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:928— (anonymous) has cyclomatic complexity 31 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 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 (anonymous) (cyclomatic 29, cognitive 35) frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1137— (anonymous) has cyclomatic complexity 29 and cognitive complexity 35; 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 executeOperatorAndFormat (cyclomatic 24, cognitive 35) agent-service/src/agent/tools/workflow-execution-tools.ts:353— executeOperatorAndFormat has cyclomatic complexity 24 and cognitive complexity 35; 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 getRunButtonBehavior (cyclomatic 23, cognitive 12) frontend/src/app/workspace/component/menu/menu.component.ts:436— getRunButtonBehavior has cyclomatic complexity 23 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function serializeOperator (cyclomatic 21, cognitive 34) agent-service/src/agent/util/context-utils.ts:218— serializeOperator has cyclomatic complexity 21 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 readParameter (cyclomatic 21, cognitive 23) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:120— readParameter has cyclomatic complexity 21 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 handleWebSocketMessage (cyclomatic 20, cognitive 30) frontend/src/app/workspace/service/agent/agent.service.ts:448— handleWebSocketMessage has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function dropInvalidAttributeValues (cyclomatic 20, cognitive 21) frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:420— dropInvalidAttributeValues 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.
Complex function getOperatorIdsFromStep (cyclomatic 19, cognitive 26) agent-service/src/agent/texera-agent.ts:770— getOperatorIdsFromStep has cyclomatic complexity 19 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 splitStatements (cyclomatic 19, cognitive 24) frontend/src/app/workspace/util/loop-variable.util.ts:202— splitStatements has cyclomatic complexity 19 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 getParsedColumnStats (cyclomatic 18, cognitive 27) frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts:217— getParsedColumnStats has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 16) frontend/src/app/dashboard/service/user/search.service.ts:249— (anonymous) has cyclomatic complexity 18 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 (anonymous) (cyclomatic 17, cognitive 36) REDACTED:313— (anonymous) has cyclomatic complexity 17 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 parseRUiParameters (cyclomatic 17, cognitive 31) frontend/src/app/workspace/service/code-editor/r-ui-udf-parameters-parser.ts:147— parseRUiParameters has cyclomatic complexity 17 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 16) REDACTED:71— (anonymous) has cyclomatic complexity 17 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 execute (cyclomatic 16, cognitive 20) agent-service/src/agent/tools/workflow-crud-tools.ts:254— execute has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 16) frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:322— (anonymous) has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createYTypeFromObject (cyclomatic 16, cognitive 15) frontend/src/app/workspace/types/shared-editing.interface.ts:50— createYTypeFromObject has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function areOperatorSchemasEqual (cyclomatic 16, cognitive 14) frontend/src/app/workspace/types/operator-schema.interface.ts:76— areOperatorSchemasEqual has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts · ×1
frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts: 2100 lines of code frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts:1— frontend/src/app/workspace/component/workflow-form/workflow-form.component.ts has 2100 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· frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts · ×1
frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts: 2026 lines of code frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts:1— frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.ts has 2026 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· frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts · ×1
frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts: 1375 lines of code frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts:1— frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.ts has 1375 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: 1241 lines of code REDACTED:1— REDACTED has 1241 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· frontend/src/app/workspace/service/agent/agent.service.ts · ×1
frontend/src/app/workspace/service/agent/agent.service.ts: 1145 lines of code frontend/src/app/workspace/service/agent/agent.service.ts:1— frontend/src/app/workspace/service/agent/agent.service.ts has 1145 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· frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts · ×1
frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts: 1142 lines of code frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:1— frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts has 1142 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· frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts · ×1
frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts: 1065 lines of code frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:1— frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts has 1065 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· frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts · ×1
frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts: 1056 lines of code frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts:1— frontend/src/app/workspace/service/joint-ui/joint-ui.service.ts has 1056 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· frontend/src/app/workspace/component/menu/menu.component.ts · ×1
frontend/src/app/workspace/component/menu/menu.component.ts: 1053 lines of code frontend/src/app/workspace/component/menu/menu.component.ts:1— frontend/src/app/workspace/component/menu/menu.component.ts has 1053 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· frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts · ×1
frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts: 927 lines of code frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts:1— frontend/src/app/workspace/service/workflow-graph/model/joint-graph-wrapper.ts has 927 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· frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts · ×1
frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts: 748 lines of code frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:1— frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts has 748 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· frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts · ×1
frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts: 735 lines of code frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts:1— frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts has 735 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· agent-service/src/agent/texera-agent.ts · ×1
agent-service/src/agent/texera-agent.ts: 729 lines of code agent-service/src/agent/texera-agent.ts:1— agent-service/src/agent/texera-agent.ts has 729 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· frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts · ×1
frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts: 715 lines of code frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts:1— frontend/src/app/workspace/service/notebook-migration/migration-prompts.ts has 715 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· frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts · ×1
frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts: 622 lines of code frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts:1— frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts has 622 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· frontend/src/app/workspace/service/notebook-migration/migration-llm.ts · ×1
frontend/src/app/workspace/service/notebook-migration/migration-llm.ts: 620 lines of code frontend/src/app/workspace/service/notebook-migration/migration-llm.ts:1— frontend/src/app/workspace/service/notebook-migration/migration-llm.ts has 620 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· frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts · ×1
frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts: 618 lines of code frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts:1— frontend/src/app/workspace/component/code-editor-dialog/code-editor.component.ts has 618 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· frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts · ×1
frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts: 615 lines of code frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:1— frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts has 615 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· frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts · ×1
frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts: 613 lines of code frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts:1— frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts has 613 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· frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts · ×1
frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts: 591 lines of code frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts:1— frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts has 591 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· agent-service/src/server.ts · ×1
agent-service/src/server.ts: 559 lines of code agent-service/src/server.ts:1— agent-service/src/server.ts has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts · ×1
frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts: 547 lines of code frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts:1— frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.ts has 547 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· frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts · ×1
frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts: 539 lines of code frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts:1— frontend/src/app/workspace/service/drag-drop/drag-drop.service.ts has 539 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: 523 lines of code REDACTED:1— REDACTED has 523 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· frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts · ×1
frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts: 515 lines of code frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts:1— frontend/src/app/workspace/component/result-panel/ai-fix/ai-workflow-fixer.service.ts has 515 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· frontend/src/app/workspace/component/result-panel/result-panel.component.ts · ×1
frontend/src/app/workspace/component/result-panel/result-panel.component.ts: 508 lines of code frontend/src/app/workspace/component/result-panel/result-panel.component.ts:1— frontend/src/app/workspace/component/result-panel/result-panel.component.ts has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 492 lines of code REDACTED:1— REDACTED has 492 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· frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts · ×1
frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts: 472 lines of code frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts:1— frontend/src/app/workspace/service/workflow-graph/model/shared-model-change-handler.ts has 472 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· frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts · ×1
frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts: 466 lines of code frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts:1— frontend/src/app/workspace/service/compile-workflow/workflow-compiling.service.ts has 466 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· frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts · ×1
frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts: 454 lines of code frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:1— frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.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· frontend/src/app/workspace/service/report-generation/report-generation.service.ts · ×1
frontend/src/app/workspace/service/report-generation/report-generation.service.ts: 451 lines of code frontend/src/app/workspace/service/report-generation/report-generation.service.ts:1— frontend/src/app/workspace/service/report-generation/report-generation.service.ts has 451 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· frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts · ×1
frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts: 441 lines of code frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts:1— frontend/src/app/dashboard/component/user/version-uploader/version-uploader.component.ts has 441 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· frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts · ×1
frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts: 420 lines of code frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts:1— frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts 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· frontend/src/app/app.module.ts · ×1
frontend/src/app/app.module.ts: 419 lines of code frontend/src/app/app.module.ts:1— frontend/src/app/app.module.ts has 419 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· frontend/src/app/common/service/user/auth.service.ts · ×1
frontend/src/app/common/service/user/auth.service.ts: 417 lines of code frontend/src/app/common/service/user/auth.service.ts:1— frontend/src/app/common/service/user/auth.service.ts has 417 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· frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts · ×1
frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts: 413 lines of code frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts:1— frontend/src/app/workspace/component/workflow-form/workflow-form.spec-harness.ts has 413 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· agent-service/src/agent/tools/workflow-execution-tools.ts · ×1
agent-service/src/agent/tools/workflow-execution-tools.ts: 408 lines of code agent-service/src/agent/tools/workflow-execution-tools.ts:1— agent-service/src/agent/tools/workflow-execution-tools.ts has 408 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· frontend/src/app/workspace/component/workspace.component.ts · ×1
frontend/src/app/workspace/component/workspace.component.ts: 407 lines of code frontend/src/app/workspace/component/workspace.component.ts:1— frontend/src/app/workspace/component/workspace.component.ts has 407 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· frontend/src/app/dashboard/component/user/share-access/share-access.component.ts · ×1
frontend/src/app/dashboard/component/user/share-access/share-access.component.ts: 404 lines of code frontend/src/app/dashboard/component/user/share-access/share-access.component.ts:1— frontend/src/app/dashboard/component/user/share-access/share-access.component.ts has 404 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 (~353 LoC) frontend/src/jsdom-svg-polyfill.ts— no import path from any entry point (14 application, 11 tooling, 276 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'pino-pretty' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular-devkit/build-angular' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular-devkit/core' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Third-party script without Subresource Integrity frontend/src/index.html:66— `https://cdn.jsdelivr.net/npm/jsoneditor@10.1.0/dist/jsoneditor.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session.
Mock-dominated test: warns when adding the pasted operators and links fails frontend/src/app/workspace/service/operator-menu/operator-menu.service.spec.ts:440— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not postMessage for an unsaved workflow (undefined wid) frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.spec.ts:613— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not postMessage when the workflow has no stored mapping frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.spec.ts:627— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: re-paints every input and output port label to the state's fill color frontend/src/app/workspace/service/joint-ui/joint-ui.service.spec.ts:612— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: renders nothing when statistics is undefined (state is rendered separately) frontend/src/app/workspace/service/joint-ui/joint-ui.service.spec.ts:746— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: leaves the port labels untouched when the metrics maps are absent frontend/src/app/workspace/service/joint-ui/joint-ui.service.spec.ts:834— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does nothing for an unsaved workflow (no wid) frontend/src/app/workspace/service/heatmap/heatmap-stats-restore.service.spec.ts:141— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: skips the restore while an execution is in progress, so the live stream wins frontend/src/app/workspace/service/heatmap/heatmap-stats-restore.service.spec.ts:150— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: drops the restore when a run starts while the fetches are in flight frontend/src/app/workspace/service/heatmap/heatmap-stats-restore.service.spec.ts:180— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: swallows an HTTP error from the executions fetch frontend/src/app/workspace/service/heatmap/heatmap-stats-restore.service.spec.ts:233— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: swallows an HTTP error from the statistics fetch frontend/src/app/workspace/service/heatmap/heatmap-stats-restore.service.spec.ts:245— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should execute workflow with email notification successfully frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.spec.ts:289— This test sets up 5 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: executeWorkflowWithReplay builds a replay request and forwards the replay info frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.spec.ts:492— This test sets up 4 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: a refused run leaves the previous execution's state untouched (#7817) frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.spec.ts:532— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ${entryPoint.name} refuses a %s unit and keeps the previous results on screen frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.spec.ts:611— This test sets up 5 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ${entryPoint.name} still runs on a %s unit frontend/src/app/workspace/service/execute-workflow/execute-workflow.service.spec.ts:631— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: flags broken workflows via NotificationService.error but still loads them frontend/src/app/workspace/component/workspace.component.spec.ts:328— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: when URL fragment does not match any element, surfaces an error and clears the fragment frontend/src/app/workspace/component/workspace.component.spec.ts:376— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: skips the URL update when the persisted wid matches the current metadata frontend/src/app/workspace/component/workspace.component.spec.ts:430— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not persist an edit made by a signed-out visitor frontend/src/app/workspace/component/workspace.component.spec.ts:451— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not persist when workflow persistence is switched off frontend/src/app/workspace/component/workspace.component.spec.ts:472— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: skips the persist call when the user is not signed in frontend/src/app/workspace/component/workspace.component.spec.ts:547— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: tears down every piece of websocket-derived state when leaving the workspace (issue #3120) frontend/src/app/workspace/component/workspace.component.spec.ts:557— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: saves on beforeunload and tears nothing down, so a page restored from the cache still works frontend/src/app/workspace/component/workspace.component.spec.ts:575— This test sets up 6 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: keeps the session when this workflow's Form View takes over frontend/src/app/workspace/component/workspace.component.spec.ts:592— This test sets up 6 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Orphaned file frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.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 agent-service/src/agent/prompts.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 frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.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 agent-service/src/agent/util/context-utils.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 amber/src/main/scala/org/apache/texera/web/resource/aiassistant/AiAssistantResource.scala: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 frontend/src/app/workspace/component/agent/agent-panel/react-step-detail-modal/react-step-detail-modal.component.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 agent-service/src/agent/util/workflow-utils.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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/FilterPredicate.java: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 frontend/src/app/workspace/component/left-panel/time-travel/time-travel.component.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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dictionary/DictionaryMatcherOpExec.scala: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 frontend/src/app/workspace/service/ai-assistant/ai-assistant.service.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 amber/src/main/scala/org/apache/texera/web/resource/UserConfigResource.scala: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 common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/model/VirtualDocument.scala: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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/hashJoin/HashJoinProbeOpExec.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/common/client/AmberClient.scala: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 amber/src/main/scala/org/apache/texera/web/service/ExecutionRuntimeService.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/promisehandlers/TakeGlobalCheckpointHandler.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/common/storage/SequentialRecordStorage.scala: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 REDACTED: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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/typecasting/TypeCastingUnit.java: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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/BufferedBlockReader.java: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 amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/promisehandlers/EmbeddedControlMessageHandler.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/architecture/worker/promisehandlers/PrepareCheckpointHandler.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/common/rpc/AsyncRPCServer.scala: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 amber/src/main/scala/org/apache/texera/amber/engine/common/statetransition/StateManager.scala: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 agent-service/src/server.ts:421— "Broadcast a server event to every client attached to the agent." repeats the code it sits on: 5 of its 6 words (broadcast, server, event, client, agent) are already in `function broadcastToAgentClients(agentId: string, event: WsServerEvent): void`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:104— "Selected computing unit type" repeats the code it sits on: 4 of its 4 words (selected, computing, unit, type) are already in `selectedComputingUnitType?: WorkflowComputingUnitType;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:108— "URI for local computing unit" repeats the code it sits on: 4 of its 4 words (uri, local, computing, unit) are already in `localComputingUnitUri: string = "";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/common/service/computing-unit/computing-unit-status/computing-unit-status.service.ts:233— "Observable for the currently selected computing unit" repeats the code it sits on: 4 of its 5 words (observable, selected, computing, unit) are already in `public getSelectedComputingUnit(): Observable<DashboardWorkflowComputingUnit | null>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/common/type/datasetVersionFileTree.ts:40— "Get the full path" repeats the code it sits on: 3 of its 3 words (get, full, path) are already in `const fullPath = getFullPathFromDatasetFileNode(node);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.ts:185— "Refresh the computing units list" repeats the code it sits on: 4 of its 4 words (refresh, computing, units, list) are already in `this.computingUnitStatusService.refreshComputingUnitList();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/dashboard/component/user/user-workflow/ngbd-modal-workflow-executions/workflow-execution-history.component.ts:144— "custom column width" repeats the code it sits on: 3 of its 3 words (custom, column, width) are already in `public customColumnWidth: Record<string, string> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts:172— "Subscribe to ReActSteps" repeats the code it sits on: 4 of its 4 words (subscribe, re, act, steps) are already in `this.agentService`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/agent/agent-panel/agent-chat/agent-chat.component.ts:291— "Stop workflow subscription" repeats the code it sits on: 3 of its 3 words (stop, workflow, subscription) are already in `this.stopWorkflowSubscription$.next();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/agent/agent-panel/agent-panel.component.ts:101— "Subscribe to agent changes" repeats the code it sits on: 3 of its 3 words (subscribe, agent, changes) are already in `this.agentService.agentChange$.pipe(untilDestroyed(this)).subscribe(() =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/code-editor-dialog/breakpoint-condition-input/breakpoint-condition-input.component.spec.ts:35— "Create a mock UdfDebugService" repeats the code it sits on: 4 of its 5 words (mock, udf, debug, service) are already in `mockUdfDebugService = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/hugging-face/hugging-face.component.spec.ts:763— 8 comments in this file only repeat the code they sit on (lines 763, 890, 969, 1023, 1052, 1292, 1323, 1440), for example "── Cached error states ──". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/menu/menu.component.ts:240— "Subscribe to computing unit" repeats the code it sits on: 3 of its 3 words (subscribe, computing, unit) are already in `this.subscribeToComputingUnitSelection();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/menu/menu.component.ts:287— "Subscribe to WorkflowResultExportService observable" repeats the code it sits on: 5 of its 6 words (subscribe, workflow, result, export, service) are already in `this.workflowResultExportService`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/menu/menu.component.ts:316— "Subscribe to get the computing unit status" repeats the code it sits on: 5 of its 5 words (subscribe, get, computing, unit, status) are already in `this.computingUnitStatusService`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:239— "Subscribe to the current selected unit from the status service" repeats the code it sits on: 5 of its 6 words (subscribe, selected, unit, status, service) are already in `this.computingUnitStatusService`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:803— "Refresh the computing units list" repeats the code it sits on: 4 of its 4 words (refresh, computing, units, list) are already in `this.computingUnitStatusService.refreshComputingUnitList();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:1037— "── Validator with formControl value ──" repeats the code it sits on: 4 of its 4 words (validator, form, control, value) are already in `it("requiredImageInput validator should pass when image task has formControl value", () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts:1117— "── formatTaskTitle via fallback preview ──" repeats the code it sits on: 4 of its 5 words (task, title, fallback, preview) are already in `it("should title-case multi-segment unknown task in fallback preview", () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:319— "Approximate height for search bar and margins" repeats the code it sits on: 4 of its 5 words (height, search, bar, margins) are already in `const SEARCH_BAR_HEIGHT_WITH_MARGIN = 77;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/workflow-editor/context-menu/context-menu/context-menu.component.spec.ts:99— "Mock return value" repeats the code it sits on: 3 of its 3 words (mock, return, value) are already in `workflowActionServiceSpy.getWorkflowMetadata.mockReturnValue({ name: "Test Workflow" });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/workflow-editor/context-menu/context-menu/context-menu.component.spec.ts:101— "Set up TexeraGraph spy return values" repeats the code it sits on: 5 of its 6 words (texera, graph, spy, return, values) are already in `texeraGraphSpy.hasLinkWithID.mockReturnValue(false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/workflow-editor/context-menu/context-menu/context-menu.component.ts:169— "Delete comment boxes" repeats the code it sits on: 3 of its 3 words (delete, comment, boxes) are already in `highlightedCommentBoxIDs.forEach(highlightedCommentBoxID =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.spec.ts:642— "add a link from scan to sentiment" repeats the code it sits on: 4 of its 4 words (add, link, scan, sentiment) are already in `workflowActionService.addLink(mockScanSentimentLink);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment frontend/src/app/workspace/component/workflow-editor/workflow-editor.component.spec.ts:675— "add a link from scan to view result" repeats the code it sits on: 4 of its 5 words (add, link, scan, result) are already in `workflowActionService.addLink(mockScanResultLink);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
+ 23 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×22
Console output used as the logging channel agent-service/src/server.ts:575— `agent-service/src/server.ts` reports through `console.*` at line 575 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:576— `agent-service/src/server.ts` reports through `console.*` at line 576 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:577— `agent-service/src/server.ts` reports through `console.*` at line 577 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:578— `agent-service/src/server.ts` reports through `console.*` at line 578 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:579— `agent-service/src/server.ts` reports through `console.*` at line 579 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:581— `agent-service/src/server.ts` reports through `console.*` at line 581 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:589— `agent-service/src/server.ts` reports through `console.*` at line 589 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:593— `agent-service/src/server.ts` reports through `console.*` at line 593 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:594— `agent-service/src/server.ts` reports through `console.*` at line 594 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:596— `agent-service/src/server.ts` reports through `console.*` at line 596 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:598— `agent-service/src/server.ts` reports through `console.*` at line 598 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:599— `agent-service/src/server.ts` reports through `console.*` at line 599 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:600— `agent-service/src/server.ts` reports through `console.*` at line 600 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:605— `agent-service/src/server.ts` reports through `console.*` at line 605 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:606— `agent-service/src/server.ts` reports through `console.*` at line 606 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:607— `agent-service/src/server.ts` reports through `console.*` at line 607 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:608— `agent-service/src/server.ts` reports through `console.*` at line 608 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:609— `agent-service/src/server.ts` reports through `console.*` at line 609 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:610— `agent-service/src/server.ts` reports through `console.*` at line 610 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:611— `agent-service/src/server.ts` reports through `console.*` at line 611 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:612— `agent-service/src/server.ts` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel agent-service/src/server.ts:613— `agent-service/src/server.ts` reports through `console.*` at line 613 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Interpolated log message defeats structured logging file-service/src/main/scala/org/apache/texera/service/util/LakeFSExceptionHandler.scala:80— `warn` at line 80 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:310— `warn` at line 310 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/ComputingUnitManagingResource.scala:992— `warn` at line 992 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:778— `warn` at line 778 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1198— `warn` at line 1198 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging common/workflow-operator/src/main/scala/com/kjetland/jackson/jsonSchema/JsonSchemaGenerator.scala:1572— `warn` at line 1572 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging common/auth/src/main/scala/org/apache/texera/auth/RequestLoggingFilter.scala:44— `info` at line 44 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/ComputingUnitMaster.scala:223— `info` at line 223 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/TexeraWebApplication.scala:190— `info` at line 190 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:119— `warn` at line 119 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:209— `warn` at line 209 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/GmailResource.scala:227— `warn` at line 227 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:92— `error` at line 92 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:155— `warn` at line 155 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:162— `warn` at line 162 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:219— `warn` at line 219 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:261— `warn` at line 261 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:362— `warn` at line 362 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:377— `warn` at line 377 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:429— `warn` at line 429 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:434— `debug` at line 434 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:439— `debug` at line 439 is handed an interpolated string as its message through SLF4J, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Duplicated predicate frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts:157— `!forced && sameList && this.sortMethod === this.lastSortMethod` appears character-identically in 4 files — frontend/src/app/dashboard/component/user/user-dataset/user-dataset.component.ts, frontend/src/app/dashboard/component/user/user-model/user-model.component.ts, frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.ts, frontend/src/app/hub/component/hub-search-result/hub-search-result.component.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 frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:448— `!isDefined(userId) || !isDefined(this.entry.id)` appears character-identically in 2 files — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts, frontend/src/app/dashboard/component/user/list-item/list-item.component.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 agent-service/src/agent/tools/result-formatting.ts:67— `!opInfo.result || !Array.isArray(opInfo.result)` appears character-identically in 2 files — agent-service/src/agent/tools/result-formatting.ts, agent-service/src/agent/tools/workflow-execution-tools.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 frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts:417— `currentNode && currentNode.type === "directory" && currentNode.children` appears character-identically in 2 files — frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/dataset-detail.component.ts, frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.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 agent-service/src/agent/workflow-state.ts:214— `currentOperator && !currentOperator.isDisabled` appears character-identically in 2 files — agent-service/src/agent/workflow-state.ts, frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.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 frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts:246— `descriptor.hasSize && typeof this.entry.id === "number"` appears character-identically in 2 files — frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts, frontend/src/app/dashboard/component/user/list-item/list-item.component.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 frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:208— `err instanceof HttpErrorResponse && err.status === 503` appears character-identically in 2 files — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts, frontend/src/app/dashboard/component/admin/cu-image/admin-cu-image.component.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 frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:256— `this.gpuOptions.length > 1 || (this.gpuOptions.length === 1 && this.gpuOptions[0] !== "0")` appears character-identically in 3 files — frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts, frontend/src/app/dashboard/component/user/user-computing-unit/user-computing-unit-list-item/user-computing-unit-list-item.component.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 frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts:540— `typeof fromModel === "string" && fromModel.trim().length > 0` appears character-identically in 2 files — frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts, frontend/src/app/workspace/util/hugging-face-field-bindings.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 frontend/src/app/common/formly/delimiter/delimiter.type.ts:78— `v === undefined || v === null || v === ""` appears character-identically in 2 files — frontend/src/app/common/formly/delimiter/delimiter.type.ts, frontend/src/app/workspace/component/workflow-form/workflow-form.component.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 common/workflow-core/src/main/scala/org/apache/texera/amber/util/IcebergUtil.scala:77— `Shell.WINDOWS && !Shell.hasWinutilsPath()` appears character-identically in 2 files — common/workflow-core/src/main/scala/org/apache/texera/amber/util/IcebergUtil.scala, common/workflow-core/src/main/scala/org/apache/texera/amber/util/WinutilsFreeLocalFileSystem.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala:93— `agg.aggFunction == AggregationFunction.COUNT && (agg.attribute == null || agg.attribute.trim.isEmpty)` appears character-identically in 2 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/aggregate/AggregateOpExec.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:103— `attributeType == FileAttributeType.BINARY || attributeType == FileAttributeType.LARGE_BINARY` appears character-identically in 3 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/text/TextInputSourceOpDesc.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpDesc.scala:150— `database != null && database.trim.nonEmpty` appears character-identically in 2 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/SQLSourceOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/asterixdb/AsterixDBSourceOpDesc.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLSourceOpExec.scala:47— `desc.keywordSearch.getOrElse(false) && keywordSearchByColumn != null && desc.keywords != null` appears character-identically in 2 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/mysql/MySQLSourceOpExec.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/sql/postgresql/PostgreSQLSourceOpExec.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala:168— `fileScanOffset.isEmpty && fileScanLimit.isEmpty` appears character-identically in 2 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/source/scan/file/FileScanSourceOpDesc.scala. 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 amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala:548— `lower == suffix || lower.endsWith("." + suffix)` appears character-identically in 2 files — amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala, common/util/src/main/scala/org/apache/texera/common/util/AvatarUtil.scala. 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 common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dictionary/DictionaryMatcherOpDesc.scala:86— `resultAttribute == null || resultAttribute.trim.isEmpty` appears character-identically in 3 files — common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/dictionary/DictionaryMatcherOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/HuggingFaceTextSummarizationOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/unneststring/UnnestStringOpDesc.scala. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: REDACTED, frontend/src/app/common/service/user/config/user-config.service.ts, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/loop/LoopOpDesc.scala, frontend/src/app/workspace/service/operator-metadata/operator-metadata.service.ts, common/workflow-core/src/main/scala/org/apache/texera/amber/core/state/StateReferencing.scala, amber/src/main/python/core/storage/iceberg/iceberg_table_writer.py, frontend/src/app/workspace/service/ai-analyst/ai-analyst.service.ts, common/workflow-core/src/main/scala/org/apache/texera/amber/core/state/State.scala (+8 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 16 significant file(s) lose their only recent owner: file-service/src/main/scala/org/apache/texera/service/resource/ResourceUploadService.scala, computing-unit-managing-service/src/main/scala/org/apache/texera/service/resource/CuratedImageResource.scala, frontend/src/app/dashboard/component/user/user-model/user-model-explorer/model-detail.component.ts, computing-unit-managing-service/src/main/scala/org/apache/texera/service/util/ImageValidationClient.scala, common/resource/src/main/scala/org/apache/texera/service/resource/ResourceAccess.scala, computing-unit-managing-service/src/main/scala/org/apache/texera/service/util/ImagePrepullClient.scala, amber/src/main/scala/org/apache/texera/web/resource/dashboard/VersionedResourceTables.scala, common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/model/LakeFSFileDocument.scala (+8 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 10 significant file(s) lose their only recent owner: workflow-compiling-service/src/main/scala/org/apache/texera/amber/translator/WorkflowToPythonTranslator.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/machineLearning/sklearnAdvanced/base/SklearnAdvancedBaseDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/StandaloneHelpers.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/StandaloneCodeGenerator.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/SpecializedFilterOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/regex/RegexOpDesc.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/HuggingFaceSentimentAnalysisOpDesc.scala, frontend/src/app/workspace/component/constrained-value/constrained-value.component.ts (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 7 significant file(s) lose their only recent owner: frontend/src/app/workspace/service/notebook-migration/migration-llm.ts, frontend/src/app/workspace/service/notebook-migration/notebook-migration.service.ts, frontend/src/app/workspace/service/jupyter-panel/jupyter-panel.service.ts, frontend/src/app/workspace/component/notebook-import-modal/notebook-import-modal.component.ts, frontend/src/app/workspace/service/notebook-migration/script-segmentation.ts, notebook-migration-service/src/main/scala/org/apache/texera/service/util/JupyterKubernetesClient.scala, frontend/src/app/workspace/component/jupyter-notebook-panel/jupyter-notebook-panel.component.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 6 significant file(s) lose their only recent owner: common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/HuggingFaceCodegenBase.scala, amber/src/main/scala/org/apache/texera/web/resource/HuggingFaceModelResource.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/ImageTaskCodegen.scala, frontend/src/app/workspace/component/hugging-face-image-upload/hugging-face-image-upload.component.ts, frontend/src/app/workspace/service/workflow-status/performance-metrics.ts, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/huggingFace/codegen/TextGenCodegen.scala. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 6 significant file(s) lose their only recent owner: amber/src/main/python/core/storage/iceberg/iceberg_document.py, amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/warehouse/WarehouseResource.scala, frontend/src/app/common/service/warehouse/warehouse-actions.service.ts, amber/src/main/python/core/storage/iceberg/iceberg_catalog_instance.py, common/workflow-core/src/main/scala/org/apache/texera/amber/core/storage/WarehouseReadGuard.scala, frontend/src/app/common/service/warehouse/warehouse.service.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 3 significant file(s) lose their only recent owner: frontend/src/app/workspace/service/form-binding/form-binding.service.ts, frontend/src/app/workspace/service/workflow-graph/model/shared-model.ts, frontend/src/app/workspace/util/custom-formly-type.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #8 — If anonymized user #8 becomes unavailable, 3 significant file(s) lose their only recent owner: common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/sort/StableMergeSortOpExec.scala, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/udf/python/PythonUdfUiParameterInjector.scala, common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonLexerUtils.scala. Pair on, review, or document these before any departure.
Silent fallback default in catch amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:173— `getNonDownloadableOperatorMap` swallows every exception into `Map.empty` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch case or in the Scaladoc, and the row stops firing.
Silent fallback default in catch bin/local-dev/tui.py:741— `subprocess_run` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch frontend/src/app/workspace/service/form-binding/form-binding.service.ts:295— `operatorSchemaProperties` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure bin/local-dev/tui.py:445— `_parse_etime` returns `-1` when `ValueError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure bin/local-dev/tui.py:542— `container_uptime` returns `'—'` when `ValueError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung REDACTED:95— An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 122 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 10 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (83 single-owned of 758 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 758 of the 1256 production source files in this repository met that bar). They are anonymized user #9 (3 file(s)), anonymized user #10 (3 file(s)), anonymized user #11 (2 file(s)), anonymized user #12 (2 file(s)), anonymized user #13 (1 file(s)), anonymized user #14 (1 file(s)) (+4 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: frontend/src/app/hub/component/login/texera-login.component.ts, amber/src/main/scala/org/apache/texera/web/resource/auth/ExternalAuthProvisioner.scala, frontend/src/app/common/service/user/email-request-modal/email-request-modal.component.ts, frontend/src/app/workspace/service/preset/preset.service.ts, common/workflow-core/src/main/scala/org/apache/texera/amber/core/workflow/PartitionInfo.scala, amber/src/main/scala/org/apache/texera/web/StaticAssetCacheFilter.scala, frontend/src/app/dashboard/service/user/workflow-version/workflow-version.service.ts, common/workflow-core/src/main/scala/org/apache/texera/amber/core/tuple/AttributeType.java (+8 more).
Documentation: no build, run or usage example pyright-language-service/README.md:1— `pyright-language-service` is runnable (a `start` script in `REDACTED`) and neither `pyright-language-service/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
No ADRs found — 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 22 project(s) overshoot their size bounds, lowering Project Cohesion to 6.6/10. The most over is `frontend` (63091 LoC, 510 module-visible types across 187 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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 54 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.ts, agent-service/src/agent/prompts.ts, frontend/src/app/workspace/component/agent/agent-interaction/agent-interaction.component.ts, agent-service/src/agent/util/context-utils.ts, frontend/src/app/workspace/component/agent/agent-panel/react-step-detail-modal/react-step-detail-modal.component.ts, agent-service/src/agent/util/workflow-utils.ts, common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/filter/FilterPredicate.java, frontend/src/app/workspace/component/left-panel/time-travel/time-travel.component.ts (and 46 more) (56 orphaned of 758 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 758 of the 1256 production source files in this repository met that bar). 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 15/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `pyright-language-service`.
No dependency-update automation REDACTED:17— `REDACTED` 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`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Unused export 'USER_DATASET_CREATE' · ×1
Unused export 'USER_DATASET_CREATE' frontend/src/app/app-routing.constant.ts:80— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'WORKFLOW_USER_ACCESS' · ×1
Unused export 'WORKFLOW_USER_ACCESS' frontend/src/app/common/service/workflow-persist/workflow-persist.service.ts:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DATASET_SEARCH_URL' · ×1
Unused export 'DATASET_SEARCH_URL' frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:42— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DATASET_DELETE_URL' · ×1
Unused export 'DATASET_DELETE_URL' frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:43— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DATASET_NAME_MAX_LENGTH' · ×1
Unused export 'DATASET_NAME_MAX_LENGTH' frontend/src/app/dashboard/service/user/dataset/dataset.service.ts:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'VIEW_RESULT_OP_NAME' · ×1
Unused export 'VIEW_RESULT_OP_NAME' frontend/src/app/workspace/service/workflow-graph/model/workflow-graph.ts:77— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'ApiMessageResponse' · ×1
Unused module-local declaration 'ApiMessageResponse' frontend/src/app/workspace/service/agent/agent.service.ts:141— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused private field 'DICT_PREFIX' · ×1
Unused private field 'DICT_PREFIX' frontend/src/app/workspace/service/preset/preset.service.ts:72— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Unused private field 'productionSharedEditingServer' · ×1
Unused private field 'productionSharedEditingServer' frontend/src/app/workspace/service/workflow-graph/model/shared-model.ts:82— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Write-only private field 'syncTexeraModel' · ×1
Write-only private field 'syncTexeraModel' frontend/src/app/workspace/service/workflow-graph/model/workflow-action.service.ts:100— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
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 3/7 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· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — No build over this repository's 703 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
doc comments repeat the names frontend/src/app/common/component/computing-unit-create-modal/computing-unit-create-modal.component.ts:278— 18 of 383 documented parameters and 24 of 1700 summaries in `gui` only repeat the member or parameter name (e.g. "Start a new computing unit." for `startComputingUnit`). 151 documentation tag(s) are empty. 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 2 file(s) — `amber/src/main/scala/org/apache/texera/web/service/ResultExportService.scala`, `frontend/src/app/workspace/component/hugging-face/hugging-face.component.ts` — so the PII/GDPR sweep did not cover them at all.
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 01a1b3cd-cb09-769f-88a9-e3b743d7742f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 318 · Warnings: 753 · Recommendations: 359 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 07-11-2026 @ 02:19 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.