Public report of Embucket/embucket-labs, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 21:10 UTC · Survey ID cd_2b0c64ab632a40739b8104a713cf090f
Embucket/embucket-labs
Measured 17 November 2026, 21:10 UTC, at code version 08dd93f
Bus factor is not measured: No living knowledge left to concentrate.
CAI scoreAt risk
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 medium codebase: 82,839 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Code Health, 44.0
Findings by how serious they are
151 critical752 serious433 minor
10 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
17 November 2026, 21:10 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 ▸
75of 75 dimensions measured by tools.
1279of 1336 findings point to an exact file and line, so you can open each one in the code. The other 57 concern the repository as a whole, such as missing documentation.
75dimensions across 9 lenses, read from 82,839 lines of product code in 18 projects.
Embucket/embucket-labs is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 54.5 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Code Health, at 44.0, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the security flaws the scanner found, worth about 1.5 points. Removing the unused code would lift Code Health itself, worth about 5.5 points. Raising Code Health to 67 would lift the score to about 61.8.
Seventy-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Forty known security holes in the packages the code depends on can be used by attackers, and seven weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Limiting each secret to its own step would fix the five secrets exposed to more of the pipeline than needed, and the five unsafe settings in infrastructure or container files need changing to safe values. Saving the change and the message together would take care of the place where data is saved and a message sent separately.
The product code is 82,839 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 44.0 to 67, the lowest score rated Strong, the score would rise from 54.5 to about 61.8.
Code composition: what the lines of code are
Product code 76%Tests 24%
Rebuild cost: about €110,000 · Estimate
Cost to rebuild
€36,000 to €180,000, for 601 to 1,906 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 82,839 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 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED.
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 5.5 points · Medium effort · Dead Code
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 1.5 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Code Health, at 44.0 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST). Of all the actions in this report, it raises the score most for the work it takes: about 1.5 points for low effort, because it clears the 7 Static Analysis (SAST) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 91,469 lines over the last 90 days, which is about 370,958 lines a year. At that pace, the extra work comes to an estimated 18.5 to 123.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
580 modules, with 345 dependencies between them. 9 loops run through 27 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 540 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.
api_ui.error uses core_history.entities.query_id, so a change to core_history.entities.query_id can break api_ui.error, while a change to api_ui.error can't break core_history.entities.query_id.
Position
Below the diagonal: api_ui.error uses a module listed above it, which is the healthy direction.
core_history.entities.result_set uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_history.entities.result_set, while a change to core_history.entities.result_set can't break core_history.entities.query_id.
Position
Below the diagonal: core_history.entities.result_set uses a module listed above it, which is the healthy direction.
core_metastore.metastore uses core_metastore.models.schema, so a change to core_metastore.models.schema can break core_metastore.metastore, while a change to core_metastore.metastore can't break core_metastore.models.schema.
Position
Below the diagonal: core_metastore.metastore uses a module listed above it, which is the healthy direction.
core_metastore.metastore uses core_utils, so a change to core_utils can break core_metastore.metastore, while a change to core_metastore.metastore can't break core_utils.
Position
Below the diagonal: core_metastore.metastore uses a module listed above it, which is the healthy direction.
df_catalog.catalog_list uses core_metastore.models, so a change to core_metastore.models can break df_catalog.catalog_list, while a change to df_catalog.catalog_list can't break core_metastore.models.
Position
Below the diagonal: df_catalog.catalog_list uses a module listed above it, which is the healthy direction.
embucket_seed.seed_models.volume uses embucket_seed.seed_generator.generator, so a change to embucket_seed.seed_generator.generator can break embucket_seed.seed_models.volume, while a change to embucket_seed.seed_models.volume can't break embucket_seed.seed_generator.generator.
Position
Below the diagonal: embucket_seed.seed_models.volume uses a module listed above it, which is the healthy direction.
sqlite_plugin.vfs uses sqlite_plugin.flags, so a change to sqlite_plugin.flags can break sqlite_plugin.vfs, while a change to sqlite_plugin.vfs can't break sqlite_plugin.flags.
Position
Below the diagonal: sqlite_plugin.vfs uses a module listed above it, which is the healthy direction.
core_history.interface uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_history.interface, while a change to core_history.interface can't break core_history.entities.query_id.
Position
Below the diagonal: core_history.interface uses a module listed above it, which is the healthy direction.
core_history.interface uses core_history.entities.worksheet, so a change to core_history.entities.worksheet can break core_history.interface, while a change to core_history.interface can't break core_history.entities.worksheet.
Position
Below the diagonal: core_history.interface uses a module listed above it, which is the healthy direction.
core_history.interface uses core_history.entities.result_set, so a change to core_history.entities.result_set can break core_history.interface, while a change to core_history.interface can't break core_history.entities.result_set.
Position
Below the diagonal: core_history.interface uses a module listed above it, which is the healthy direction.
27→29 core_history.interface uses core_history.entities.querypart of a loop✕
Connections
2 pairs of types, where a type in core_history.interface uses a type in core_history.entities.query.
core_history.interface uses core_history.entities.query, so a change to core_history.entities.query can break core_history.interface, while a change to core_history.interface can't break core_history.entities.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sqlite_plugin.mock uses sqlite_plugin.flags, so a change to sqlite_plugin.flags can break sqlite_plugin.mock, while a change to sqlite_plugin.mock can't break sqlite_plugin.flags.
Position
Below the diagonal: sqlite_plugin.mock uses a module listed above it, which is the healthy direction.
sqlite_plugin.mock uses sqlite_plugin.vfs, so a change to sqlite_plugin.vfs can break sqlite_plugin.mock, while a change to sqlite_plugin.mock can't break sqlite_plugin.vfs.
Position
Below the diagonal: sqlite_plugin.mock uses a module listed above it, which is the healthy direction.
core_history.entities.query uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_history.entities.query, while a change to core_history.entities.query can't break core_history.entities.query_id.
Position
Below the diagonal: core_history.entities.query uses a module listed above it, which is the healthy direction.
core_history.entities.query uses core_history.interface, so a change to core_history.interface can break core_history.entities.query, while a change to core_history.entities.query can't break core_history.interface.
Position
Below the diagonal: core_history.entities.query uses a module listed above it, which is the healthy direction.
core_sqlite.vfs uses sqlite_plugin.flags, so a change to sqlite_plugin.flags can break core_sqlite.vfs, while a change to core_sqlite.vfs can't break sqlite_plugin.flags.
Position
Below the diagonal: core_sqlite.vfs uses a module listed above it, which is the healthy direction.
core_sqlite.vfs uses sqlite_plugin.vfs, so a change to sqlite_plugin.vfs can break core_sqlite.vfs, while a change to core_sqlite.vfs can't break sqlite_plugin.vfs.
Position
Below the diagonal: core_sqlite.vfs uses a module listed above it, which is the healthy direction.
core_sqlite.vfs uses sqlite_plugin.mock, so a change to sqlite_plugin.mock can break core_sqlite.vfs, while a change to core_sqlite.vfs can't break sqlite_plugin.mock.
Position
Below the diagonal: core_sqlite.vfs uses a module listed above it, which is the healthy direction.
core_executor.error uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_executor.error, while a change to core_executor.error can't break core_history.entities.query_id.
Position
Below the diagonal: core_executor.error uses a module listed above it, which is the healthy direction.
core_executor.error uses core_history.entities.query, so a change to core_history.entities.query can break core_executor.error, while a change to core_executor.error can't break core_history.entities.query.
Position
Below the diagonal: core_executor.error uses a module listed above it, which is the healthy direction.
core_executor.models uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_executor.models, while a change to core_executor.models can't break core_history.entities.query_id.
Position
Below the diagonal: core_executor.models uses a module listed above it, which is the healthy direction.
core_executor.models uses core_metastore.models.schema, so a change to core_metastore.models.schema can break core_executor.models, while a change to core_executor.models can't break core_metastore.models.schema.
Position
Below the diagonal: core_executor.models uses a module listed above it, which is the healthy direction.
core_executor.models uses core_history.entities.result_set, so a change to core_history.entities.result_set can break core_executor.models, while a change to core_executor.models can't break core_history.entities.result_set.
Position
Below the diagonal: core_executor.models uses a module listed above it, which is the healthy direction.
core_executor.models uses core_history.entities.query, so a change to core_history.entities.query can break core_executor.models, while a change to core_executor.models can't break core_history.entities.query.
Position
Below the diagonal: core_executor.models uses a module listed above it, which is the healthy direction.
32→36 core_executor.models uses core_executor.utilspart of a loop✕
Connections
1 pair of types, where a type in core_executor.models uses a type in core_executor.utils.
core_executor.models uses core_executor.utils, so a change to core_executor.utils can break core_executor.models, while a change to core_executor.models can't break core_executor.utils.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core_history.slatedb_history_store uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_history.slatedb_history_store, while a change to core_history.slatedb_history_store can't break core_history.entities.query_id.
Position
Below the diagonal: core_history.slatedb_history_store uses a module listed above it, which is the healthy direction.
core_history.slatedb_history_store uses core_history.entities.worksheet, so a change to core_history.entities.worksheet can break core_history.slatedb_history_store, while a change to core_history.slatedb_history_store can't break core_history.entities.worksheet.
Position
Below the diagonal: core_history.slatedb_history_store uses a module listed above it, which is the healthy direction.
core_history.slatedb_history_store uses core_utils, so a change to core_utils can break core_history.slatedb_history_store, while a change to core_history.slatedb_history_store can't break core_utils.
Position
Below the diagonal: core_history.slatedb_history_store uses a module listed above it, which is the healthy direction.
core_history.slatedb_history_store uses core_history.interface, so a change to core_history.interface can break core_history.slatedb_history_store, while a change to core_history.slatedb_history_store can't break core_history.interface.
Position
Below the diagonal: core_history.slatedb_history_store uses a module listed above it, which is the healthy direction.
core_history.slatedb_history_store uses core_history.entities.query, so a change to core_history.entities.query can break core_history.slatedb_history_store, while a change to core_history.slatedb_history_store can't break core_history.entities.query.
Position
Below the diagonal: core_history.slatedb_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_history.entities.query_id.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_history.entities.worksheet, so a change to core_history.entities.worksheet can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_history.entities.worksheet.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_utils, so a change to core_utils can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_utils.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_history.entities.result_set, so a change to core_history.entities.result_set can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_history.entities.result_set.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_history.interface, so a change to core_history.interface can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_history.interface.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_history.sqlite_history_store uses core_history.entities.query, so a change to core_history.entities.query can break core_history.sqlite_history_store, while a change to core_history.sqlite_history_store can't break core_history.entities.query.
Position
Below the diagonal: core_history.sqlite_history_store uses a module listed above it, which is the healthy direction.
core_executor.dedicated_executor uses sqlite_plugin.mock, so a change to sqlite_plugin.mock can break core_executor.dedicated_executor, while a change to core_executor.dedicated_executor can't break sqlite_plugin.mock.
Position
Below the diagonal: core_executor.dedicated_executor uses a module listed above it, which is the healthy direction.
core_executor.dedicated_executor uses core_executor.error, so a change to core_executor.error can break core_executor.dedicated_executor, while a change to core_executor.dedicated_executor can't break core_executor.error.
Position
Below the diagonal: core_executor.dedicated_executor uses a module listed above it, which is the healthy direction.
core_executor.utils uses core_executor.models, so a change to core_executor.models can break core_executor.utils, while a change to core_executor.utils can't break core_executor.models.
Position
Below the diagonal: core_executor.utils uses a module listed above it, which is the healthy direction.
api_snowflake_rest.server.server_models uses core_executor.utils, so a change to core_executor.utils can break api_snowflake_rest.server.server_models, while a change to api_snowflake_rest.server.server_models can't break core_executor.utils.
Position
Below the diagonal: api_snowflake_rest.server.server_models uses a module listed above it, which is the healthy direction.
core_executor.service uses core_history.entities.query_id, so a change to core_history.entities.query_id can break core_executor.service, while a change to core_executor.service can't break core_history.entities.query_id.
Position
Below the diagonal: core_executor.service uses a module listed above it, which is the healthy direction.
core_executor.service uses df_catalog.catalog_list, so a change to df_catalog.catalog_list can break core_executor.service, while a change to core_executor.service can't break df_catalog.catalog_list.
Position
Below the diagonal: core_executor.service uses a module listed above it, which is the healthy direction.
core_executor.service uses core_executor.models, so a change to core_executor.models can break core_executor.service, while a change to core_executor.service can't break core_executor.models.
Position
Below the diagonal: core_executor.service uses a module listed above it, which is the healthy direction.
core_executor.service uses core_executor.utils, so a change to core_executor.utils can break core_executor.service, while a change to core_executor.service can't break core_executor.utils.
Position
Below the diagonal: core_executor.service uses a module listed above it, which is the healthy direction.
core_executor.session uses embucket_functions.session_params, so a change to embucket_functions.session_params can break core_executor.session, while a change to core_executor.session can't break embucket_functions.session_params.
Position
Below the diagonal: core_executor.session uses a module listed above it, which is the healthy direction.
core_executor.session uses df_catalog.catalog_list, so a change to df_catalog.catalog_list can break core_executor.session, while a change to core_executor.session can't break df_catalog.catalog_list.
Position
Below the diagonal: core_executor.session uses a module listed above it, which is the healthy direction.
core_executor.session uses core_executor.models, so a change to core_executor.models can break core_executor.session, while a change to core_executor.session can't break core_executor.models.
Position
Below the diagonal: core_executor.session uses a module listed above it, which is the healthy direction.
core_executor.session uses core_executor.dedicated_executor, so a change to core_executor.dedicated_executor can break core_executor.session, while a change to core_executor.session can't break core_executor.dedicated_executor.
Position
Below the diagonal: core_executor.session uses a module listed above it, which is the healthy direction.
core_executor.session uses core_executor.utils, so a change to core_executor.utils can break core_executor.session, while a change to core_executor.session can't break core_executor.utils.
Position
Below the diagonal: core_executor.session uses a module listed above it, which is the healthy direction.
39→40 core_executor.session uses core_executor.querypart of a loop✕
Connections
1 pair of types, where a type in core_executor.session uses a type in core_executor.query.
core_executor.session uses core_executor.query, so a change to core_executor.query can break core_executor.session, while a change to core_executor.session can't break core_executor.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core_executor.query uses df_catalog.catalog_list, so a change to df_catalog.catalog_list can break core_executor.query, while a change to core_executor.query can't break df_catalog.catalog_list.
Position
Below the diagonal: core_executor.query uses a module listed above it, which is the healthy direction.
core_executor.query uses core_executor.models, so a change to core_executor.models can break core_executor.query, while a change to core_executor.query can't break core_executor.models.
Position
Below the diagonal: core_executor.query uses a module listed above it, which is the healthy direction.
core_executor.query uses core_executor.utils, so a change to core_executor.utils can break core_executor.query, while a change to core_executor.query can't break core_executor.utils.
Position
Below the diagonal: core_executor.query uses a module listed above it, which is the healthy direction.
core_executor.query uses core_executor.session, so a change to core_executor.session can break core_executor.query, while a change to core_executor.query can't break core_executor.session.
Position
Below the diagonal: core_executor.query uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 44.0 · Weak · gated by R7 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
123
High / Critical
A05:2025 — Injection
93
High / Critical
A02:2025 — Security Misconfiguration
8
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Top priorities: Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only; Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED.
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
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.
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 — 151
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 — 752
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 — 433
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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 75 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
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 — 75 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, 1279 of 1336 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: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .rs) and this repository declares a Cargo test suite (repository root, 143 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 325 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 325 of the 598 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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.
D28 Secrets (history) — 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 newest 200 of 1138 commits were scanned for secrets, back to commit f337a08f341f; older commits were not. `gitleaks` TIMED OUT after 168.5s against a 168.5s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
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. `ui/orval.config.ts`, `ui/src/app/types/vite-env.d.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.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — embucket Error context canceled spark-iceberg Warning context canceled mc Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: spark-iceberg Warning context canceled minio Error context canceled embucket Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build spark-iceberg Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
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.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 83 further occurrence(s) are not listed individually; the score already reflects all 123.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X5 Nullable reference types — 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. 91 further occurrence(s) are not listed individually; the score already reflects all 131.
Repo exclusion declarations: 12 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was core_executor::snowflake_error::datafusion_error at 43. A further 8 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 auto-completion.customAutoCompletion at 47 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts (auto-completion.customAutoCompletion at 47), crates/embucket-functions/src/json.rs (embucket_functions::json::encode_array at 46), crates/embucket-functions/src/datetime/date_add.rs (DateAddFunc::invoke_with_args at 18), crates/api-ui/src/auth/error.rs (TokenErrorKind::from at 16), crates/embucket-functions/src/datetime/date_diff.rs (DateDiffFunc::invoke_with_args at 16). 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.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with core_executor::snowflake_error::datafusion_error (cyclomatic 43), ToTimestampFunc::invoke_with_args (cyclomatic 33), UserQuery::execute (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 3 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.
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.
+ 53 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with ToTimeFunc::invoke_with_args (cognitive 87). — Refactoring it lifts Cognitive Complexity from 5.7 to about 6.2/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 FileTooLong finding(s) in God Classes — start with REDACTED, metastore.rs, json.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 MethodTooLong finding(s) in God Classes — start with REDACTED (4), merge.rs, div0.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 ClassTooLong finding(s) in God Classes — start with REDACTED, sqlite_history_store.rs, metastore.rs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
149 duplicated block group(s) detected. 7.8 % of the production lines (6,429 of 82,839) are in a reported copy. A further 92 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 114 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with layer.rs, REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with sqlite_history_store.rs, metastore.rs, to_boolean.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with json.rs (2), columns.rs, parameters.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
18 production modules (Cargo+npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 16 of the 18 (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).
Unstable project df-catalog
Off the main sequence: sqlite-plugin
What to do
Resolve the 1 Unstable project df-catalog finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs, catalog.rs, layers.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
44 outdated, 0 yanked direct Cargo dependencies. 96 of 97 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: aes · ×44
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 793 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 47 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: REDACTED (20×31=620); crates/embucket-functions/src/conversion/to_timestamp.rs (8×33=264); crates/core-executor/src/snowflake_error.rs (5×43=215) Repeated repair below the complexity floor: crates/core-executor/src/datafusion/physical_plan/merge.rs (5 of 9 changes were fixes); REDACTED (3 of 4 changes were fixes); crates/embucket-functions/src/regexp/regexp_replace.rs (3 of 4 changes were fixes)
Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, to_timestamp.rs, snowflake_error.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with merge.rs, REDACTED, regexp_replace.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_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.
96 deducted task-comment markers across 82839 LoC (0.1/KLoC) → score 9.8. 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 92 TodoComment finding(s) in Explicit Debt — start with REDACTED (8), REDACTED (8), error.rs (6). — One of this dimension's main actionable groups (92 warning-level).
Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with result.py (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with options.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 47 document(s) read across 21 unit(s).
Documentation: no build, run or usage example · ×11crates/api-iceberg-rest/README.md:1
What to do
Resolve the 11 Documentation finding(s) in Documentation Quality — start with README.md (11). — One of this dimension's main actionable groups (11 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.
Resolve the 3 redundant comment finding(s) in Comment Value — start with sidebar.tsx, toggle.tsx, editor-theme.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
3 of 18 build units (Cargo, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3crates/embucket-functions/Cargo.toml:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (2), package.json. — One of this dimension's main actionable groups (3 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. History coverage: The newest 200 of 1138 commits were scanned for secrets, back to commit f337a08f341f; older commits were not. `gitleaks` TIMED OUT after 168.5s against a 168.5s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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).
93 finding(s): 0 critical, 93 high, 0 medium, 0 low. 72 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 3 file(s) — `crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs` (line 414), `ui/orval.config.ts` (line 27), `ui/src/app/types/vite-env.d.ts` (lines 4–6) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 72 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 (72 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 33 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27), REDACTED (6). — One of this dimension's main actionable groups (33 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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.
325 of 325 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 325 of the 598 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 322 Orphaned file finding(s) in Knowledge Freshness — start with error.rs (16), REDACTED (11), errors.rs (10). — One of this dimension's main actionable groups (322 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED, utils.rs, dedicated_executor.rs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with router.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels5.0 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. — ui/src/modules/shared/table-data-upload-dialog/table-data-upload-database-select.tsx:50
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.
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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Domain Modelling — Whether an aggregate references another aggregate by identity rather than embedding it by object reference.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Event-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`AllQueries.try_new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/benchmarks/src/clickbench/run.rs:67
`ConvertOpt.run` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/benchmarks/src/tpch/convert.rs:108
`tpch.get_query_sql` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/benchmarks/src/tpch/mod.rs:257
`SlateDBHistoryStore.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — crates/core-history/src/sqlite_history_store.rs:73, crates/core-history/src/sqlite_history_store.rs:76
`SlatedbVfs.delete` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/core-sqlite/src/vfs/mod.rs:210
`EmbucketIcebergCatalog.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:44, crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:51
`generate_implemented_functions.generate_implemented_functions_csv` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/embucket-functions/src/bin/generate_implemented_functions.rs:82
`generate_implemented_functions.generate_implemented_functions_csv` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/embucket-functions/src/bin/generate_implemented_functions.rs:86
`src.load_openapi_spec` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/embucketd/src/main.rs:525
What to do
Use the awaited twin of each blocking call, or move the work off the loop with `tokio::task::spawn_blocking` — a synchronous handler cannot simply `.await` in place.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`CoreExecutionService.submit_query` performs two independent DURABLE writes — a durable state write (`history_store.save_query_record`, :654) and a second independent durable store write — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — crates/core-executor/src/service.rs:616
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, 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.
`register_table` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:572
`invoke_with_args` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — crates/embucket-functions/src/scalar_template.rs:91
What to do
Finish or delete the functions that are still `todo!()`/`unimplemented!()` or panic "not implemented", and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls 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.
`merge_clause_projection` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — REDACTED:3015
`init` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/core-sqlite/src/vfs/init.rs:17
`register_table` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:572
`invoke_with_args` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — crates/embucket-functions/src/scalar_template.rs:91
`visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×16) — crates/embucket-functions/src/semi-structured/variant/visitors/array_agg.rs:60, crates/embucket-functions/src/semi-structured/variant/visitors/array_construct.rs:49, crates/embucket-functions/src/semi-structured/variant/visitors/array_construct_compact.rs:65, …
`substitute_aliases` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/embucket-functions/src/visitors/inline_aliases_in_query.rs:131
`inline_cte_refs_in_query` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/embucket-functions/src/visitors/table_functions_cte_relation.rs:132
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
test/README.md links to `test/README.md`, but `test/test/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — test/README.md:1
What to do
Reconcile the README with reality: test/README.md links to `test/README.md`, but `test/test/README.md` does not exist.
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/17 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/benchmarks`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
What to do
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.
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.
`reqwest::Client::new(` 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. — crates/embucket-seed/src/requests/service_client.rs:89
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
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.
Do you agree with this assessment?
R10 · Code Duplication4.5 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
19 duplicated blocks under ui/src/modules/ have copies in at least two of the sibling directories columns, data-preview, databases, home, queries, schemas (+3 more sibling(s) not listed) — 12 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 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. — ui/src/modules/databases/databases-page-table.tsx:13
8 duplicated blocks under ui/src/modules/shared/ have copies in at least two of the sibling directories create-database-dialog, create-schema-dialog, create-volume-dialog, table-data-upload-dialog — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28
ui/src/components/ui/dropdown-menu.tsx:6 · ui/src/components/ui/select.tsx:6 — the two spans are one implementation copied and then locally edited — 496 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. — ui/src/components/ui/dropdown-menu.tsx:6
ui/src/components/ui/alert-dialog.tsx:7 · ui/src/components/ui/dialog.tsx:10 — the two spans are one implementation copied and then locally edited — 379 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. — ui/src/components/ui/alert-dialog.tsx:7
ui/src/modules/databases/databases-page-table.tsx:13 · ui/src/modules/schemas/schemas-page-table.tsx:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ui/src/modules/databases/databases-page-table.tsx:13
ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28 · ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:26 — 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. — ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28
ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:64 · ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:95 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:64
ui/src/modules/columns/columns-page-toolbar.tsx:15 · ui/src/modules/data-preview/data-preview-page-toolbar.tsx:15 — 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. — ui/src/modules/columns/columns-page-toolbar.tsx:15
ui/src/modules/databases/databases-page-toolbar.tsx:15 · ui/src/modules/schemas/schemas-page-toolbar.tsx:15 · ui/src/modules/tables/tables-page-toolbar.tsx:15 · ui/src/modules/volumes/volumes-page-toolbar.tsx:15 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/modules/databases/databases-page-toolbar.tsx:15
ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:40 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:204 — 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. — ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:40
ui/src/modules/columns/columns-page.tsx:34 · ui/src/modules/data-preview/data-preview-page.tsx:52 — 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. — ui/src/modules/columns/columns-page.tsx:34
ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:49 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog.tsx:44 — 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. — ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:49
ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-databases.tsx:16 · ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-schemas.tsx:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-databases.tsx:16
ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx:17 · ui/src/modules/editor/editor-center-panel/editor-center-panel-header/editor-center-panel-header.tsx:14 — 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. — ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx:17
ui/src/modules/home/home-action-buttons.tsx:48 · ui/src/modules/tables/tables-page.tsx:56 — 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. — ui/src/modules/home/home-action-buttons.tsx:48
ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:38 · ui/src/modules/shared/create-schema-dialog/create-schema-dialog-form.tsx:27 — 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. — ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:38
ui/src/modules/columns/columns-page.tsx:99 · ui/src/modules/data-preview/data-preview-page.tsx:118 — 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. — ui/src/modules/columns/columns-page.tsx:99
ui/src/modules/databases/databases-page-table.tsx:15 · ui/src/modules/tables/tables-page-table.tsx:17 · ui/src/modules/volumes/volumes-page-table.tsx:13 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/modules/databases/databases-page-table.tsx:15
ui/src/components/ui/alert-dialog.tsx:60 · ui/src/components/ui/alert.tsx:30 · ui/src/components/ui/breadcrumb.tsx:17 · ui/src/components/ui/card.tsx:23 · +4 more site(s) not listed — the 8 copies are spread across 7 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. — ui/src/components/ui/alert-dialog.tsx:60
ui/src/components/ui/select.tsx:126 · ui/src/components/ui/select.tsx:141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — ui/src/components/ui/select.tsx:126
ui/src/modules/editor/editor-page.tsx:21 · ui/src/modules/editor/editor-page.tsx:43 — 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. — ui/src/modules/editor/editor-page.tsx:21
ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:26 · ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:49 — 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. — ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:26
ui/src/modules/columns/columns-page-table.tsx:6 · ui/src/modules/volumes/volumes-page-table.tsx:7 — 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. — ui/src/modules/columns/columns-page-table.tsx:6
ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets-skeleton.tsx:14 · ui/src/modules/editor/editor-right-panel/editor-right-panel-queries-skeleton.tsx:14 — 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. — ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets-skeleton.tsx:14
ui/src/modules/queries/queries-history-page-toolbar.tsx:22 · ui/src/modules/shared/trees/trees-toolbar.tsx:19 — 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. — ui/src/modules/queries/queries-history-page-toolbar.tsx:22
ui/src/modules/schemas/schemas-page.tsx:42 · ui/src/modules/volumes/volumes-page.tsx:37 — 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. — ui/src/modules/schemas/schemas-page.tsx:42
ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:260 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:276 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:289 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:302 — all 4 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:260
ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:279 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:292 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:305 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:279
ui/src/modules/home/home-dashboard-metrics.tsx:20 · ui/src/modules/home/home-dashboard-metrics.tsx:32 · ui/src/modules/home/home-dashboard-metrics.tsx:44 · ui/src/modules/home/home-dashboard-metrics.tsx:56 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — ui/src/modules/home/home-dashboard-metrics.tsx:20
ui/src/modules/databases/databases-page.tsx:30 · ui/src/modules/volumes/volumes-page.tsx:26 — 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. — ui/src/modules/databases/databases-page.tsx:30
ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:53 · ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:72 — 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. — ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:53
ui/src/modules/columns/columns-page-table.tsx:3 · ui/src/modules/queries/queries-history-table.tsx:8 · ui/src/modules/volumes/volumes-page-table.tsx:4 — the 3 copies are spread across 3 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. — ui/src/modules/columns/columns-page-table.tsx:3
ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-beautify-button.tsx:7 · ui/src/modules/editor/editor.tsx:29 — the two spans are one implementation copied and then locally edited — 69 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. — ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-beautify-button.tsx:7
ui/src/components/ui/alert-dialog.tsx:3 · ui/src/components/ui/dialog.tsx:2 · ui/src/components/ui/dropdown-menu.tsx:2 · ui/src/components/ui/hover-card.tsx:3 · +1 more site(s) not listed — the 5 copies are spread across 5 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. — ui/src/components/ui/alert-dialog.tsx:3
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.
EditorCenterBottomPanel has cyclomatic complexity 15 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. — ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx:23
TableDataUploadDialog has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:32
getDisplayValue has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx:7
EditorLeftBottomPanel has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx:12
Do you agree with this assessment?
R3 · Large Files9.8 / 10Exemplary✓ 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.
ui/src/components/ui/sidebar.tsx has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/components/ui/sidebar.tsx: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?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ 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 8 application, 9 tooling and 8 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx, ui/src/modules/editor/editor-left-panel/editor-left-panel.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx, ui/src/app/layout/sidebar/app-sidebar-org-menu.tsx, ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/components/ui/dropdown-menu.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (ui/src/app/routes/sql-editor/$worksheetId.index.tsx, ui/src/modules/editor/editor-center-panel/editor-center-panel-footer.tsx, ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-panels-state-provider.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx, ui/src/modules/editor/editor-right-panel/editor-right-panel-query/editor-right-panel-query.tsx, ui/src/modules/query/query-sql.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion-types.ts, ui/src/modules/editor/editor-extensions/editor-autocomplete/icons-svg.ts
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts, ui/src/modules/editor/editor.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-theme.ts
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx, ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/shared/delete-worksheet-alert-dialog/delete-worksheet-alert-dialog.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/components/ui/alert-dialog.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/__root.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/app/layout/sidebar/app-sidebar.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.$tableName.data-preview.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/data-preview/data-preview-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/tables/tables-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.$tableName.columns.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/columns/columns-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/modules/data-preview/data-preview-page.tsx, ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/data-preview/use-infinite-preview-data.ts
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/shared/data-page/data-page-layout.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/shared/data-page/data-page-trees.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (ui/src/modules/columns/columns-page.tsx, ui/src/modules/data-preview/data-preview-page.tsx, ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/components/ui/tabs.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/auth/sign-in-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — ui/src/modules/auth/sign-in-form.tsx, ui/src/components/ui/card.tsx
no import path from any entry point (8 application, 9 tooling, 8 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 — ui/src/components/ui/breadcrumb.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx, ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/shared/delete-worksheet-alert-dialog/delete-worksheet-alert-dialog.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/queries/queries-history-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/queries/queries-history-table.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/query/query-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/query/query-details.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/databases/databases-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheet.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/schemas/schemas-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/queries/$queryId.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/query/query-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/schemas/schemas-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-right-panel/editor-right-panel-queries.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-right-panel/editor-right-panel-query/editor-right-panel-query.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/volumes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/volumes/volumes-page.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx, ui/src/app/layout/sidebar/app-sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/app/layout/sidebar/app-sidebar-group.tsx
no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-panel-table-columns-toolbar.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — ui/package.json:55, ui/package.json:100
Every import is type-only — move it to devDependencies. — ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-run-sql-button.tsx:3
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 — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`axum::serve(` (crates/embucketd/src/main.rs:331)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
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.
This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `axum::serve(` (crates/embucketd/src/main.rs:331).
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (crates/embucketd/src/main.rs:331).
What to do
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
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.
`sqlite_plugin::vars::SQLITE_OK_LOAD_PERMANENTLY` follows `{ return err; }` (line 792) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/core-sqlite/src/vfs/mod.rs:796
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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.
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 document1.4 / 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.
`flatten` is public and takes `value: &Value` from its caller, and it calls itself at line 127 with a piece of the document (and at line 151) — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `flatten` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:127
`is_query_cancelled` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 679 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_query_cancelled` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/core-executor/src/error.rs:679
`is_query_timeout` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 687 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_query_timeout` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/core-executor/src/error.rs:687
`executor_error` is public and takes `error: &Error` from its caller, and it calls itself at line 179 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `executor_error` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/core-executor/src/snowflake_error.rs:179
`status_code` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 85 with a piece of the document (and at line 86, line 87, line 88, line 89, line 90, line 91, line 92, line 93, line 94) — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `status_code` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-ui/src/error.rs:85
`query_id` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 149 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `query_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-ui/src/error.rs:149
`display_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 167 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `display_error_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-ui/src/error.rs:167
`debug_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 181 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `debug_error_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-ui/src/error.rs:181
`into_response` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 124 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `into_response` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-ui/src/error.rs:124
`display_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 145 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `display_error_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-snowflake-rest/src/server/error.rs:145
`query_id` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 137 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `query_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-snowflake-rest/src/server/error.rs:137
`debug_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 153 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `debug_error_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/api-snowflake-rest/src/server/error.rs:153
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 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 0/5 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.
`createMemoryVolumes` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`. — ui/seed.js:20
`createDatabases` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`. — ui/seed.js:48
`createSchemas` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`. — ui/seed.js:80
`createTables` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`. — ui/seed.js:167
`createWorksheets` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`. — ui/seed.js:226
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
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`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.
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.
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.
`ResponseData.row_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:97
`ResponseData.row_set_base_64` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:99
`ResponseData.row_set` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:101
`ResponseData.total` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:102
`ResponseData.query_result_format` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:104
`ResponseData.sql_state` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/api-snowflake-rest/src/models.rs:108
`QueryContext.async_query` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/core-executor/src/models.rs:39
`Config.defaults` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/core-metastore/src/models/table.rs:134
`Config.overrides` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/core-metastore/src/models/table.rs:135
`CachingCatalog.enable_information_schema` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/df-catalog/src/catalog.rs:15
`FunctionInfo.subcategory` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/embucket-functions/src/visitors/unimplemented/mod.rs:17
`CliOpts.cors_enabled` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/embucketd/src/cli.rs:131
What to do
Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
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.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`debug!` at line 64 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/lib.rs:64
`debug!` at line 66 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/lib.rs:66
`info!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/init.rs:25
`info!` at line 46 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/init.rs:46
`error!` at line 76 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/init.rs:76
`error!` at line 655 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/mod.rs:655
`error!` at line 759 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/mod.rs:759
`error!` at line 766 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-sqlite/src/vfs/mod.rs:766
`info!` at line 461 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-history/src/sqlite_history_store.rs:461
`error!` at line 110 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-history/src/entities/result_set.rs:110
`error!` at line 741 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core-executor/src/service.rs:741
Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`syn::parse2(input_cloned)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `stack_trace_style_impl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/error-stack-trace/src/stack.rs:31
`self.access_key_id.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:312
`self.secret_access_key.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:313
`self.region.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:314
`self.bucket.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:315
`self.file_storage_path.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:331
`fs::create_dir(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/cli.rs:334
`tokio::runtime::Builder::new_multi_thread().enable_all().on_thread_start({move||{#[cfg(feature="alloc-tracing")]if opts.alloc_tracing.unwrap_or(false){alloc_tracing::TRACE_ALLOCATOR.with(|cell|*cell.borrow_mut()=true);}}}).build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:127
`Config::new(&data_format)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:153
`opts.auth_demo_user.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/embucketd/src/main.rs:155, crates/embucketd/src/main.rs:183
`opts.auth_demo_password.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/embucketd/src/main.rs:156, crates/embucketd/src/main.rs:184
`opts.host.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:176
`opts.port` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:177
`opts.catalog_url.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:179
`opts.assets_port` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:195
`opts.object_store_backend()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:200
`` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×5) — crates/embucketd/src/main.rs:206, crates/embucketd/src/main.rs:229, crates/embucketd/src/main.rs:328, …
`helpers::resolve_ipv4(format!("{}:{}",static_web_config.host,static_web_config.port))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:325
`listener.local_addr()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/embucketd/src/main.rs:329, crates/embucketd/src/main.rs:348
`helpers::resolve_ipv4(format!("{host}:{port}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:344
`opts.timeout` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:350
`tracing_provider.shutdown()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:362
`Settings::load()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `slatedb_default_settings` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:369
`opentelemetry_otlp::SpanExporter::builder().with_tonic().build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `setup_tracing` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:378
`alloc_tracing::AllocLogLayer::write_to_file("./alloc.log")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `setup_tracing` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:408
`` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `shutdown_signal` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — crates/embucketd/src/main.rs:483, crates/embucketd/src/main.rs:504, crates/embucketd/src/main.rs:508
`signal::unix::signal(signal::unix::SignalKind::terminate())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `shutdown_signal` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucketd/src/main.rs:489
`res` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `http_req_with_headers` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucket-seed/src/requests/http.rs:88
`` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `http_req_with_headers` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/embucket-seed/src/requests/http.rs:92, crates/embucket-seed/src/requests/http.rs:135
`serde_json::from_str::<T>("null")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `http_req_with_headers` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/embucket-seed/src/requests/http.rs:97
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 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 — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 13% of this repository's production lines — rust (71,882 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — embucket Error context canceled spark-iceberg Warning context canceled mc Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: spark-iceberg Warning context canceled minio Error context canceled embucket Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build spark-iceberg Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~26704 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
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 — D21 withholds its case and prefix conventions rows: 11 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust 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. Aggregate roots were found in only one source directory (embucket-functions), which is a layered codebase, not two contexts. 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 (.rs), 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
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 — Rust suite
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
R4 Test Coverage — 8 test file(s) reach none of 174 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X24 Document value interpolated into markup unescaped — X24 reached only 13% of this repository's production lines — rust (71,882 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 13% of this repository's production lines — rust (71,882 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
ED1 · Handler temporal coupling· Blocking call on the event loop · ×11
Blocking call on the event loop: AllQueries.try_new calls `std::fs::read_to_string` crates/benchmarks/src/clickbench/run.rs:67— `AllQueries.try_new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: ConvertOpt.run calls `std::fs::create_dir_all` crates/benchmarks/src/tpch/convert.rs:108— `ConvertOpt.run` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: tpch.get_query_sql calls `std::fs::read_to_string` crates/benchmarks/src/tpch/mod.rs:257— `tpch.get_query_sql` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: SlateDBHistoryStore.new calls `std::fs::create_dir_all` crates/core-history/src/sqlite_history_store.rs:73— `SlateDBHistoryStore.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: SlateDBHistoryStore.new calls `std::fs::create_dir_all` crates/core-history/src/sqlite_history_store.rs:76— `SlateDBHistoryStore.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: SlatedbVfs.delete calls `block_on` crates/core-sqlite/src/vfs/mod.rs:210— `SlatedbVfs.delete` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: EmbucketIcebergCatalog.new calls `block_on` crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:44— `EmbucketIcebergCatalog.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: EmbucketIcebergCatalog.new calls `block_on` crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:51— `EmbucketIcebergCatalog.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: generate_implemented_functions.generate_implemented_functions_csv calls `std::fs::create_dir_all` crates/embucket-functions/src/bin/generate_implemented_functions.rs:82— `generate_implemented_functions.generate_implemented_functions_csv` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: generate_implemented_functions.generate_implemented_functions_csv calls `std::fs::write` crates/embucket-functions/src/bin/generate_implemented_functions.rs:86— `generate_implemented_functions.generate_implemented_functions_csv` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: src.load_openapi_spec calls `std::fs::read_to_string` crates/embucketd/src/main.rs:525— `src.load_openapi_spec` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Dual write (no outbox): CoreExecutionService.submit_query crates/core-executor/src/service.rs:616— `CoreExecutionService.submit_query` performs two independent DURABLE writes — a durable state write (`history_store.save_query_record`, :654) and a second independent durable store write — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox).
TodoComment ui/src/modules/shared/trees/trees-items.tsx:171— // TODO: Not the best place to put empty states for volumes — 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 ui/src/modules/shared/trees/trees-toolbar.tsx:9— // TODO: ??? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:31— // TODO: Double check keys hack — 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 ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:44— // TODO: Better not to reuse trees interface here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment ui/src/modules/shared/delete-worksheet-alert-dialog/delete-worksheet-alert-dialog.tsx:46— // TODO: Centralize logic for navigating and managing tabs — 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 ui/src/modules/shared/data-preview-table/data-preview-table.tsx:17— // TODO: Type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:30— // TODO: This naming is a joke — 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 ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:192— // TODO: Implement memory volume — 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 ui/src/modules/query/query-details.tsx:31— // TODO: DRY Progress, Status — 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 ui/src/modules/query/use-measure-query-results-height.tsx:5— // TODO: No way we do this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment ui/src/modules/home/home-page.tsx:45— // TODO: Hardcode — 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 ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets.tsx:28— // TODO: Hardcode — 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 ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-panel-table-columns.tsx:14— // TODO: Hardcode — 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 ui/src/modules/editor/editor-settings-store.ts:34— // TODO: Meh — 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 ui/src/modules/editor/editor-center-panel/editor-context-dropdown/use-sync-editor-context.ts:5— // TODO: DRY — 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 ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-databases.tsx:4— // TODO: DRY — 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 ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-schemas.tsx:4— // TODO: DRY — 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 ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown.tsx:33— // TODO: Tmp solution — 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 ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx:34— // TODO: EmptyContainer designed to be used for empty states strictly — 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 ui/src/components/ui/scroll-area.tsx:7— // TODO: Better to use viewportClassName instead of custom prop — 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 ui/src/components/data-table/data-table.tsx:47— // TODO: Double check index keys — 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 test/slt_runner/result.py:967— # TODO refactor: encapsulate logic, check if embucket_enabled: False — 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 test/slt_runner/parser/parser.py:100— # TODO: set snowflake's types. — 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 test/slt_runner/parser/parser.py:467— # TODO: collect error — 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 test/slt_runner/parser/parser.py:470— # TODO: collect error — 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.
+ 67 more in this group — see findings.md.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded crates/error-stack-trace/src/stack.rs:31— `syn::parse2(input_cloned)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `stack_trace_style_impl` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:312— `self.access_key_id.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:313— `self.secret_access_key.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:314— `self.region.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:315— `self.bucket.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:331— `self.file_storage_path.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/cli.rs:334— `fs::create_dir(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `object_store_backend` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:127— `tokio::runtime::Builder::new_multi_thread().enable_all().on_thread_start({move||{#[cfg(feature="alloc-tracing")]if opts.alloc_tracing.unwrap_or(false){alloc_tracing::TRACE_ALLOCATOR.with(|cell|*cell.borrow_mut()=true);}}}).build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:153— `Config::new(&data_format)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:155— `opts.auth_demo_user.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:156— `opts.auth_demo_password.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:176— `opts.host.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:177— `opts.port` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:179— `opts.catalog_url.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:183— `opts.auth_demo_user.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:184— `opts.auth_demo_password.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:195— `opts.assets_port` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:200— `opts.object_store_backend()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:206— `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:229— `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:325— `helpers::resolve_ipv4(format!("{}:{}",static_web_config.host,static_web_config.port))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:328— `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:329— `listener.local_addr()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:344— `helpers::resolve_ipv4(format!("{host}:{port}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/embucketd/src/main.rs:347— `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `async_main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
+ 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×25
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
IC1 · Incompleteness & stubs· Empty method body · ×19
Empty method body — does nothing with its inputs crates/core-sqlite/src/vfs/init.rs:17— `init` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/semi-structured/variant/visitors/array_agg.rs:60— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/semi-structured/variant/visitors/array_construct.rs:49— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/semi-structured/variant/visitors/array_construct_compact.rs:65— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/semi-structured/variant/visitors/type_rewrite.rs:38— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/semi-structured/variant/visitors/variant_element.rs:65— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/copy_into_identifiers.rs:58— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/functions_rewriter.rs:127— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/inline_aliases_in_query.rs:131— `substitute_aliases` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/inline_aliases_in_query.rs:197— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/json_element.rs:61— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/like_ilike_any.rs:131— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/rlike_regexp_expr_rewriter.rs:81— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/select_expr_aliases.rs:80— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/table_functions.rs:73— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/table_functions_cte_relation.rs:132— `inline_cte_refs_in_query` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/table_functions_cte_relation.rs:281— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/timestamp.rs:65— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/embucket-functions/src/visitors/top_limit.rs:93— `visit` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
D30 · Dependency Vulnerabilities· Medium CVE · ×17
embucket_functions::conversion::to_varchar::apply_numeric_format (cognitive 44) crates/embucket-functions/src/conversion/to_varchar.rs:304— embucket_functions::conversion::to_varchar::apply_numeric_format has cognitive complexity 44 (threshold 15). Drivers by points: if/else 28 (39 pts), boolean chains 5 (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.
embucket_functions::json::encode_duration_array (cognitive 35) crates/embucket-functions/src/json.rs:408— embucket_functions::json::encode_duration_array has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4 (12 pts), match/switch 2 (3 pts) (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
embucket_functions::conversion::to_binary::convert_string_to_binary (cognitive 32) crates/embucket-functions/src/conversion/to_binary.rs:182— embucket_functions::conversion::to_binary::convert_string_to_binary has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 3 (11 pts), loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embucket_functions::json::tokenize_path (cognitive 32) crates/embucket-functions/src/json.rs:940— embucket_functions::json::tokenize_path has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (10 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embucket_functions::json::encode_interval_array (cognitive 27) crates/embucket-functions/src/json.rs:493— embucket_functions::json::encode_interval_array has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (9 pts), match/switch 2 (3 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
embucket_functions::json::encode_timestamp_array (cognitive 26) crates/embucket-functions/src/json.rs:232— embucket_functions::json::encode_timestamp_array has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 4 (8 pts), match/switch 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.
embucket_functions::string-binary::hex_decode_binary::decode_hex_strings (cognitive 25) crates/embucket-functions/src/string-binary/hex_decode_binary.rs:123— embucket_functions::string-binary::hex_decode_binary::decode_hex_strings has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embucket_functions::string-binary::hex_decode_string::decode_hex_strings (cognitive 25) crates/embucket-functions/src/string-binary/hex_decode_string.rs:124— embucket_functions::string-binary::hex_decode_string::decode_hex_strings has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embucket_functions::conversion::to_timestamp::parse_decimal (cognitive 22) crates/embucket-functions/src/conversion/to_timestamp.rs:586— embucket_functions::conversion::to_timestamp::parse_decimal has cognitive complexity 22 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 6 (7 pts), match/switch 5 (7 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.
embucket_functions::datetime::date_part_extract::calculate_week_of_year (cognitive 21) crates/embucket-functions/src/datetime/date_part_extract.rs:290— embucket_functions::datetime::date_part_extract::calculate_week_of_year has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
embucket_functions::string-binary::strtok::process_split (cognitive 20) crates/embucket-functions/src/string-binary/strtok.rs:139— embucket_functions::string-binary::strtok::process_split has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 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.
embucket_functions::conversion::to_timestamp::try_parse_with_regex (cognitive 19) crates/embucket-functions/src/conversion/to_timestamp.rs:449— embucket_functions::conversion::to_timestamp::try_parse_with_regex has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embucket_functions::json::encode_time32_array (cognitive 19) crates/embucket-functions/src/json.rs:318— embucket_functions::json::encode_time32_array has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), match/switch 2 (3 pts) (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (embucket_functions::json::encode_time64_array) 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.
embucket_functions::json::encode_time64_array (cognitive 19) crates/embucket-functions/src/json.rs:363— embucket_functions::json::encode_time64_array has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), match/switch 2 (3 pts) (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (embucket_functions::json::encode_time32_array) 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.
embucket_functions::conversion::to_timestamp::build_timestamp_array_from_scalar_string (cognitive 18) crates/embucket-functions/src/conversion/to_timestamp.rs:401— embucket_functions::conversion::to_timestamp::build_timestamp_array_from_scalar_string has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (8 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.
embucket_functions::string-binary::randstr::cast_to_i64_with_numeric_error (cognitive 18) crates/embucket-functions/src/string-binary/randstr.rs:180— embucket_functions::string-binary::randstr::cast_to_i64_with_numeric_error has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×15
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×13
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×12
Recursive walk over a caller-supplied document has no depth cap REDACTED:127— `flatten` is public and takes `value: &Value` from its caller, and it calls itself at line 127 with a piece of the document (and at line 151) — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `flatten` 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 crates/core-executor/src/error.rs:679— `is_query_cancelled` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 679 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_query_cancelled` 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 crates/core-executor/src/error.rs:687— `is_query_timeout` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 687 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_query_timeout` 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 crates/core-executor/src/snowflake_error.rs:179— `executor_error` is public and takes `error: &Error` from its caller, and it calls itself at line 179 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `executor_error` 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 crates/api-ui/src/error.rs:85— `status_code` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 85 with a piece of the document (and at line 86, line 87, line 88, line 89, line 90, line 91, line 92, line 93, line 94) — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `status_code` 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 crates/api-ui/src/error.rs:149— `query_id` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 149 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `query_id` 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 crates/api-ui/src/error.rs:167— `display_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 167 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `display_error_message` 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 crates/api-ui/src/error.rs:181— `debug_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 181 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `debug_error_message` 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 crates/api-ui/src/error.rs:124— `into_response` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 124 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `into_response` 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 crates/api-snowflake-rest/src/server/error.rs:145— `display_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 145 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `display_error_message` 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 crates/api-snowflake-rest/src/server/error.rs:137— `query_id` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 137 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `query_id` 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 crates/api-snowflake-rest/src/server/error.rs:153— `debug_error_message` is public and takes a `Error` as its receiver from its caller, and it calls itself at line 153 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. 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. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `debug_error_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:97— `ResponseData.row_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:99— `ResponseData.row_set_base_64` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:101— `ResponseData.row_set` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:102— `ResponseData.total` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:104— `ResponseData.query_result_format` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/api-snowflake-rest/src/models.rs:108— `ResponseData.sql_state` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/core-executor/src/models.rs:39— `QueryContext.async_query` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/core-metastore/src/models/table.rs:134— `Config.defaults` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/core-metastore/src/models/table.rs:135— `Config.overrides` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/df-catalog/src/catalog.rs:15— `CachingCatalog.enable_information_schema` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/embucket-functions/src/visitors/unimplemented/mod.rs:17— `FunctionInfo.subcategory` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/embucketd/src/cli.rs:131— `CliOpts.cors_enabled` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Duplicated block (10 lines × 2) crates/api-sessions/src/layer.rs:29— crates/api-sessions/src/layer.rs:29-38 | crates/api-sessions/src/layer.rs:46-55 — 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 `crates/api-sessions/src/layer.rs:29` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) REDACTED:99— REDACTED:99-108 | crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:117-126 — 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 `REDACTED:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:1819— REDACTED:1819-1828 | REDACTED:1873-1882 — 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:1819` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/embucket-functions/src/conversion/to_binary.rs:138— crates/embucket-functions/src/conversion/to_binary.rs:138-147 | crates/embucket-functions/src/conversion/to_binary.rs:151-160 — 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 `crates/embucket-functions/src/conversion/to_binary.rs:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/embucket-functions/src/datetime/last_day.rs:190— crates/embucket-functions/src/datetime/last_day.rs:190-199 | crates/embucket-functions/src/datetime/previous_day.rs:96-105 — before extracting anything, compare `crates/embucket-functions/src/datetime/last_day.rs` and `crates/embucket-functions/src/datetime/previous_day.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `crates/embucket-functions/src/datetime/last_day.rs:190` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/embucket-functions/src/datetime/next_day.rs:75— crates/embucket-functions/src/datetime/next_day.rs:75-84 | crates/embucket-functions/src/datetime/previous_day.rs:77-86 — 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 (10 lines × 2) crates/embucket-functions/src/semi-structured/array/array_generate_range.rs:101— crates/embucket-functions/src/semi-structured/array/array_generate_range.rs:101-110 | crates/embucket-functions/src/semi-structured/array/array_generate_range.rs:112-121 — 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 `crates/embucket-functions/src/semi-structured/array/array_generate_range.rs:101` 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 (10 lines × 2) crates/embucket-functions/src/semi-structured/array/array_insert.rs:141— crates/embucket-functions/src/semi-structured/array/array_insert.rs:141-150 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:140-149 — 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 `crates/embucket-functions/src/semi-structured/array/array_insert.rs:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:101— crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:101-110 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:108-117 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_remove_at.rs` and `crates/embucket-functions/src/semi-structured/array/array_slice.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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 `crates/embucket-functions/src/semi-structured/array/array_remove_at.rs: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 (10 lines × 2) REDACTED:121— REDACTED:121-130 | REDACTED:145-154 — 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:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/embucket-functions/src/visitors/like_ilike_any.rs:19— crates/embucket-functions/src/visitors/like_ilike_any.rs:19-28 | crates/embucket-functions/src/visitors/like_ilike_any.rs:43-52 — 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 `crates/embucket-functions/src/visitors/like_ilike_any.rs:19` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
FileTooLong: REDACTED REDACTED— FileTooLong — 2510 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: UserQuery (2 blocks, 124-2938). The bar is 500 significant lines; this is 2010 over it, 5.02× 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: src/metastore.rs crates/core-metastore/src/metastore.rs— FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: SlateDBMetastore (4 blocks, 109-885). The bar is 500 significant lines; this is 185 over it, 1.37× 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: src/json.rs crates/embucket-functions/src/json.rs— FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 38 free functions. The bar is 500 significant lines; this is 173 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/sqlite_history_store.rs crates/core-history/src/sqlite_history_store.rs— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: SlateDBHistoryStore (5 blocks, 53-793). The bar is 500 significant lines; this is 142 over it, 1.28× 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: src/service.rs crates/core-executor/src/service.rs— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 86% of them inside a single declaration: CoreExecutionService (3 blocks, 153-928). The bar is 500 significant lines; this is 115 over it, 1.23× 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: src/utils.rs crates/core-executor/src/utils.rs— FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 67 over it, 1.13× 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: src/error.rs crates/core-executor/src/error.rs— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: Error (3 blocks, 20-702). The bar is 500 significant lines; this is 51 over it, 1.10× 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: conversion/to_timestamp.rs crates/embucket-functions/src/conversion/to_timestamp.rs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: vfs/mod.rs crates/core-sqlite/src/vfs/mod.rs— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: SlatedbVfs (3 blocks, 55-689). The bar is 500 significant lines; this is 8 over it, 1.02× 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: src/vfs.rs crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 3 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (8 lines × 2) crates/core-history/src/sqlite_history_store.rs:591— crates/core-history/src/sqlite_history_store.rs:591-598 | crates/core-history/src/sqlite_history_store.rs:674-681 — 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 `crates/core-history/src/sqlite_history_store.rs:591` 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 (8 lines × 2) crates/core-metastore/src/metastore.rs:550— crates/core-metastore/src/metastore.rs:550-557 | crates/core-metastore/src/metastore.rs:704-711 — 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 `crates/core-metastore/src/metastore.rs:550` 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) crates/embucket-functions/src/conversion/to_boolean.rs:77— crates/embucket-functions/src/conversion/to_boolean.rs:77-84 | crates/embucket-functions/src/semi-structured/conversion/as_func.rs:66-73 — 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 `crates/embucket-functions/src/conversion/to_boolean.rs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/embucket-functions/src/encryption/decrypt_raw.rs:246— crates/embucket-functions/src/encryption/decrypt_raw.rs:246-253 | crates/embucket-functions/src/encryption/encrypt_raw.rs:213-220 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 after the matched lines, `crates/embucket-functions/src/encryption/decrypt_raw.rs:254` calls `value` and `crates/embucket-functions/src/encryption/encrypt_raw.rs:221` 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 (8 lines × 2) crates/embucket-functions/src/regexp/regexp_substr.rs:97— crates/embucket-functions/src/regexp/regexp_substr.rs:97-104 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:99-106 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_substr.rs` and `crates/embucket-functions/src/regexp/regexp_substr_all.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 226 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 `crates/embucket-functions/src/regexp/regexp_substr.rs:97` 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 after the matched lines, `crates/embucket-functions/src/regexp/regexp_substr_all.rs:107` calls `from` and `crates/embucket-functions/src/regexp/regexp_substr.rs:105` 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 (8 lines × 2) crates/embucket-functions/src/semi-structured/array/array_compact.rs:96— crates/embucket-functions/src/semi-structured/array/array_compact.rs:96-103 | crates/embucket-functions/src/semi-structured/array/array_distinct.rs:107-114 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_compact.rs` and `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `crates/embucket-functions/src/semi-structured/array/array_compact.rs:96` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/embucket-functions/src/semi-structured/array/array_insert.rs:114— crates/embucket-functions/src/semi-structured/array/array_insert.rs:114-121 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:103-110 — 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 `crates/embucket-functions/src/semi-structured/array/array_insert.rs:114` 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) crates/embucket-functions/src/semi-structured/array/array_max.rs:143— crates/embucket-functions/src/semi-structured/array/array_max.rs:143-150 | crates/embucket-functions/src/semi-structured/array/array_min.rs:143-150 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_max.rs` and `crates/embucket-functions/src/semi-structured/array/array_min.rs` as WHOLE FILES: this scan already matched 8 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. 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 `crates/embucket-functions/src/semi-structured/array/array_max.rs:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/embucket-functions/src/string-binary/substr.rs:256— crates/embucket-functions/src/string-binary/substr.rs:256-263 | crates/embucket-functions/src/string-binary/substr.rs:266-273 — 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 `crates/embucket-functions/src/string-binary/substr.rs:256` 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 (8 lines × 2) crates/embucket-functions/src/semi-structured/variant/visitors/array_agg.rs:20— crates/embucket-functions/src/semi-structured/variant/visitors/array_agg.rs:20-27 | crates/embucket-functions/src/semi-structured/variant/visitors/array_construct_compact.rs:19-29 — 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 `crates/embucket-functions/src/semi-structured/variant/visitors/array_agg.rs:20` 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.
MethodTooLong: UserQuery.show_query REDACTED:1759— MethodTooLong — show_query runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UserQuery.merge_query REDACTED:1329— MethodTooLong — merge_query runs 154 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: MergeCOWFilterStream.poll_next crates/core-executor/src/datafusion/physical_plan/merge.rs:348— MethodTooLong — poll_next runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: Div0Func.invoke_with_args crates/embucket-functions/src/numeric/div0.rs:91— MethodTooLong — invoke_with_args runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToTimestampFunc.invoke_with_args crates/embucket-functions/src/conversion/to_timestamp.rs:235— MethodTooLong — invoke_with_args runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: UserQuery.execute REDACTED:311— MethodTooLong — execute runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UserQuery.drop_query REDACTED:678— MethodTooLong — drop_query runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: ToTimeFunc.invoke_with_args crates/embucket-functions/src/conversion/to_time.rs:113— MethodTooLong — invoke_with_args runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: DecryptRawFunc.invoke_with_args crates/embucket-functions/src/encryption/decrypt_raw.rs:178— MethodTooLong — invoke_with_args runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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.
Duplicated block (6 lines × 2) crates/df-catalog/src/information_schema/columns.rs:228— crates/df-catalog/src/information_schema/columns.rs:228-233 | crates/df-catalog/src/information_schema/tables.rs:104-109 — 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 `crates/df-catalog/src/information_schema/columns.rs:228` 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) crates/df-catalog/src/information_schema/parameters.rs:131— crates/df-catalog/src/information_schema/parameters.rs:131-136 | crates/df-catalog/src/information_schema/routines.rs:129-134 — 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 `crates/df-catalog/src/information_schema/parameters.rs:131` 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) crates/embucket-functions/src/json.rs:74— crates/embucket-functions/src/json.rs:74-79 | crates/embucket-functions/src/json.rs:305-310 — 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 `crates/embucket-functions/src/json.rs:74` 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) crates/embucket-functions/src/json.rs:479— crates/embucket-functions/src/json.rs:479-484 | crates/embucket-functions/src/json.rs:872-877 — 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) crates/embucket-functions/src/semi-structured/array/is_array.rs:66— crates/embucket-functions/src/semi-structured/array/is_array.rs:66-71 | crates/embucket-functions/src/semi-structured/object/is_object.rs:69-74 — 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 `crates/embucket-functions/src/semi-structured/array/is_array.rs:66` 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) crates/embucket-functions/src/string-binary/replace.rs:109— crates/embucket-functions/src/string-binary/replace.rs:109-114 | crates/embucket-functions/src/string-binary/replace.rs:133-138 — 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 `crates/embucket-functions/src/string-binary/replace.rs:109` 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, `crates/embucket-functions/src/string-binary/replace.rs:115` calls `Some`, `replace` and `crates/embucket-functions/src/string-binary/replace.rs:139` 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 (6 lines × 2) crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:91— crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:91-97 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:93-98 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_remove_at.rs` and `crates/embucket-functions/src/semi-structured/array/array_slice.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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 (6 lines × 2) crates/api-ui/src/web_assets/handler.rs:54— crates/api-ui/src/web_assets/handler.rs:54-59 | crates/api-ui/src/web_assets/handler.rs:100-105 — 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 `crates/api-ui/src/web_assets/handler.rs:54` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/embucket-functions/src/datetime/time_from_parts.rs:145— crates/embucket-functions/src/datetime/time_from_parts.rs:145-150 | crates/embucket-functions/src/datetime/timestamp_from_parts.rs:280-285 — 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 (14 lines × 2) crates/core-executor/src/datafusion/rewriters/session_context.rs:166— crates/core-executor/src/datafusion/rewriters/session_context.rs:166-179 | crates/embucket-functions/src/table/result_scan.rs:155-168 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/embucket-functions/src/aggregate/array_union_agg.rs:166— crates/embucket-functions/src/aggregate/array_union_agg.rs:166-179 | crates/embucket-functions/src/aggregate/array_union_agg.rs:232-245 — 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 `crates/embucket-functions/src/aggregate/array_union_agg.rs:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/embucket-functions/src/aggregate/array_union_agg.rs:180` calls `Some` and `crates/embucket-functions/src/aggregate/array_union_agg.rs:246` 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 (14 lines × 2) crates/embucket-functions/src/conversion/to_decimal.rs:280— crates/embucket-functions/src/conversion/to_decimal.rs:280-293 | crates/embucket-functions/src/conversion/to_decimal.rs:295-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 `crates/embucket-functions/src/conversion/to_decimal.rs:280` 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 (14 lines × 2) crates/embucket-functions/src/datetime/last_day.rs:175— crates/embucket-functions/src/datetime/last_day.rs:175-188 | crates/embucket-functions/src/datetime/previous_day.rs:81-94 — before extracting anything, compare `crates/embucket-functions/src/datetime/last_day.rs` and `crates/embucket-functions/src/datetime/previous_day.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `crates/embucket-functions/src/datetime/last_day.rs:175` 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 (14 lines × 2) crates/embucket-functions/src/datetime/next_day.rs:41— crates/embucket-functions/src/datetime/next_day.rs:41-54 | crates/embucket-functions/src/datetime/previous_day.rs:43-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/embucket-functions/src/semi-structured/variant/visitors/array_construct.rs:32— crates/embucket-functions/src/semi-structured/variant/visitors/array_construct.rs:32-45 | crates/embucket-functions/src/semi-structured/variant/visitors/variant_element.rs:48-61 — 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 `crates/embucket-functions/src/semi-structured/variant/visitors/array_construct.rs:32` 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 (14 lines × 2) crates/embucket-functions/src/string-binary/hex_decode_binary.rs:44— crates/embucket-functions/src/string-binary/hex_decode_binary.rs:44-57 | crates/embucket-functions/src/string-binary/hex_decode_string.rs:45-58 — before extracting anything, compare `crates/embucket-functions/src/string-binary/hex_decode_binary.rs` and `crates/embucket-functions/src/string-binary/hex_decode_string.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 (14 lines × 2) REDACTED:1804— REDACTED:1804-1817 | REDACTED:1830-1843 — 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 (9 lines × 2) crates/embucket-functions/src/geospatial/measurement/contains.rs:98— crates/embucket-functions/src/geospatial/measurement/contains.rs:98-106 | crates/embucket-functions/src/geospatial/measurement/distance.rs:101-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) crates/embucket-functions/src/json.rs:245— crates/embucket-functions/src/json.rs:245-253 | crates/embucket-functions/src/json.rs:415-423 — 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 `crates/embucket-functions/src/json.rs:245` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) crates/embucket-functions/src/json.rs:255— crates/embucket-functions/src/json.rs:255-263 | crates/embucket-functions/src/json.rs:425-433 — 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 `crates/embucket-functions/src/json.rs:255` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) crates/embucket-functions/src/semi-structured/array/array_cat.rs:97— crates/embucket-functions/src/semi-structured/array/array_cat.rs:97-105 | crates/embucket-functions/src/semi-structured/array/array_cat.rs:119-127 — 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 `crates/embucket-functions/src/semi-structured/array/array_cat.rs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/embucket-functions/src/semi-structured/array/array_cat.rs:107— crates/embucket-functions/src/semi-structured/array/array_cat.rs:107-115 | crates/embucket-functions/src/semi-structured/array/array_cat.rs:152-160 — 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 `crates/embucket-functions/src/semi-structured/array/array_cat.rs:107` 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 (9 lines × 2) crates/embucket-functions/src/visitors/functions_rewriter.rs:75— crates/embucket-functions/src/visitors/functions_rewriter.rs:75-83 | crates/embucket-functions/src/visitors/functions_rewriter.rs:90-98 — 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 `crates/embucket-functions/src/visitors/functions_rewriter.rs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:99— REDACTED:99-107 | REDACTED:110-118 — 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:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:116— crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:116-124 | crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:127-135 — 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 `crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:116` 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.
Hotspot: REDACTED REDACTED:311— REDACTED changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in UserQuery::execute at line 311. 8 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06: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: crates/embucket-functions/src/conversion/to_timestamp.rs crates/embucket-functions/src/conversion/to_timestamp.rs:235— crates/embucket-functions/src/conversion/to_timestamp.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in ToTimestampFunc::invoke_with_args at line 235. 5 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/embucket-functions/src/conversion/to_timestamp.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core-executor/src/snowflake_error.rs crates/core-executor/src/snowflake_error.rs:375— crates/core-executor/src/snowflake_error.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in core_executor::snowflake_error::datafusion_error at line 375. 2 of those changes were fix/bug commits, 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/core-executor/src/snowflake_error.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/embucket-functions/src/visitors/functions_rewriter.rs crates/embucket-functions/src/visitors/functions_rewriter.rs:15— crates/embucket-functions/src/visitors/functions_rewriter.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in FunctionsRewriter::post_visit_expr at line 15. 2 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/embucket-functions/src/visitors/functions_rewriter.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core-executor/src/datafusion/type_planner.rs crates/core-executor/src/datafusion/type_planner.rs:24— crates/core-executor/src/datafusion/type_planner.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in CustomTypePlanner::plan_type at line 24. 1 of those changes was a fix/bug commit, and the other 2 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/core-executor/src/datafusion/type_planner.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core-executor/src/datafusion/rewriters/session_context.rs crates/core-executor/src/datafusion/rewriters/session_context.rs:103— crates/core-executor/src/datafusion/rewriters/session_context.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ExprRewriter::f_up at line 103. 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/core-executor/src/datafusion/rewriters/session_context.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/embucket-functions/src/semi-structured/typeof_func.rs crates/embucket-functions/src/semi-structured/typeof_func.rs:58— crates/embucket-functions/src/semi-structured/typeof_func.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in TypeofFunc::invoke_with_args at line 58. 1 of those changes was a fix/bug commit, and the other 1 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/embucket-functions/src/semi-structured/typeof_func.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (11 lines × 2) crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:233— crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:233-243 | crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:261-271 — 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 `crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:233` 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) crates/embucket-functions/src/json.rs:55— crates/embucket-functions/src/json.rs:55-65 | crates/embucket-functions/src/json.rs:74-84 — 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 `crates/embucket-functions/src/json.rs:55` 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 (11 lines × 2) crates/embucket-functions/src/json.rs:950— crates/embucket-functions/src/json.rs:950-960 | crates/embucket-functions/src/json.rs:964-974 — 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 `crates/embucket-functions/src/json.rs:950` 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) crates/embucket-functions/src/string-binary/insert.rs:101— crates/embucket-functions/src/string-binary/insert.rs:101-111 | crates/embucket-functions/src/string-binary/jarowinkler_similarity.rs:61-71 — 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 (11 lines × 2) crates/embucket-functions/src/json.rs:468— crates/embucket-functions/src/json.rs:468-478 | crates/embucket-functions/src/json.rs:844-854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/embucket-functions/src/session/last_query_id.rs:22— crates/embucket-functions/src/session/last_query_id.rs:22-32 | crates/embucket-functions/src/system/cancel_query.rs:44-54 — 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 (11 lines × 2) crates/embucket-seed/src/requests/service_client.rs:210— crates/embucket-seed/src/requests/service_client.rs:210-220 | crates/embucket-seed/src/requests/service_client.rs:250-260 — 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 `crates/embucket-seed/src/requests/service_client.rs:210` 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.
ClassTooLong: UserQuery REDACTED:124— ClassTooLong — 2033 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 58 methods, 2 blocks, lines 124-2938. The bar is 400 significant lines; this is 1633 over it, 5.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SlateDBHistoryStore crates/core-history/src/sqlite_history_store.rs:53— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 5 blocks, lines 53-793. The bar is 400 significant lines; this is 186 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.
ClassTooLong: SlateDBMetastore crates/core-metastore/src/metastore.rs:109— ClassTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 4 blocks, lines 109-885. The bar is 400 significant lines; this is 170 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CoreExecutionService crates/core-executor/src/service.rs:153— ClassTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 153-928. The bar is 400 significant lines; this is 126 over it, 1.32× 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: Error crates/core-executor/src/error.rs:20— ClassTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 3 blocks, lines 20-702. The bar is 400 significant lines; this is 105 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: SlatedbVfs crates/core-sqlite/src/vfs/mod.rs:55— ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 55-689. The bar is 400 significant lines; this is 2 over it, 1.01× 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.
FunctionTooLong: core_executor::snowflake_error::datafusion_error crates/core-executor/src/snowflake_error.rs:375— FunctionTooLong — core_executor::snowflake_error::datafusion_error runs 186 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: create-volume-dialog-form.CreateVolumeDialogForm ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:112— FunctionTooLong — CreateVolumeDialogForm runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: embucketd::async_main crates/embucketd/src/main.rs:143— FunctionTooLong — embucketd::async_main runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: editor-center-panel.EditorCenterPanel ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx:30— FunctionTooLong — EditorCenterPanel runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: table-data-upload-dialog.TableDataUploadDialog ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:32— FunctionTooLong — TableDataUploadDialog runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: editor-panels-state-provider.EditorPanelsStateProvider ui/src/modules/editor/editor-panels-state-provider.tsx:57— FunctionTooLong — EditorPanelsStateProvider runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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.
Duplicated block (5 lines × 2) crates/core-executor/src/datafusion/rewriters/session_context.rs:61— crates/core-executor/src/datafusion/rewriters/session_context.rs:61-65 | crates/embucket-functions/src/table/result_scan.rs:47-51 — 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 `crates/core-executor/src/datafusion/rewriters/session_context.rs:61` 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) REDACTED:3121— REDACTED:3121-3126 | REDACTED:3137-3141 — 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:3121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/embucket-functions/src/conversion/to_varchar.rs:446— crates/embucket-functions/src/conversion/to_varchar.rs:446-450 | crates/embucket-functions/src/conversion/to_varchar.rs:453-457 — 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 `crates/embucket-functions/src/conversion/to_varchar.rs:446` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/embucket-functions/src/aggregate/array_union_agg.rs:270— crates/embucket-functions/src/aggregate/array_union_agg.rs:270-274 | crates/embucket-functions/src/aggregate/array_unique_agg.rs:120-124 — 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 (5 lines × 2) crates/embucket-functions/src/aggregate/array_union_agg.rs:318— crates/embucket-functions/src/aggregate/array_union_agg.rs:318-322 | crates/embucket-functions/src/aggregate/array_unique_agg.rs:145-149 — 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 (5 lines × 2) crates/embucket-functions/src/semi-structured/array/array_slice.rs:113— crates/embucket-functions/src/semi-structured/array/array_slice.rs:113-117 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:121-125 — 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 `crates/embucket-functions/src/semi-structured/array/array_slice.rs:113` 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.
UserQuery::drop_query (cognitive 23) REDACTED:678— UserQuery::drop_query has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 5 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserQuery::show_query (cognitive 23) REDACTED:1759— UserQuery::show_query has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserQuery::convert_batches_to_exprs (cognitive 17) REDACTED:2443— UserQuery::convert_batches_to_exprs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), boolean chains 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.
UserQuery::merge_query (cognitive 16) REDACTED:1329— UserQuery::merge_query has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UserQuery::get_table_path (cognitive 16) REDACTED:2589— UserQuery::get_table_path has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 2 (4 pts) (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/embucket-functions/src/json.rs:182— crates/embucket-functions/src/json.rs:182-194 | crates/embucket-functions/src/json.rs:197-209 | crates/embucket-functions/src/json.rs:713-725 | crates/embucket-functions/src/json.rs:728-740 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/embucket-functions/src/json.rs:589— crates/embucket-functions/src/json.rs:589-602 | crates/embucket-functions/src/json.rs:605-618 | crates/embucket-functions/src/json.rs:621-634 | crates/embucket-functions/src/json.rs:637-650 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/embucket-functions/src/regexp/regexp_instr.rs:72— crates/embucket-functions/src/regexp/regexp_instr.rs:72-119 | crates/embucket-functions/src/regexp/regexp_replace.rs:62-100 | crates/embucket-functions/src/regexp/regexp_substr.rs:68-106 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:70-109 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/embucket-functions/src/semi-structured/array/array_append.rs:85— crates/embucket-functions/src/semi-structured/array/array_append.rs:85-122 | crates/embucket-functions/src/semi-structured/array/array_prepend.rs:71-114 | crates/embucket-functions/src/semi-structured/array/array_remove.rs:79-152 | crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:89-156 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/embucket-functions/src/semi-structured/array/array_except.rs:78— crates/embucket-functions/src/semi-structured/array/array_except.rs:78-149 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:81-148 | crates/embucket-functions/src/semi-structured/array/arrays_overlap.rs:74-157 | crates/embucket-functions/src/semi-structured/array/arrays_to_object.rs:70-166 — 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×5
Edited copy of a member (15 corresponding lines) crates/api-sessions/src/session.rs:116— crates/api-sessions/src/session.rs:116-132 | crates/api-ui/src/auth/handlers.rs:31-45 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) REDACTED:2734— REDACTED:2734-2748 | REDACTED:2750-2769 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/df-catalog/src/information_schema/parameters.rs:48— crates/df-catalog/src/information_schema/parameters.rs:48-62 | crates/df-catalog/src/information_schema/routines.rs:43-59 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/df-catalog/src/catalogs/slatedb/queries.rs:41— crates/df-catalog/src/catalogs/slatedb/queries.rs:41-55 | crates/df-catalog/src/catalogs/slatedb/tables.rs:41-56 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/df-catalog/src/information_schema/parameters.rs:70— crates/df-catalog/src/information_schema/parameters.rs:70-85 | crates/df-catalog/src/information_schema/routines.rs:67-81 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) crates/df-catalog/src/information_schema/tables.rs:88— crates/df-catalog/src/information_schema/tables.rs:88-101 | crates/df-catalog/src/information_schema/views.rs:89-100 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/embucket-functions/src/aggregate/array_unique_agg.rs:101— crates/embucket-functions/src/aggregate/array_unique_agg.rs:101-112 | crates/embucket-functions/src/aggregate/array_unique_agg.rs:131-142 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/core-history/src/slatedb_history_store.rs:88— crates/core-history/src/slatedb_history_store.rs:88-105 | crates/core-history/src/slatedb_history_store.rs:186-197 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/core-executor/src/dedicated_executor.rs:699— crates/core-executor/src/dedicated_executor.rs:699-712 | crates/core-executor/src/dedicated_executor.rs:719-730 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/embucket-functions/src/semi-structured/array/array_construct.rs:22— crates/embucket-functions/src/semi-structured/array/array_construct.rs:22-33 | crates/embucket-functions/src/semi-structured/object/object_construct.rs:22-34 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 3) REDACTED:326— REDACTED:326-336 | crates/api-ui/src/volumes/handlers.rs:284-293 | crates/api-ui/src/worksheets/handlers.rs:86-95 — 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 `REDACTED:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/api-ui/src/worksheets/handlers.rs:96` calls `downcast_int64_column`, `context` and `REDACTED:337` 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) crates/embucket-functions/src/conversion/to_timestamp.rs:269— crates/embucket-functions/src/conversion/to_timestamp.rs:269-278 | crates/embucket-functions/src/conversion/to_timestamp.rs:280-289 | crates/embucket-functions/src/conversion/to_timestamp.rs:291-300 — 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 `crates/embucket-functions/src/conversion/to_timestamp.rs:269` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) crates/embucket-functions/src/conversion/to_timestamp.rs:614— crates/embucket-functions/src/conversion/to_timestamp.rs:614-623 | crates/embucket-functions/src/conversion/to_timestamp.rs:625-634 | crates/embucket-functions/src/conversion/to_timestamp.rs:636-645 — 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 `crates/embucket-functions/src/conversion/to_timestamp.rs:614` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) crates/embucket-functions/src/semi-structured/array/array_distinct.rs:93— crates/embucket-functions/src/semi-structured/array/array_distinct.rs:93-102 | crates/embucket-functions/src/semi-structured/array/array_max.rs:129-138 | crates/embucket-functions/src/semi-structured/array/array_min.rs:129-138 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` and `crates/embucket-functions/src/semi-structured/array/array_max.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 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 `crates/embucket-functions/src/semi-structured/array/array_distinct.rs: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 (10 lines × 3) crates/embucket-functions/src/semi-structured/object/object_delete.rs:120— crates/embucket-functions/src/semi-structured/object/object_delete.rs:120-129 | crates/embucket-functions/src/semi-structured/object/object_insert.rs:178-187 | crates/embucket-functions/src/semi-structured/object/object_pick.rs:124-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/semi-structured/object/object_delete.rs:120` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
X2 · Cancellation propagation· Async function without AbortSignal · ×5
Async function without AbortSignal: createMemoryVolumes ui/seed.js:20— `createMemoryVolumes` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`.
Async function without AbortSignal: createDatabases ui/seed.js:48— `createDatabases` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`.
Async function without AbortSignal: createSchemas ui/seed.js:80— `createSchemas` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`.
Async function without AbortSignal: createTables ui/seed.js:167— `createTables` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`.
Async function without AbortSignal: createWorksheets ui/seed.js:226— `createWorksheets` awaits `apiClient.post(…)` 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: `apiClient.post(url, { signal })`.
core_executor::utils::convert_record_batches (cognitive 27) crates/core-executor/src/utils.rs:209— core_executor::utils::convert_record_batches has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
core_executor::query::merge_clause_projection (cognitive 25) REDACTED:2966— core_executor::query::merge_clause_projection has cognitive complexity 25 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (9 pts), match/switch 2 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
core_executor::snowflake_error::datafusion_error (cognitive 24) crates/core-executor/src/snowflake_error.rs:375— core_executor::snowflake_error::datafusion_error has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 5 (11 pts) (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.
core_executor::query::create_file_format (cognitive 19) REDACTED:3488— core_executor::query::create_file_format has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) crates/df-catalog/src/information_schema/parameters.rs:130— crates/df-catalog/src/information_schema/parameters.rs:130-146 | crates/df-catalog/src/information_schema/routines.rs:128-146 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) crates/embucket-functions/src/json.rs:762— crates/embucket-functions/src/json.rs:762-778 | crates/embucket-functions/src/json.rs:781-797 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) crates/core-metastore/src/metastore.rs:161— crates/core-metastore/src/metastore.rs:161-182 | crates/core-metastore/src/metastore.rs:193-209 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) crates/api-sessions/src/layer.rs:65— crates/api-sessions/src/layer.rs:65-81 | crates/api-ui/src/auth/handlers.rs:117-133 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) crates/df-catalog/src/catalogs/slatedb/history_store_schema.rs:59— crates/df-catalog/src/catalogs/slatedb/history_store_schema.rs:59-71 | crates/df-catalog/src/catalogs/slatedb/metastore_schema.rs:58-72 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/df-catalog/src/information_schema/parameters.rs:116— crates/df-catalog/src/information_schema/parameters.rs:116-128 | crates/df-catalog/src/information_schema/routines.rs:113-126 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/embucket-functions/src/json.rs:152— crates/embucket-functions/src/json.rs:152-164 | crates/embucket-functions/src/json.rs:167-179 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/core-executor/src/dedicated_executor.rs:827— crates/core-executor/src/dedicated_executor.rs:827-842 | crates/core-executor/src/dedicated_executor.rs:844-856 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) REDACTED:1021— REDACTED:1021-1033 | REDACTED:1081-1093 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:1076` calls `clone`, `resolve_table_object_name`, `into` and `REDACTED:1018` 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 (13 lines × 2) crates/embucket-functions/src/semi-structured/array/array_remove.rs:94— crates/embucket-functions/src/semi-structured/array/array_remove.rs:94-106 | crates/embucket-functions/src/semi-structured/array/array_remove.rs:133-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.
Duplicated block (13 lines × 2) crates/embucket-functions/src/string-binary/substr.rs:592— crates/embucket-functions/src/string-binary/substr.rs:592-604 | crates/embucket-functions/src/string-binary/substr.rs:657-669 — 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 `crates/embucket-functions/src/string-binary/substr.rs:592` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/df-catalog/src/information_schema/config.rs:336— crates/df-catalog/src/information_schema/config.rs:336-348 | crates/df-catalog/src/information_schema/config.rs:350-362 — 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 `crates/df-catalog/src/information_schema/config.rs:336` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) REDACTED:2229— REDACTED:2229-2237 | REDACTED:2259-2267 | REDACTED:2299-2307 — 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:2229` 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, `REDACTED:2227` calls `schema`, `as_arrow`, `clone` and `REDACTED:2258` 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 (9 lines × 3) crates/embucket-functions/src/conversion/to_binary.rs:112— crates/embucket-functions/src/conversion/to_binary.rs:112-120 | crates/embucket-functions/src/string-binary/hex_decode_binary.rs:88-96 | crates/embucket-functions/src/string-binary/hex_decode_string.rs:89-97 — before extracting anything, compare `crates/embucket-functions/src/string-binary/hex_decode_binary.rs` and `crates/embucket-functions/src/string-binary/hex_decode_string.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 `crates/embucket-functions/src/conversion/to_binary.rs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/embucket-functions/src/json.rs:265— crates/embucket-functions/src/json.rs:265-273 | crates/embucket-functions/src/json.rs:370-378 | crates/embucket-functions/src/json.rs:435-443 — 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 `crates/embucket-functions/src/json.rs:265` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 3) crates/embucket-functions/src/semi-structured/array/array_remove.rs:106— crates/embucket-functions/src/semi-structured/array/array_remove.rs:106-114 | crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:114-122 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:127-135 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_remove_at.rs` and `crates/embucket-functions/src/semi-structured/array/array_slice.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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 `crates/embucket-functions/src/semi-structured/array/array_remove.rs:106` 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) crates/df-catalog/src/catalog.rs:147— crates/df-catalog/src/catalog.rs:147-154 | crates/df-catalog/src/catalog.rs:172-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/embucket-functions/src/string-binary/substr.rs:292— crates/embucket-functions/src/string-binary/substr.rs:292-298 | crates/embucket-functions/src/string-binary/substr.rs:332-338 — 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 `crates/embucket-functions/src/string-binary/substr.rs:292` 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) crates/embucket-functions/src/string-binary/substr.rs:312— crates/embucket-functions/src/string-binary/substr.rs:312-318 | crates/embucket-functions/src/string-binary/substr.rs:350-356 — 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 `crates/embucket-functions/src/string-binary/substr.rs:312` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) crates/embucket-functions/src/datetime/add_months.rs:83— crates/embucket-functions/src/datetime/add_months.rs:83-91 | crates/embucket-functions/src/datetime/next_day.rs:78-84 — 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 `crates/embucket-functions/src/datetime/add_months.rs:83` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2 locations) ui/src/modules/columns/columns-page-table.tsx:6— ui/src/modules/columns/columns-page-table.tsx:6 · ui/src/modules/volumes/volumes-page-table.tsx:7 — 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 (13 lines × 2 locations) ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets-skeleton.tsx:14— ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets-skeleton.tsx:14 · ui/src/modules/editor/editor-right-panel/editor-right-panel-queries-skeleton.tsx:14 — 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 (13 lines × 2 locations) ui/src/modules/queries/queries-history-page-toolbar.tsx:22— ui/src/modules/queries/queries-history-page-toolbar.tsx:22 · ui/src/modules/shared/trees/trees-toolbar.tsx:19 — 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 (13 lines × 2 locations) ui/src/modules/schemas/schemas-page.tsx:42— ui/src/modules/schemas/schemas-page.tsx:42 · ui/src/modules/volumes/volumes-page.tsx:37 — 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.
UserQuery::execute (cyclomatic 31) REDACTED:311— UserQuery::execute has cyclomatic complexity 31 (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.
UserQuery::show_query (cyclomatic 21) REDACTED:1759— UserQuery::show_query 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.
UserQuery::drop_query (cyclomatic 20) REDACTED:678— UserQuery::drop_query has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
embucket_functions::conversion::to_varchar::apply_numeric_format (cyclomatic 23) crates/embucket-functions/src/conversion/to_varchar.rs:304— embucket_functions::conversion::to_varchar::apply_numeric_format 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.
embucket_functions::array_to_boolean (cyclomatic 21) crates/embucket-functions/src/lib.rs:175— embucket_functions::array_to_boolean has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
embucket_functions::conversion::to_timestamp::parse_decimal (cyclomatic 17) crates/embucket-functions/src/conversion/to_timestamp.rs:586— embucket_functions::conversion::to_timestamp::parse_decimal has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: embucket_functions::conversion::to_timestamp::parse_timezone (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
Repeated repair: crates/core-executor/src/datafusion/physical_plan/merge.rs crates/core-executor/src/datafusion/physical_plan/merge.rs:348— crates/core-executor/src/datafusion/physical_plan/merge.rs changed 9 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 14 (its worst body is MergeCOWFilterStream::poll_next at line 348), AT OR 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 merge single partition execution (#1697)”; “Fix merge predicate handling and refactor COW filter stream (#1674)”; “engine: Arrow null fix (#1663)”; “Fix merge from empty source table (#1600)”. 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/core-executor/src/datafusion/physical_plan/merge.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:90— REDACTED changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is api_ui::tables::handlers::get_table_statistics at line 90), AT OR 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: “engine: Explain fix (#1891)”; “api: UI OpenAPI snake_case schema fix (#1799)”; “Fix sqlstate for some sqls (#1738)”. 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06: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.
Repeated repair: crates/embucket-functions/src/regexp/regexp_replace.rs crates/embucket-functions/src/regexp/regexp_replace.rs:102— crates/embucket-functions/src/regexp/regexp_replace.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is RegexpReplaceFunc::take_args_values at line 102), AT OR 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: “engine: Explain fix (#1891)”; “engine: `regexp_replace` occurrence bug fix (#1844)”; “Fix utf8view to StringArray converter (#1756)”. 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 2025-08-24..2025-11-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-08-24 12:39:35 -06:00' --until='2025-11-22 12:39:35 -06:00' --full-history --no-merges -- crates/embucket-functions/src/regexp/regexp_replace.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FixmeComment test/slt_runner/result.py:685— # FIXME: create a CLI argument for 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.
FixmeComment test/slt_runner/result.py:1066— # FIXME: these connections are expected to have the same settings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment crates/core-executor/src/tests/query.rs:268— // FIXME: ILIKE is not supported yet — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:490— crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:490-500 | crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:507-520 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/embucket-functions/src/encryption/decrypt_raw.rs:322— crates/embucket-functions/src/encryption/decrypt_raw.rs:322-332 | crates/embucket-functions/src/encryption/encrypt_raw.rs:302-313 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/embucket-functions/src/string-binary/jarowinkler_similarity.rs:25— crates/embucket-functions/src/string-binary/jarowinkler_similarity.rs:25-35 | crates/embucket-functions/src/string-binary/split.rs:38-48 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:547— crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:547-556 | crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:581-590 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/embucket-functions/src/conversion/to_varchar.rs:417— crates/embucket-functions/src/conversion/to_varchar.rs:417-426 | crates/embucket-functions/src/conversion/to_varchar.rs:481-492 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/embucket-functions/src/aggregate/array_unique_agg.rs:71— crates/embucket-functions/src/aggregate/array_unique_agg.rs:71-80 | crates/embucket-functions/src/aggregate/object_agg.rs:60-75 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) crates/core-executor/src/models.rs:163— crates/core-executor/src/models.rs:163-171 | crates/embucket-functions/src/table/result_scan.rs:176-187 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:98— crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:98-106 | crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:262-273 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/embucket-functions/src/conversion/to_time.rs:68— crates/embucket-functions/src/conversion/to_time.rs:68-84 | crates/embucket-functions/src/regexp/regexp_like.rs:58-66 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) crates/embucket-functions/src/aggregate/any_value.rs:57— crates/embucket-functions/src/aggregate/any_value.rs:57-63 | crates/embucket-functions/src/aggregate/percentile_cont.rs:37-43 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/embucket-functions/src/crypto/mod.rs:7— crates/embucket-functions/src/crypto/mod.rs:7-13 | crates/embucket-functions/src/encryption/mod.rs:9-16 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/df-catalog/src/schema.rs:18— crates/df-catalog/src/schema.rs:18-24 | crates/df-catalog/src/table.rs:42-48 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (17 lines × 2) crates/embucket-functions/src/aggregate/percentile_cont.rs:208— crates/embucket-functions/src/aggregate/percentile_cont.rs:208-224 | crates/embucket-functions/src/aggregate/percentile_cont.rs:279-295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) crates/embucket-functions/src/semi-structured/array/array_max.rs:62— crates/embucket-functions/src/semi-structured/array/array_max.rs:62-78 | crates/embucket-functions/src/semi-structured/array/array_min.rs:62-78 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_max.rs` and `crates/embucket-functions/src/semi-structured/array/array_min.rs` as WHOLE FILES: this scan already matched 8 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. 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 `crates/embucket-functions/src/semi-structured/array/array_max.rs:62` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) crates/embucket-functions/src/string-binary/substr.rs:127— crates/embucket-functions/src/string-binary/substr.rs:127-143 | crates/embucket-functions/src/string-binary/substr.rs:210-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) crates/embucket-functions/src/semi-structured/array/array_except.rs:30— crates/embucket-functions/src/semi-structured/array/array_except.rs:30-41 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:33-44 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_except.rs` and `crates/embucket-functions/src/semi-structured/array/array_intersection.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `crates/embucket-functions/src/semi-structured/array/array_except.rs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/embucket-functions/src/semi-structured/object/is_object.rs:79— crates/embucket-functions/src/semi-structured/object/is_object.rs:79-90 | crates/embucket-functions/src/semi-structured/parse_json.rs:91-102 — 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 `crates/embucket-functions/src/semi-structured/object/is_object.rs:79` 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 (12 lines × 2) crates/embucket-functions/src/string-binary/insert.rs:132— crates/embucket-functions/src/string-binary/insert.rs:132-143 | crates/embucket-functions/src/string-binary/insert.rs:161-172 — 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 `crates/embucket-functions/src/string-binary/insert.rs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) crates/embucket-functions/src/json.rs:154— crates/embucket-functions/src/json.rs:154-164 | crates/embucket-functions/src/json.rs:169-179 | crates/embucket-functions/src/json.rs:749-759 — 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 `crates/embucket-functions/src/json.rs: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 (11 lines × 3) crates/embucket-functions/src/semi-structured/array/array_compact.rs:77— crates/embucket-functions/src/semi-structured/array/array_compact.rs:77-87 | crates/embucket-functions/src/semi-structured/array/array_reverse.rs:70-80 | crates/embucket-functions/src/semi-structured/array/array_size.rs:63-73 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_compact.rs` and `crates/embucket-functions/src/semi-structured/array/array_reverse.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `crates/embucket-functions/src/semi-structured/array/array_compact.rs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) crates/embucket-functions/src/semi-structured/array/array_distinct.rs:24— crates/embucket-functions/src/semi-structured/array/array_distinct.rs:24-34 | crates/embucket-functions/src/semi-structured/array/array_max.rs:24-34 | crates/embucket-functions/src/semi-structured/array/array_min.rs:24-34 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` and `crates/embucket-functions/src/semi-structured/array/array_max.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 4) crates/embucket-functions/src/conversion/to_timestamp.rs:614— crates/embucket-functions/src/conversion/to_timestamp.rs:614-621 | crates/embucket-functions/src/conversion/to_timestamp.rs:625-632 | crates/embucket-functions/src/conversion/to_timestamp.rs:636-643 | crates/embucket-functions/src/conversion/to_timestamp.rs:647-654 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/conversion/to_timestamp.rs:614` 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 (8 lines × 4) crates/embucket-functions/src/regexp/regexp_instr.rs:73— crates/embucket-functions/src/regexp/regexp_instr.rs:73-80 | crates/embucket-functions/src/regexp/regexp_replace.rs:63-70 | crates/embucket-functions/src/regexp/regexp_substr.rs:69-76 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:71-78 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:73` 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 × 4) crates/embucket-functions/src/semi-structured/array/array_except.rs:90— crates/embucket-functions/src/semi-structured/array/array_except.rs:90-97 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:93-100 | crates/embucket-functions/src/semi-structured/array/arrays_overlap.rs:86-93 | crates/embucket-functions/src/semi-structured/array/arrays_to_object.rs:79-86 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_except.rs` and `crates/embucket-functions/src/semi-structured/array/array_intersection.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `crates/embucket-functions/src/semi-structured/array/array_except.rs:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) crates/embucket-functions/src/datetime/last_day.rs:177— crates/embucket-functions/src/datetime/last_day.rs:177-182 | crates/embucket-functions/src/datetime/monthname.rs:74-79 | crates/embucket-functions/src/datetime/previous_day.rs:83-88 — before extracting anything, compare `crates/embucket-functions/src/datetime/last_day.rs` and `crates/embucket-functions/src/datetime/previous_day.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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, `crates/embucket-functions/src/datetime/previous_day.rs:79` calls `Scalar`, `Utf8`, `Some` and `crates/embucket-functions/src/datetime/monthname.rs:73` 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 (6 lines × 3) crates/embucket-functions/src/geospatial/measurement/contains.rs:103— crates/embucket-functions/src/geospatial/measurement/contains.rs:103-108 | crates/embucket-functions/src/geospatial/measurement/distance.rs:106-111 | crates/embucket-functions/src/geospatial/measurement/within.rs:103-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/geospatial/measurement/contains.rs:103` 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 × 3) crates/embucket-functions/src/json.rs:32— crates/embucket-functions/src/json.rs:32-37 | crates/embucket-functions/src/json.rs:55-60 | crates/embucket-functions/src/json.rs:749-754 — 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 `crates/embucket-functions/src/json.rs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) crates/embucket-functions/src/regexp/regexp_instr.rs:312— crates/embucket-functions/src/regexp/regexp_instr.rs:312-316 | crates/embucket-functions/src/regexp/regexp_substr.rs:277-281 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:280-284 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_substr.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 183 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 `crates/embucket-functions/src/regexp/regexp_instr.rs: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.
Duplicated block (5 lines × 3) crates/embucket-functions/src/datetime/date_diff.rs:66— crates/embucket-functions/src/datetime/date_diff.rs:66-70 | crates/embucket-functions/src/datetime/date_part_extract.rs:86-90 | crates/embucket-functions/src/datetime/last_day.rs:67-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) REDACTED:338— REDACTED:338-342 | crates/api-ui/src/volumes/handlers.rs:295-299 | crates/api-ui/src/worksheets/handlers.rs:98-102 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/api-ui/src/worksheets/handlers.rs:96` calls `downcast_int64_column`, `context` and `crates/api-ui/src/volumes/handlers.rs:293` 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.
Low cohesion: SlatedbVfs (LCOM4 4) crates/core-sqlite/src/vfs/mod.rs:55— SlatedbVfs'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: CachingCatalog (LCOM4 4) crates/df-catalog/src/catalog.rs:9— CachingCatalog'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: AllocLogLayer (LCOM4 4) crates/embucketd/src/layers.rs:85— AllocLogLayer'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 (14 lines × 2 locations) ui/src/components/ui/select.tsx:126— ui/src/components/ui/select.tsx:126 · ui/src/components/ui/select.tsx:141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) ui/src/modules/editor/editor-page.tsx:21— ui/src/modules/editor/editor-page.tsx:21 · ui/src/modules/editor/editor-page.tsx:43 — 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 (14 lines × 2 locations) ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:26— ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:26 · ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:49 — 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.
Dead file (~74 LoC) ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~74 LoC) ui/src/modules/query/query-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/queries/$queryId.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~74 LoC) ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/schemas/schemas-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
ToTimestampFunc::invoke_with_args (cyclomatic 33) crates/embucket-functions/src/conversion/to_timestamp.rs:235— ToTimestampFunc::invoke_with_args has cyclomatic complexity 33 (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.
ToTimestampFunc::return_field_from_args (cyclomatic 17) crates/embucket-functions/src/conversion/to_timestamp.rs:136— ToTimestampFunc::return_field_from_args 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. This is NOT this file's highest cyclomatic complexity: embucket_functions::conversion::to_timestamp::parse_timezone (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
DecryptRawFunc::invoke_with_args (cyclomatic 27) crates/embucket-functions/src/encryption/decrypt_raw.rs:178— DecryptRawFunc::invoke_with_args has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DecryptRawFunc::coerce_types (cyclomatic 16) crates/embucket-functions/src/encryption/decrypt_raw.rs:76— DecryptRawFunc::coerce_types 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.
ToTimestampFunc::invoke_with_args (cognitive 59) crates/embucket-functions/src/conversion/to_timestamp.rs:235— ToTimestampFunc::invoke_with_args has cognitive complexity 59 (threshold 15). Drivers by points: if/else 22 (34 pts), loops 4 (12 pts), match/switch 7 (12 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToTimestampFunc::return_field_from_args (cognitive 23) crates/embucket-functions/src/conversion/to_timestamp.rs:136— ToTimestampFunc::return_field_from_args has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 1 (4 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.
ArrayUniqueAggAccumulator::evaluate (cognitive 52) crates/embucket-functions/src/aggregate/array_union_agg.rs:163— ArrayUniqueAggAccumulator::evaluate has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (49 pts), match/switch 2 (3 pts) (nesting depth added 28). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ArrayUniqueAggAccumulator::update_batch (cognitive 18) crates/embucket-functions/src/aggregate/array_union_agg.rs:104— ArrayUniqueAggAccumulator::update_batch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 3 (7 pts), match/switch 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DecryptRawFunc::invoke_with_args (cognitive 42) crates/embucket-functions/src/encryption/decrypt_raw.rs:178— DecryptRawFunc::invoke_with_args has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (27 pts), match/switch 7 (11 pts), boolean chains 3, 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.
DecryptRawFunc::coerce_types (cognitive 21) crates/embucket-functions/src/encryption/decrypt_raw.rs:76— DecryptRawFunc::coerce_types has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EncryptRawFunc::invoke_with_args (cognitive 31) crates/embucket-functions/src/encryption/encrypt_raw.rs:164— EncryptRawFunc::invoke_with_args has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 6 (9 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EncryptRawFunc::coerce_types (cognitive 17) crates/embucket-functions/src/encryption/encrypt_raw.rs:80— EncryptRawFunc::coerce_types has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, match/switch 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.
InformationSchemaConfig::make_columns (cognitive 27) crates/df-catalog/src/information_schema/config.rs:183— InformationSchemaConfig::make_columns has cognitive complexity 27 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 4 (12 pts) (nesting depth added 18). 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.
InformationSchemaConfig::make_views (cognitive 20) crates/df-catalog/src/information_schema/config.rs:142— InformationSchemaConfig::make_views has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (7 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.
ListAggAccumulator::merge_batch (cognitive 25) crates/embucket-functions/src/aggregate/listagg.rs:167— ListAggAccumulator::merge_batch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListAggAccumulator::update_batch (cognitive 20) crates/embucket-functions/src/aggregate/listagg.rs:123— ListAggAccumulator::update_batch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) crates/embucket-functions/src/datetime/add_months.rs:79— crates/embucket-functions/src/datetime/add_months.rs:79-120 | crates/embucket-functions/src/datetime/next_day.rs:74-105 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) crates/core-executor/src/dedicated_executor.rs:274— crates/core-executor/src/dedicated_executor.rs:274-305 | crates/core-executor/src/dedicated_executor.rs:740-772 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) crates/embucket-functions/src/geospatial/measurement/contains.rs:97— crates/embucket-functions/src/geospatial/measurement/contains.rs:97-120 | crates/embucket-functions/src/geospatial/measurement/within.rs:97-122 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) crates/embucket-functions/src/semi-structured/array/array_except.rs:29— crates/embucket-functions/src/semi-structured/array/array_except.rs:29-52 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:32-55 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) crates/core-history/src/sqlite_history_store.rs:203— crates/core-history/src/sqlite_history_store.rs:203-240 | crates/core-history/src/sqlite_history_store.rs:319-354 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) crates/df-catalog/src/information_schema/config.rs:145— crates/df-catalog/src/information_schema/config.rs:145-180 | crates/df-catalog/src/information_schema/config.rs:186-227 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×2
Edited copy of a member (28 corresponding lines) crates/embucket-functions/src/aggregate/boolxor_agg.rs:72— crates/embucket-functions/src/aggregate/boolxor_agg.rs:72-99 | crates/embucket-functions/src/aggregate/boolxor_agg.rs:113-143 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:36— crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:36-63 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:36-65 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) crates/embucket-functions/src/json.rs:87— crates/embucket-functions/src/json.rs:87-107 | crates/embucket-functions/src/json.rs:111-130 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) crates/embucket-functions/src/datetime/date_from_parts.rs:94— crates/embucket-functions/src/datetime/date_from_parts.rs:94-113 | crates/embucket-functions/src/datetime/time_from_parts.rs:101-122 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) crates/core-history/src/sqlite_history_store.rs:168— crates/core-history/src/sqlite_history_store.rs:168-194 | crates/core-history/src/sqlite_history_store.rs:363-420 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) crates/api-iceberg-rest/src/handlers.rs:45— crates/api-iceberg-rest/src/handlers.rs:45-72 | REDACTED:191-217 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) crates/embucket-functions/src/geospatial/constructors/line_string.rs:139— crates/embucket-functions/src/geospatial/constructors/line_string.rs:139-162 | crates/embucket-functions/src/geospatial/constructors/line_string.rs:164-184 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/core-executor/src/running_queries.rs:147— crates/core-executor/src/running_queries.rs:147-167 | crates/core-executor/src/running_queries.rs:176-198 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) crates/embucket-functions/src/string-binary/hex_encode.rs:158— crates/embucket-functions/src/string-binary/hex_encode.rs:158-180 | crates/embucket-functions/src/string-binary/hex_encode.rs:186-208 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) crates/error-stack-trace/src/stack.rs:279— crates/error-stack-trace/src/stack.rs:279-301 | crates/error-stack-trace/src/stack.rs:303-325 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:92— crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:92-112 | crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:121-136 | crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:232-248 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) REDACTED:195— REDACTED:195-210 | REDACTED:213-228 | REDACTED:231-246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×2
Edited copies of one member (4 members, 9+ corresponding lines) crates/embucket-functions/src/datetime/date_add.rs:47— crates/embucket-functions/src/datetime/date_add.rs:47-57 | crates/embucket-functions/src/datetime/date_add.rs:63-76 | crates/embucket-functions/src/datetime/date_add.rs:78-91 | crates/embucket-functions/src/datetime/date_add.rs:97-105 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) crates/df-catalog/src/catalogs/slatedb/databases.rs:33— crates/df-catalog/src/catalogs/slatedb/databases.rs:33-41 | crates/df-catalog/src/catalogs/slatedb/schemas.rs:33-41 | crates/df-catalog/src/catalogs/slatedb/volumes.rs:33-41 | crates/df-catalog/src/catalogs/slatedb/worksheets.rs:36-45 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) crates/api-ui/src/error.rs:143— crates/api-ui/src/error.rs:143-154 | crates/api-ui/src/error.rs:156-173 | crates/api-ui/src/error.rs:175-186 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) crates/embucket-functions/src/datetime/add_months.rs:40— crates/embucket-functions/src/datetime/add_months.rs:40-54 | crates/embucket-functions/src/datetime/date_part_extract.rs:70-83 | crates/embucket-functions/src/datetime/dayname.rs:38-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) crates/core-executor/src/session.rs:194— crates/core-executor/src/session.rs:194-201 | crates/core-executor/src/session.rs:204-215 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/api-ui/src/databases/models.rs:34— crates/api-ui/src/databases/models.rs:34-41 | crates/api-ui/src/volumes/models.rs:127-134 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×2
Edited copies of one member (3 members, 15+ corresponding lines) crates/embucket-functions/src/conversion/to_date.rs:273— crates/embucket-functions/src/conversion/to_date.rs:273-287 | crates/embucket-functions/src/regexp/regexp_instr.rs:264-280 | crates/embucket-functions/src/regexp/regexp_like.rs:82-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) crates/embucket-seed/src/seed_models/database.rs:26— crates/embucket-seed/src/seed_models/database.rs:26-40 | crates/embucket-seed/src/seed_models/schema.rs:26-40 | crates/embucket-seed/src/seed_models/table.rs:27-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (22 lines × 2) crates/embucket-functions/src/datetime/date_part_extract.rs:303— crates/embucket-functions/src/datetime/date_part_extract.rs:303-324 | crates/embucket-functions/src/datetime/date_part_extract.rs:392-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/datetime/date_part_extract.rs:303` 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 (22 lines × 2) crates/embucket-functions/src/semi-structured/array/array_except.rs:118— crates/embucket-functions/src/semi-structured/array/array_except.rs:118-139 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:115-136 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_except.rs` and `crates/embucket-functions/src/semi-structured/array/array_intersection.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `crates/embucket-functions/src/semi-structured/array/array_except.rs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) crates/embucket-functions/src/conditional/booland.rs:56— crates/embucket-functions/src/conditional/booland.rs:56-71 | crates/embucket-functions/src/conditional/boolor.rs:57-72 | crates/embucket-functions/src/conditional/boolxor.rs:57-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/conditional/booland.rs:56` 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 (16 lines × 3) crates/embucket-functions/src/regexp/regexp_replace.rs:211— crates/embucket-functions/src/regexp/regexp_replace.rs:211-226 | crates/embucket-functions/src/regexp/regexp_substr.rs:229-244 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:232-247 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_replace.rs` and `crates/embucket-functions/src/regexp/regexp_substr.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 176 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13–15 lines × 2) crates/core-metastore/src/metastore.rs:821— crates/core-metastore/src/metastore.rs:821-833 | crates/core-metastore/src/metastore.rs:839-853 — 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 `crates/core-metastore/src/metastore.rs:821` 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 (13–15 lines × 2) crates/embucket-functions/src/aggregate/boolxor_agg.rs:87— crates/embucket-functions/src/aggregate/boolxor_agg.rs:87-99 | crates/embucket-functions/src/aggregate/boolxor_agg.rs:129-143 — 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 `crates/embucket-functions/src/aggregate/boolxor_agg.rs:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) crates/embucket-functions/src/json.rs:591— crates/embucket-functions/src/json.rs:591-602 | crates/embucket-functions/src/json.rs:607-618 | crates/embucket-functions/src/json.rs:623-634 | crates/embucket-functions/src/json.rs:639-650 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/json.rs:591` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) crates/embucket-functions/src/semi-structured/array/array_size.rs:68— crates/embucket-functions/src/semi-structured/array/array_size.rs:68-79 | crates/embucket-functions/src/semi-structured/array/array_sort.rs:157-168 | crates/embucket-functions/src/semi-structured/object/object_delete.rs:104-115 | crates/embucket-functions/src/semi-structured/object/object_insert.rs:157-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/semi-structured/array/array_size.rs:68` 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 × 7) crates/embucket-functions/src/semi-structured/array/array_compact.rs:82— crates/embucket-functions/src/semi-structured/array/array_compact.rs:82-88 | crates/embucket-functions/src/semi-structured/array/array_distinct.rs:93-99 | crates/embucket-functions/src/semi-structured/array/array_max.rs:129-135 | crates/embucket-functions/src/semi-structured/array/array_min.rs:129-135 | crates/embucket-functions/src/semi-structured/array/array_reverse.rs:75-81 | crates/embucket-functions/src/semi-structured/array/array_size.rs:68-74 | crates/embucket-functions/src/semi-structured/object/object_delete.rs:104-110 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_compact.rs` and `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `crates/embucket-functions/src/semi-structured/array/array_compact.rs:82` 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 × 7) crates/embucket-functions/src/semi-structured/array/array_remove.rs:108— crates/embucket-functions/src/semi-structured/array/array_remove.rs:108-114 | crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:116-122 | crates/embucket-functions/src/semi-structured/array/array_size.rs:73-79 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:129-135 | crates/embucket-functions/src/semi-structured/array/array_sort.rs:162-168 | crates/embucket-functions/src/semi-structured/object/object_delete.rs:109-115 | crates/embucket-functions/src/semi-structured/object/object_insert.rs:162-168 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_remove_at.rs` and `crates/embucket-functions/src/semi-structured/array/array_slice.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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 `crates/embucket-functions/src/semi-structured/array/array_remove.rs: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 (7 lines × 4) crates/embucket-functions/src/semi-structured/array/array_append.rs:108— crates/embucket-functions/src/semi-structured/array/array_append.rs:108-114 | crates/embucket-functions/src/semi-structured/array/array_prepend.rs:97-103 | crates/embucket-functions/src/semi-structured/array/array_remove.rs:119-125 | crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:128-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/semi-structured/array/array_append.rs:108` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 4) crates/embucket-functions/src/regexp/regexp_instr.rs:228— crates/embucket-functions/src/regexp/regexp_instr.rs:228-234 | crates/embucket-functions/src/regexp/regexp_replace.rs:143-149 | crates/embucket-functions/src/regexp/regexp_substr.rs:192-198 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:195-201 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:228` 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.
Unfinished stub — body is todo!() / unimplemented!() crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:572— `register_table` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is todo!() / unimplemented!() crates/embucket-functions/src/scalar_template.rs:91— `invoke_with_args` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — body is todo!() / unimplemented!() crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:572— `register_table` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface.
Unfinished stub — body is todo!() / unimplemented!() crates/embucket-functions/src/scalar_template.rs:91— `invoke_with_args` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface.
Duplicated block (33 lines × 2 locations) ui/src/modules/databases/databases-page-table.tsx:13— ui/src/modules/databases/databases-page-table.tsx:13 · ui/src/modules/schemas/schemas-page-table.tsx:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (33 lines × 2 locations) ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28— ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28 · ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:26 — 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 (18 lines × 2 locations) ui/src/modules/home/home-action-buttons.tsx:48— ui/src/modules/home/home-action-buttons.tsx:48 · ui/src/modules/tables/tables-page.tsx:56 — 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 × 2 locations) ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:38— ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:38 · ui/src/modules/shared/create-schema-dialog/create-schema-dialog-form.tsx:27 — 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.
Dead file (~114 LoC) ui/src/modules/columns/columns-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.$tableName.columns.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~114 LoC) ui/src/modules/data-preview/use-infinite-preview-data.ts— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/modules/data-preview/data-preview-page.tsx, ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~85 LoC) ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~85 LoC) ui/src/modules/query/query-details.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/query/query-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~77 LoC) ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~77 LoC) ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheet.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheets.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~71 LoC) ui/src/modules/editor/editor-right-panel/editor-right-panel-query/editor-right-panel-query.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-right-panel/editor-right-panel-queries.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~71 LoC) ui/src/modules/volumes/volumes-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/volumes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC2 · Forms & labels· <Select> field component without a label · ×1
<Select> field component without a label ui/src/modules/shared/table-data-upload-dialog/table-data-upload-database-select.tsx:50— This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
core_executor::snowflake_error::datafusion_error (cyclomatic 43) crates/core-executor/src/snowflake_error.rs:375— core_executor::snowflake_error::datafusion_error has cyclomatic complexity 43 (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.
ToTimeFunc::invoke_with_args (cyclomatic 30) crates/embucket-functions/src/conversion/to_time.rs:113— ToTimeFunc::invoke_with_args has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FunctionsRewriter::post_visit_expr (cyclomatic 25) crates/embucket-functions/src/visitors/functions_rewriter.rs:15— FunctionsRewriter::post_visit_expr has cyclomatic complexity 25 (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.
generate_unimplemented_snowflake_functions.main (cyclomatic 24) crates/embucket-functions/src/visitors/unimplemented/helper/generate_unimplemented_snowflake_functions.py:220— generate_unimplemented_snowflake_functions.main 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.
CustomTypePlanner::plan_type (cyclomatic 23) crates/core-executor/src/datafusion/type_planner.rs:24— CustomTypePlanner::plan_type 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.
EncryptRawFunc::invoke_with_args (cyclomatic 22) crates/embucket-functions/src/encryption/encrypt_raw.rs:164— EncryptRawFunc::invoke_with_args has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToDateFunc::to_date (cyclomatic 21) crates/embucket-functions/src/conversion/to_date.rs:141— ToDateFunc::to_date 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.
DatePartExtractFunc::invoke_with_args (cyclomatic 19) crates/embucket-functions/src/datetime/date_part_extract.rs:140— DatePartExtractFunc::invoke_with_args has cyclomatic complexity 19 (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.
TableRequirementExt::assert (cyclomatic 18) crates/core-metastore/src/models/table.rs:166— TableRequirementExt::assert 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.
TypeofFunc::invoke_with_args (cyclomatic 18) crates/embucket-functions/src/semi-structured/typeof_func.rs:58— TypeofFunc::invoke_with_args has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ExprRewriter::f_up (cyclomatic 17) crates/core-executor/src/datafusion/rewriters/session_context.rs:103— ExprRewriter::f_up has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
GetFunc::invoke_with_args (cyclomatic 17) crates/embucket-functions/src/semi-structured/get.rs:74— GetFunc::invoke_with_args 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.
IsTypeofFunc::invoke_with_args (cyclomatic 17) crates/embucket-functions/src/semi-structured/is_typeof.rs:87— IsTypeofFunc::invoke_with_args has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ArrayUniqueAggAccumulator::evaluate (cyclomatic 16) crates/embucket-functions/src/aggregate/array_union_agg.rs:163— ArrayUniqueAggAccumulator::evaluate 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.
BoolXorFunc::invoke_with_args (cyclomatic 16) crates/embucket-functions/src/conditional/boolxor.rs:56— BoolXorFunc::invoke_with_args has cyclomatic complexity 16 (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.
ToBinaryFunc::invoke_with_args (cyclomatic 16) crates/embucket-functions/src/conversion/to_binary.rs:88— ToBinaryFunc::invoke_with_args 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.
Div0Func::invoke_with_args (cyclomatic 16) crates/embucket-functions/src/numeric/div0.rs:91— Div0Func::invoke_with_args 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.
ArraysToObjectUDF::invoke_with_args (cyclomatic 16) crates/embucket-functions/src/semi-structured/array/arrays_to_object.rs:70— ArraysToObjectUDF::invoke_with_args 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.
HackComment crates/benchmarks/src/util/options.rs:13— // hack to avoid `default_value is meaningless for bool` errors — 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.
ToTimeFunc::invoke_with_args (cognitive 87) crates/embucket-functions/src/conversion/to_time.rs:113— ToTimeFunc::invoke_with_args has cognitive complexity 87 (threshold 15). Drivers by points: if/else 22 (53 pts), match/switch 6 (24 pts), loops 5 (10 pts) (nesting depth added 54). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToDateFunc::to_date (cognitive 48) crates/embucket-functions/src/conversion/to_date.rs:141— ToDateFunc::to_date has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (37 pts), loops 2 (6 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 24). 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.
generate_unimplemented_snowflake_functions.main (cognitive 41) crates/embucket-functions/src/visitors/unimplemented/helper/generate_unimplemented_snowflake_functions.py:220— generate_unimplemented_snowflake_functions.main has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 7 (16 pts), loops 3 (4 pts), boolean chains 2, error handling 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.
ArrayMaxUDF::find_max (cognitive 39) crates/embucket-functions/src/semi-structured/array/array_max.rs:36— ArrayMaxUDF::find_max has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 3 (11 pts), boolean chains 2, loops 1 (2 pts) (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.
ArrayMinUDF::find_min (cognitive 39) crates/embucket-functions/src/semi-structured/array/array_min.rs:36— ArrayMinUDF::find_min has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 3 (11 pts), boolean chains 2, loops 1 (2 pts) (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.
GetFunc::invoke_with_args (cognitive 39) crates/embucket-functions/src/semi-structured/get.rs:74— GetFunc::invoke_with_args has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (31 pts), loops 2 (5 pts), match/switch 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Div0Func::invoke_with_args (cognitive 38) crates/embucket-functions/src/numeric/div0.rs:91— Div0Func::invoke_with_args has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (31 pts), match/switch 2 (4 pts), boolean chains 3 (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.
FunctionsRewriter::post_visit_expr (cognitive 35) crates/embucket-functions/src/visitors/functions_rewriter.rs:15— FunctionsRewriter::post_visit_expr has cognitive complexity 35 (threshold 15). Drivers by points: match/switch 6 (16 pts), if/else 6 (15 pts), boolean chains 4 (nesting depth added 19). 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.
MergeCOWFilterStream::poll_next (cognitive 34) crates/core-executor/src/datafusion/physical_plan/merge.rs:348— MergeCOWFilterStream::poll_next has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 5 (14 pts), match/switch 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArraysZipUDF::invoke_with_args (cognitive 33) crates/embucket-functions/src/semi-structured/array/arrays_zip.rs:89— ArraysZipUDF::invoke_with_args has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 3 (8 pts), loops 3 (7 pts) (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ArraysToObjectUDF::invoke_with_args (cognitive 32) crates/embucket-functions/src/semi-structured/array/arrays_to_object.rs:70— ArraysToObjectUDF::invoke_with_args has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 3 (8 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ObjectConstructUDF::invoke_with_args (cognitive 32) crates/embucket-functions/src/semi-structured/object/object_construct.rs:68— ObjectConstructUDF::invoke_with_args has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 1 (4 pts), 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.
ObjectPickUDF::invoke_with_args (cognitive 31) crates/embucket-functions/src/semi-structured/object/object_pick.rs:75— ObjectPickUDF::invoke_with_args has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3 (8 pts), match/switch 2 (3 pts) (nesting depth added 17). 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.
TopLimitVisitor::process_set_expr (cognitive 29) crates/embucket-functions/src/visitors/top_limit.rs:26— TopLimitVisitor::process_set_expr has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 2 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EmbucketCatalogList::refresh (cognitive 28) crates/df-catalog/src/catalog_list.rs:388— EmbucketCatalogList::refresh has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 4 (12 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayRemoveUDF::invoke_with_args (cognitive 28) crates/embucket-functions/src/semi-structured/array/array_remove.rs:79— ArrayRemoveUDF::invoke_with_args has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
generate_unimplemented_snowflake_functions.expand_function_patterns (cognitive 28) crates/embucket-functions/src/visitors/unimplemented/helper/generate_unimplemented_snowflake_functions.py:103— generate_unimplemented_snowflake_functions.expand_function_patterns has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ObjectInsertUDF::invoke_with_args (cognitive 27) crates/embucket-functions/src/semi-structured/object/object_insert.rs:87— ObjectInsertUDF::invoke_with_args has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 6 (9 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AllocLogLayer::on_event (cognitive 26) crates/embucketd/src/layers.rs:172— AllocLogLayer::on_event has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (22 pts), match/switch 1 (3 pts), boolean chains 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.
ParseIpFunc::invoke_with_args (cognitive 24) crates/embucket-functions/src/string-binary/parse_ip.rs:98— ParseIpFunc::invoke_with_args has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 3 (7 pts), boolean chains 1, 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.
ToBinaryFunc::invoke_with_args (cognitive 23) crates/embucket-functions/src/conversion/to_binary.rs:88— ToBinaryFunc::invoke_with_args has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StrtokToArrayFunc::invoke_with_args (cognitive 23) crates/embucket-functions/src/semi-structured/array/strtok_to_array.rs:70— StrtokToArrayFunc::invoke_with_args has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Insert::invoke_with_args (cognitive 23) crates/embucket-functions/src/string-binary/insert.rs:100— Insert::invoke_with_args has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 7 (11 pts), if/else 2 (6 pts), loops 2 (4 pts), boolean chains 2 (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.
InlineAliasesInSelect::pre_visit_query (cognitive 23) crates/embucket-functions/src/visitors/inline_aliases_in_query.rs:49— InlineAliasesInSelect::pre_visit_query has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (6 pts), match/switch 1 (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.
ObjectDeleteUDF::invoke_with_args (cognitive 22) crates/embucket-functions/src/semi-structured/object/object_delete.rs:74— ObjectDeleteUDF::invoke_with_args has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (7 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableRequirementExt::assert (cognitive 21) crates/core-metastore/src/models/table.rs:166— TableRequirementExt::assert has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SlatedbVfs::file_control (cognitive 21) crates/core-sqlite/src/vfs/mod.rs:459— SlatedbVfs::file_control has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (7 pts), 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.
TypeofFunc::invoke_with_args (cognitive 21) crates/embucket-functions/src/semi-structured/typeof_func.rs:58— TypeofFunc::invoke_with_args has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 3 (5 pts), loops 1 (2 pts) (nesting depth added 12). 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.
SubstrFunc::simplify (cognitive 21) crates/embucket-functions/src/string-binary/substr.rs:163— SubstrFunc::simplify has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ToArrayFunc::invoke_with_args (cognitive 20) crates/embucket-functions/src/conversion/to_array.rs:80— ToArrayFunc::invoke_with_args has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (6 pts), match/switch 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArraySliceUDF::invoke_with_args (cognitive 20) crates/embucket-functions/src/semi-structured/array/array_slice.rs:91— ArraySliceUDF::invoke_with_args has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 4 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ParseJsonFunc::invoke_with_args (cognitive 20) crates/embucket-functions/src/semi-structured/parse_json.rs:58— ParseJsonFunc::invoke_with_args has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BoolXorFunc::invoke_with_args (cognitive 19) crates/embucket-functions/src/conditional/boolxor.rs:56— BoolXorFunc::invoke_with_args has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (8 pts), match/switch 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableFuncInlineCte::extract_projected_columns (cognitive 19) crates/embucket-functions/src/visitors/table_functions_cte_relation.rs:234— TableFuncInlineCte::extract_projected_columns has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomTypePlanner::plan_type (cognitive 18) crates/core-executor/src/datafusion/type_planner.rs:24— CustomTypePlanner::plan_type has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 1 (4 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 11). 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.
SlateDBMetastore::create_table (cognitive 18) crates/core-metastore/src/metastore.rs:514— SlateDBMetastore::create_table has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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.
ArrayCatUDF::invoke_with_args (cognitive 18) crates/embucket-functions/src/semi-structured/array/array_cat.rs:77— ArrayCatUDF::invoke_with_args has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArraySortUDF::sort_array (cognitive 18) crates/embucket-functions/src/semi-structured/array/array_sort.rs:59— ArraySortUDF::sort_array has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorVariant::from_enum_variant (cognitive 18) crates/error-stack-trace/src/stack.rs:134— ErrorVariant::from_enum_variant has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (nesting depth added 7). 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.
ConvertTimezoneFunc::invoke_with_args (cognitive 17) crates/embucket-functions/src/datetime/convert_timezone.rs:163— ConvertTimezoneFunc::invoke_with_args has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 7 (14 pts), if/else 3 (nesting depth added 7). 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.
ArrayConstructUDF::invoke_with_args (cognitive 17) crates/embucket-functions/src/semi-structured/array/array_construct.rs:63— ArrayConstructUDF::invoke_with_args has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (4 pts), match/switch 1 (4 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.
IsTypeofFunc::invoke_with_args (cognitive 17) crates/embucket-functions/src/semi-structured/is_typeof.rs:87— IsTypeofFunc::invoke_with_args has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 3 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
VariantArrayElementUDF::invoke_with_args (cognitive 17) crates/embucket-functions/src/semi-structured/variant/variant_element.rs:105— VariantArrayElementUDF::invoke_with_args has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (8 pts), if/else 4 (7 pts), boolean chains 1, loops 1 (nesting depth added 7). 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.
ArrayObjectToBinaryVisitor::post_visit_statement (cognitive 17) crates/embucket-functions/src/semi-structured/variant/visitors/type_rewrite.rs:18— ArrayObjectToBinaryVisitor::post_visit_statement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (15 pts), 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.
Sha2Func::invoke_with_args (cognitive 17) crates/embucket-functions/src/string-binary/sha2.rs:76— Sha2Func::invoke_with_args has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 2 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
editor-center-bottom-panel-selected-cell.getDisplayValue (cognitive 17) ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx:7— editor-center-bottom-panel-selected-cell.getDisplayValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, error handling 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayGenerateRangeUDF::invoke_with_args (cognitive 16) crates/embucket-functions/src/semi-structured/array/array_generate_range.rs:62— ArrayGenerateRangeUDF::invoke_with_args has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayRemoveAtUDF::invoke_with_args (cognitive 16) crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:89— ArrayRemoveAtUDF::invoke_with_args has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
editor-panels-state-provider.EditorPanelsStateProvider (cognitive 16) ui/src/modules/editor/editor-panels-state-provider.tsx:57— editor-panels-state-provider.EditorPanelsStateProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. None of this is in the body itself: all 16 points belong to 6 function literals inside it that branch (lines 87, 97, 107, …). 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.
TooManyMethods: UserQuery REDACTED:124— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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.
TooManyFields: CliOpts crates/embucketd/src/cli.rs:15— TooManyFields — 35 stored fields beside 2 methods. The bar is 30 stored fields; this is 5 over it, 1.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
Change coupling: router.rs ↔ models.rs crates/api-ui/src/router.rs:1— `crates/api-ui/src/router.rs` and `crates/api-ui/src/tables/models.rs` 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) 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 `acace726` UI Utoipa schema fix (#441) (at that commit the files were still `crates/runtime/src/http/ui/router.rs` and `crates/runtime/src/http/ui/tables/models.rs`); `e757c113` api: Issues/344 renewed upload handler (#418) (at that commit the files were still `crates/runtime/src/http/ui/router.rs` and `crates/runtime/src/http/ui/tables/models.rs`); `1ad2d91a` UI Tables Get List (#419) (at that commit the files were still `crates/runtime/src/http/ui/router.rs` and `crates/runtime/src/http/ui/tables/models.rs`) — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (5 members, 24 shared lines) · ×1
Near-duplicate member family (5 members, 24 shared lines) crates/embucket-functions/src/regexp/regexp_instr.rs:121— crates/embucket-functions/src/regexp/regexp_instr.rs:121-248 | crates/embucket-functions/src/regexp/regexp_like.rs:101-178 | crates/embucket-functions/src/regexp/regexp_replace.rs:102-194 | crates/embucket-functions/src/regexp/regexp_substr.rs:108-212 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:111-215 — These 5 members are variants of one another: a block of 24 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 71 shared lines) · ×1
Near-duplicate member family (4 members, 71 shared lines) crates/embucket-functions/src/regexp/regexp_instr.rs:121— crates/embucket-functions/src/regexp/regexp_instr.rs:121-248 | crates/embucket-functions/src/regexp/regexp_replace.rs:102-194 | crates/embucket-functions/src/regexp/regexp_substr.rs:108-212 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:111-215 — These 4 members are variants of one another: a block of 71 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
Near-duplicate member pair (77 shared lines) crates/embucket-functions/src/encryption/decrypt_raw.rs:178— crates/embucket-functions/src/encryption/decrypt_raw.rs:178-319 | crates/embucket-functions/src/encryption/encrypt_raw.rs:164-288 — These two members are variants of one another: 77 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.
Near-duplicate member pair (67 shared lines) crates/embucket-functions/src/encryption/decrypt_raw.rs:76— crates/embucket-functions/src/encryption/decrypt_raw.rs:76-175 | crates/embucket-functions/src/encryption/encrypt_raw.rs:80-161 — These two members are variants of one another: 67 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.
Near-duplicate member pair (27 shared lines) crates/embucket-functions/src/json.rs:232— crates/embucket-functions/src/json.rs:232-285 | crates/embucket-functions/src/json.rs:408-463 — These two members are variants of one another: 27 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.
Near-duplicate member pair (25 shared lines) crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:89— crates/embucket-functions/src/semi-structured/array/array_remove_at.rs:89-156 | crates/embucket-functions/src/semi-structured/array/array_slice.rs:91-177 — These two members are variants of one another: 25 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 (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/embucket-functions/src/regexp/regexp_instr.rs:282— crates/embucket-functions/src/regexp/regexp_instr.rs:282-346 | crates/embucket-functions/src/regexp/regexp_like.rs:101-178 | crates/embucket-functions/src/regexp/regexp_replace.rs:228-297 | crates/embucket-functions/src/regexp/regexp_substr.rs:246-299 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:249-321 — These 5 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 5 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 5 times.
D4 · Code Duplication· Edited copy of a member (63 corresponding lines) · ×1
Edited copy of a member (63 corresponding lines) crates/embucket-functions/src/semi-structured/array/array_max.rs:36— crates/embucket-functions/src/semi-structured/array/array_max.rs:36-98 | crates/embucket-functions/src/semi-structured/array/array_min.rs:36-98 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) crates/embucket-functions/src/semi-structured/array/array_sort.rs:137— crates/embucket-functions/src/semi-structured/array/array_sort.rs:137-190 | crates/embucket-functions/src/semi-structured/object/object_pick.rs:75-142 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) crates/core-history/src/sqlite_history_store.rs:554— crates/core-history/src/sqlite_history_store.rs:554-611 | crates/core-history/src/sqlite_history_store.rs:620-698 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) crates/api-ui/src/databases/handlers.rs:282— crates/api-ui/src/databases/handlers.rs:282-317 | crates/api-ui/src/volumes/handlers.rs:277-310 | crates/api-ui/src/worksheets/handlers.rs:79-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) crates/embucket-functions/src/json.rs:318— crates/embucket-functions/src/json.rs:318-360 | crates/embucket-functions/src/json.rs:363-405 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) crates/embucket-functions/src/string-binary/substr.rs:285— crates/embucket-functions/src/string-binary/substr.rs:285-323 | crates/embucket-functions/src/string-binary/substr.rs:325-361 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) crates/api-ui/src/databases/error.rs:58— crates/api-ui/src/databases/error.rs:58-90 | crates/api-ui/src/schemas/error.rs:51-81 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) crates/embucket-functions/src/conditional/booland.rs:55— crates/embucket-functions/src/conditional/booland.rs:55-82 | crates/embucket-functions/src/conditional/boolor.rs:56-82 | crates/embucket-functions/src/conditional/boolxor.rs:56-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) crates/embucket-functions/src/string-binary/substr.rs:543— crates/embucket-functions/src/string-binary/substr.rs:543-580 | crates/embucket-functions/src/string-binary/substr.rs:586-645 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 33+ corresponding lines) · ×1
Edited copies of one member (6 members, 33+ corresponding lines) crates/embucket-functions/src/semi-structured/array/array_compact.rs:76— crates/embucket-functions/src/semi-structured/array/array_compact.rs:76-109 | crates/embucket-functions/src/semi-structured/array/array_distinct.rs:87-120 | crates/embucket-functions/src/semi-structured/array/array_max.rs:124-156 | crates/embucket-functions/src/semi-structured/array/array_min.rs:124-156 | crates/embucket-functions/src/semi-structured/array/array_reverse.rs:69-114 | crates/embucket-functions/src/semi-structured/array/array_size.rs:62-103 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) crates/embucket-functions/src/string-binary/hex_decode_binary.rs:126— crates/embucket-functions/src/string-binary/hex_decode_binary.rs:126-169 | crates/embucket-functions/src/string-binary/hex_decode_string.rs:127-170 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) REDACTED:2650— REDACTED:2650-2690 | REDACTED:2696-2725 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) REDACTED:2239— REDACTED:2239-2267 | REDACTED:2273-2307 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) crates/embucket-functions/src/aggregate/booland_agg.rs:71— crates/embucket-functions/src/aggregate/booland_agg.rs:71-95 | crates/embucket-functions/src/aggregate/booland_agg.rs:109-133 | crates/embucket-functions/src/aggregate/boolor_agg.rs:72-97 | crates/embucket-functions/src/aggregate/boolor_agg.rs:111-134 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) crates/embucket-functions/src/json.rs:49— crates/embucket-functions/src/json.rs:49-65 | crates/embucket-functions/src/json.rs:72-84 | crates/embucket-functions/src/json.rs:288-300 | crates/embucket-functions/src/json.rs:303-315 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) crates/embucket-functions/src/conversion/to_binary.rs:46— crates/embucket-functions/src/conversion/to_binary.rs:46-64 | crates/embucket-functions/src/semi-structured/get.rs:33-50 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) crates/embucket-functions/src/json.rs:26— crates/embucket-functions/src/json.rs:26-42 | crates/embucket-functions/src/json.rs:743-759 | crates/embucket-functions/src/json.rs:825-837 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) crates/core-sqlite/src/vfs/mod.rs:102— crates/core-sqlite/src/vfs/mod.rs:102-124 | crates/core-sqlite/src/vfs/mod.rs:130-147 | crates/core-sqlite/src/vfs/mod.rs:148-165 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) crates/core-executor/src/datafusion/physical_plan/merge.rs:113— crates/core-executor/src/datafusion/physical_plan/merge.rs:113-130 | crates/core-executor/src/datafusion/physical_plan/merge.rs:266-281 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) crates/df-catalog/src/catalogs/slatedb/databases.rs:85— crates/df-catalog/src/catalogs/slatedb/databases.rs:85-95 | crates/df-catalog/src/catalogs/slatedb/schemas.rs:85-95 | crates/df-catalog/src/catalogs/slatedb/volumes.rs:85-95 | crates/df-catalog/src/catalogs/slatedb/worksheets.rs:97-108 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:28— crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:28-44 | crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:55-71 | crates/df-catalog/src/catalogs/slatedb/metastore_config.rs:81-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:525— crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:525-533 | crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:558-566 | crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:568-576 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) crates/embucket-functions/src/conversion/to_date.rs:49— crates/embucket-functions/src/conversion/to_date.rs:49-70 | crates/embucket-functions/src/conversion/to_decimal.rs:28-56 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) crates/embucket-functions/src/visitors/fetch_to_limit.rs:51— crates/embucket-functions/src/visitors/fetch_to_limit.rs:51-56 | crates/embucket-functions/src/visitors/unimplemented/functions_checker.rs:65-70 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (38 lines × 2) crates/embucket-functions/src/string-binary/hex_decode_binary.rs:82— crates/embucket-functions/src/string-binary/hex_decode_binary.rs:82-119 | crates/embucket-functions/src/string-binary/hex_decode_string.rs:83-120 — before extracting anything, compare `crates/embucket-functions/src/string-binary/hex_decode_binary.rs` and `crates/embucket-functions/src/string-binary/hex_decode_string.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (37 lines × 3) crates/embucket-functions/src/regexp/regexp_instr.rs:209— crates/embucket-functions/src/regexp/regexp_instr.rs:209-245 | crates/embucket-functions/src/regexp/regexp_substr.rs:173-209 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:176-212 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_substr.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 183 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:209` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (37 lines × 2) crates/embucket-functions/src/string-binary/hex_decode_binary.rs:133— crates/embucket-functions/src/string-binary/hex_decode_binary.rs:133-169 | crates/embucket-functions/src/string-binary/hex_decode_string.rs:134-170 — before extracting anything, compare `crates/embucket-functions/src/string-binary/hex_decode_binary.rs` and `crates/embucket-functions/src/string-binary/hex_decode_string.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 `crates/embucket-functions/src/string-binary/hex_decode_binary.rs:133` 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 (33 lines × 2) crates/embucket-functions/src/string-binary/substr.rs:613— crates/embucket-functions/src/string-binary/substr.rs:613-645 | crates/embucket-functions/src/string-binary/substr.rs:670-702 — 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 `crates/embucket-functions/src/string-binary/substr.rs:613` 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 (28 lines × 2) crates/embucket-functions/src/encryption/decrypt_raw.rs:179— crates/embucket-functions/src/encryption/decrypt_raw.rs:179-206 | crates/embucket-functions/src/encryption/encrypt_raw.rs:165-192 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/encryption/decrypt_raw.rs:179` 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 (26–27 lines × 2) crates/embucket-functions/src/encryption/decrypt_raw.rs:88— crates/embucket-functions/src/encryption/decrypt_raw.rs:88-114 | crates/embucket-functions/src/encryption/encrypt_raw.rs:92-117 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/encryption/decrypt_raw.rs:88` 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 (25 lines × 2) crates/embucket-functions/src/encryption/decrypt_raw.rs:269— crates/embucket-functions/src/encryption/decrypt_raw.rs:269-293 | crates/embucket-functions/src/encryption/encrypt_raw.rs:224-248 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 (24 lines × 5) crates/embucket-functions/src/regexp/regexp_instr.rs:190— crates/embucket-functions/src/regexp/regexp_instr.rs:190-213 | crates/embucket-functions/src/regexp/regexp_like.rs:127-150 | crates/embucket-functions/src/regexp/regexp_replace.rs:163-186 | crates/embucket-functions/src/regexp/regexp_substr.rs:154-177 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:157-180 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:190` 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 (23–24 lines × 4) crates/embucket-functions/src/regexp/regexp_instr.rs:126— crates/embucket-functions/src/regexp/regexp_instr.rs:126-148 | crates/embucket-functions/src/regexp/regexp_replace.rs:116-139 | crates/embucket-functions/src/regexp/regexp_substr.rs:113-135 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:116-138 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:126` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24 lines × 2) crates/embucket-functions/src/numeric/div0.rs:171— crates/embucket-functions/src/numeric/div0.rs:171-194 | crates/embucket-functions/src/numeric/div0.rs:196-219 — 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 (23 lines × 2) crates/embucket-functions/src/semi-structured/array/array_max.rs:37— crates/embucket-functions/src/semi-structured/array/array_max.rs:37-59 | crates/embucket-functions/src/semi-structured/array/array_min.rs:37-59 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_max.rs` and `crates/embucket-functions/src/semi-structured/array/array_min.rs` as WHOLE FILES: this scan already matched 8 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. 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 `crates/embucket-functions/src/semi-structured/array/array_max.rs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) REDACTED:2671— REDACTED:2671-2690 | REDACTED:2707-2725 — 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:2671` 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 (19 lines × 3) crates/embucket-functions/src/regexp/regexp_replace.rs:242— crates/embucket-functions/src/regexp/regexp_replace.rs:242-260 | crates/embucket-functions/src/regexp/regexp_substr.rs:260-278 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:263-281 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_replace.rs` and `crates/embucket-functions/src/regexp/regexp_substr.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 176 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 `crates/embucket-functions/src/regexp/regexp_replace.rs:242` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) crates/embucket-functions/src/semi-structured/object/object_insert.rs:113— crates/embucket-functions/src/semi-structured/object/object_insert.rs:113-130 | crates/embucket-functions/src/semi-structured/object/object_insert.rs:135-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 `crates/embucket-functions/src/semi-structured/object/object_insert.rs:113` 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 (17 lines × 5) crates/embucket-functions/src/regexp/regexp_instr.rs:284— crates/embucket-functions/src/regexp/regexp_instr.rs:284-300 | crates/embucket-functions/src/regexp/regexp_like.rs:103-119 | crates/embucket-functions/src/regexp/regexp_replace.rs:230-246 | crates/embucket-functions/src/regexp/regexp_substr.rs:248-264 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:251-267 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:284` 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 (17 lines × 3) crates/embucket-functions/src/semi-structured/array/array_except.rs:79— crates/embucket-functions/src/semi-structured/array/array_except.rs:79-95 | crates/embucket-functions/src/semi-structured/array/array_intersection.rs:82-98 | crates/embucket-functions/src/semi-structured/array/arrays_overlap.rs:75-91 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_except.rs` and `crates/embucket-functions/src/semi-structured/array/array_intersection.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `crates/embucket-functions/src/semi-structured/array/array_except.rs: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 (14–16 lines × 4) crates/embucket-functions/src/regexp/regexp_instr.rs:149— crates/embucket-functions/src/regexp/regexp_instr.rs:149-164 | crates/embucket-functions/src/regexp/regexp_replace.rs:147-160 | crates/embucket-functions/src/regexp/regexp_substr.rs:136-151 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:139-154 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:149` 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) crates/embucket-functions/src/encryption/decrypt_raw.rs:160— crates/embucket-functions/src/encryption/decrypt_raw.rs:160-175 | crates/embucket-functions/src/encryption/encrypt_raw.rs:146-161 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/encryption/decrypt_raw.rs:160` 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 (15 lines × 3) crates/embucket-functions/src/string-binary/substr.rs:560— crates/embucket-functions/src/string-binary/substr.rs:560-574 | crates/embucket-functions/src/string-binary/substr.rs:624-638 | crates/embucket-functions/src/string-binary/substr.rs:681-695 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 2) crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:149— crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:149-163 | crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:185-199 — 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 `crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:149` 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 (14 lines × 5) crates/embucket-functions/src/encryption/decrypt_raw.rs:112— crates/embucket-functions/src/encryption/decrypt_raw.rs:112-125 | crates/embucket-functions/src/encryption/decrypt_raw.rs:127-140 | crates/embucket-functions/src/encryption/decrypt_raw.rs:143-156 | crates/embucket-functions/src/encryption/encrypt_raw.rs:115-128 | crates/embucket-functions/src/encryption/encrypt_raw.rs:130-143 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/encryption/decrypt_raw.rs:112` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–14 lines × 3) crates/df-catalog/src/information_schema/config.rs:435— crates/df-catalog/src/information_schema/config.rs:435-448 | crates/df-catalog/src/information_schema/config.rs:450-463 | crates/df-catalog/src/information_schema/config.rs:464-475 — 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 `crates/df-catalog/src/information_schema/config.rs:435` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) crates/embucket-functions/src/aggregate/booland_agg.rs:72— crates/embucket-functions/src/aggregate/booland_agg.rs:72-84 | crates/embucket-functions/src/aggregate/boolor_agg.rs:73-86 — 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 `crates/embucket-functions/src/aggregate/booland_agg.rs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) crates/embucket-functions/src/regexp/regexp_instr.rs:134— crates/embucket-functions/src/regexp/regexp_instr.rs:134-146 | crates/embucket-functions/src/regexp/regexp_instr.rs:156-168 | crates/embucket-functions/src/regexp/regexp_replace.rs:131-143 | crates/embucket-functions/src/regexp/regexp_substr.rs:121-133 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:124-136 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:134` 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–12 lines × 6) crates/embucket-functions/src/regexp/regexp_instr.rs:136— crates/embucket-functions/src/regexp/regexp_instr.rs:136-146 | crates/embucket-functions/src/regexp/regexp_instr.rs:158-169 | crates/embucket-functions/src/regexp/regexp_replace.rs:111-121 | crates/embucket-functions/src/regexp/regexp_replace.rs:133-143 | crates/embucket-functions/src/regexp/regexp_substr.rs:123-133 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:126-136 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:136` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 3) crates/embucket-functions/src/json.rs:500— crates/embucket-functions/src/json.rs:500-511 | crates/embucket-functions/src/json.rs:521-530 | crates/embucket-functions/src/json.rs:546-557 — 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 `crates/embucket-functions/src/json.rs:500` 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 (11–12 lines × 3) crates/embucket-functions/src/semi-structured/array/array_append.rs:86— crates/embucket-functions/src/semi-structured/array/array_append.rs:86-96 | crates/embucket-functions/src/semi-structured/array/array_prepend.rs:72-83 | crates/embucket-functions/src/semi-structured/array/array_remove.rs:80-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/semi-structured/array/array_append.rs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/embucket-functions/src/semi-structured/array/array_prepend.rs:84` calls `encode_scalar` and `crates/embucket-functions/src/semi-structured/array/array_append.rs:97` 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 (12 lines × 3) crates/embucket-functions/src/string-binary/substr.rs:546— crates/embucket-functions/src/string-binary/substr.rs:546-557 | crates/embucket-functions/src/string-binary/substr.rs:591-602 | crates/embucket-functions/src/string-binary/substr.rs:656-667 — 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 `crates/embucket-functions/src/string-binary/substr.rs:546` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–12 lines × 2) crates/embucket-functions/src/visitors/like_ilike_any.rs:30— crates/embucket-functions/src/visitors/like_ilike_any.rs:30-40 | crates/embucket-functions/src/visitors/like_ilike_any.rs:54-65 — 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 `crates/embucket-functions/src/visitors/like_ilike_any.rs:30` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 4) crates/embucket-functions/src/json.rs:184— crates/embucket-functions/src/json.rs:184-194 | crates/embucket-functions/src/json.rs:199-209 | crates/embucket-functions/src/json.rs:715-725 | crates/embucket-functions/src/json.rs:730-740 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/json.rs:184` 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 (9–11 lines × 3) crates/embucket-functions/src/datetime/date_from_parts.rs:95— crates/embucket-functions/src/datetime/date_from_parts.rs:95-103 | crates/embucket-functions/src/datetime/time_from_parts.rs:102-112 | crates/embucket-functions/src/datetime/timestamp_from_parts.rs:183-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (10–11 lines × 2) crates/df-catalog/src/catalogs/slatedb/tables.rs:65— crates/df-catalog/src/catalogs/slatedb/tables.rs:65-74 | crates/df-catalog/src/information_schema/tables.rs:59-69 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22–23 lines × 2) crates/embucket-functions/src/encryption/decrypt_raw.rs:209— crates/embucket-functions/src/encryption/decrypt_raw.rs:209-231 | crates/embucket-functions/src/encryption/encrypt_raw.rs:187-208 — before extracting anything, compare `crates/embucket-functions/src/encryption/decrypt_raw.rs` and `crates/embucket-functions/src/encryption/encrypt_raw.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/encryption/decrypt_raw.rs:209` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/embucket-functions/src/encryption/decrypt_raw.rs:232` calls `as_binary_array`, `cloned`, `transpose` and `crates/embucket-functions/src/encryption/encrypt_raw.rs:209` 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 (9 lines × 6) crates/embucket-functions/src/semi-structured/array/array_compact.rs:82— crates/embucket-functions/src/semi-structured/array/array_compact.rs:82-90 | crates/embucket-functions/src/semi-structured/array/array_distinct.rs:93-101 | crates/embucket-functions/src/semi-structured/array/array_max.rs:129-137 | crates/embucket-functions/src/semi-structured/array/array_min.rs:129-137 | crates/embucket-functions/src/semi-structured/array/array_reverse.rs:75-83 | crates/embucket-functions/src/semi-structured/object/object_pick.rs:108-116 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_compact.rs` and `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `crates/embucket-functions/src/semi-structured/array/array_compact.rs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) crates/embucket-functions/src/conversion/to_timestamp.rs:269— crates/embucket-functions/src/conversion/to_timestamp.rs:269-277 | crates/embucket-functions/src/conversion/to_timestamp.rs:280-288 | crates/embucket-functions/src/conversion/to_timestamp.rs:291-299 | crates/embucket-functions/src/conversion/to_timestamp.rs:302-310 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/conversion/to_timestamp.rs:269` 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 × 7) crates/embucket-functions/src/semi-structured/array/array_append.rs:96— crates/embucket-functions/src/semi-structured/array/array_append.rs:96-103 | crates/embucket-functions/src/semi-structured/array/array_compact.rs:84-91 | crates/embucket-functions/src/semi-structured/array/array_distinct.rs:95-102 | crates/embucket-functions/src/semi-structured/array/array_max.rs:131-138 | crates/embucket-functions/src/semi-structured/array/array_min.rs:131-138 | crates/embucket-functions/src/semi-structured/array/array_reverse.rs:77-84 | crates/embucket-functions/src/semi-structured/object/object_pick.rs:110-117 — before extracting anything, compare `crates/embucket-functions/src/semi-structured/array/array_compact.rs` and `crates/embucket-functions/src/semi-structured/array/array_distinct.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `crates/embucket-functions/src/semi-structured/array/array_append.rs:96` 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 × 3) crates/embucket-functions/src/datetime/dayname.rs:71— crates/embucket-functions/src/datetime/dayname.rs:71-78 | crates/embucket-functions/src/semi-structured/parse_json.rs:59-66 | crates/embucket-functions/src/semi-structured/typeof_func.rs:59-66 — 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 (7–8 lines × 2) crates/df-catalog/src/information_schema/config.rs:146— crates/df-catalog/src/information_schema/config.rs:146-153 | crates/df-catalog/src/information_schema/config.rs:187-193 — 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 `crates/df-catalog/src/information_schema/config.rs:146` 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–8 lines × 3) crates/embucket-functions/src/datetime/add_months.rs:94— crates/embucket-functions/src/datetime/add_months.rs:94-101 | crates/embucket-functions/src/datetime/dayname.rs:79-85 | crates/embucket-functions/src/datetime/next_day.rs:87-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/embucket-functions/src/datetime/add_months.rs:94` 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 × 3) crates/df-catalog/src/catalogs/slatedb/databases.rs:77— crates/df-catalog/src/catalogs/slatedb/databases.rs:77-83 | crates/df-catalog/src/catalogs/slatedb/schemas.rs:77-83 | crates/df-catalog/src/catalogs/slatedb/volumes.rs:77-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/df-catalog/src/catalogs/slatedb/databases.rs:77` 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 (14 lines × 3) REDACTED:1832— REDACTED:1832-1845 | REDACTED:1858-1873 | REDACTED:1886-1904 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 9) crates/embucket-functions/src/regexp/regexp_instr.rs:130— crates/embucket-functions/src/regexp/regexp_instr.rs:130-142 | crates/embucket-functions/src/regexp/regexp_instr.rs:152-164 | crates/embucket-functions/src/regexp/regexp_instr.rs:175-187 | crates/embucket-functions/src/regexp/regexp_replace.rs:127-139 | crates/embucket-functions/src/regexp/regexp_replace.rs:148-160 | crates/embucket-functions/src/regexp/regexp_substr.rs:117-129 | crates/embucket-functions/src/regexp/regexp_substr.rs:139-151 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:120-132 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:142-154 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:130` 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 × 5) crates/embucket-functions/src/regexp/regexp_instr.rs:189— crates/embucket-functions/src/regexp/regexp_instr.rs:189-195 | crates/embucket-functions/src/regexp/regexp_replace.rs:103-109 | crates/embucket-functions/src/regexp/regexp_replace.rs:162-168 | crates/embucket-functions/src/regexp/regexp_substr.rs:153-159 | crates/embucket-functions/src/regexp/regexp_substr_all.rs:156-162 — before extracting anything, compare `crates/embucket-functions/src/regexp/regexp_instr.rs` and `crates/embucket-functions/src/regexp/regexp_replace.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 141 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 `crates/embucket-functions/src/regexp/regexp_instr.rs:189` 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.
Off the main sequence: sqlite-plugin — sqlite-plugin: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Unfinished branch — a todo!() / unimplemented!() arm in a real function REDACTED:3015— `merge_clause_projection` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Outbound HTTP without resilience crates/embucket-seed/src/requests/service_client.rs:89— `reqwest::Client::new(` 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.
Duplication concentrated across 9 sibling directories (19 clone groups) ui/src/modules/databases/databases-page-table.tsx:13— 19 duplicated blocks under ui/src/modules/ have copies in at least two of the sibling directories columns, data-preview, databases, home, queries, schemas (+3 more sibling(s) not listed) — 12 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 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 4 sibling directories (8 clone groups) ui/src/modules/shared/create-database-dialog/create-database-dialog.tsx:28— 8 duplicated blocks under ui/src/modules/shared/ have copies in at least two of the sibling directories create-database-dialog, create-schema-dialog, create-volume-dialog, table-data-upload-dialog — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (113 matched lines × 2 locations) · ×1
Duplicated block with local edits (113 matched lines × 2 locations) ui/src/components/ui/dropdown-menu.tsx:6— ui/src/components/ui/dropdown-menu.tsx:6 · ui/src/components/ui/select.tsx:6 — the two spans are one implementation copied and then locally edited — 496 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 (76 matched lines × 2 locations) · ×1
Duplicated block with local edits (76 matched lines × 2 locations) ui/src/components/ui/alert-dialog.tsx:7— ui/src/components/ui/alert-dialog.tsx:7 · ui/src/components/ui/dialog.tsx:10 — the two spans are one implementation copied and then locally edited — 379 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 (30 lines × 2 locations) ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:64— ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:64 · ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx:95 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (28 lines × 2 locations) ui/src/modules/columns/columns-page-toolbar.tsx:15— ui/src/modules/columns/columns-page-toolbar.tsx:15 · ui/src/modules/data-preview/data-preview-page-toolbar.tsx:15 — 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 (28 lines × 4 locations) ui/src/modules/databases/databases-page-toolbar.tsx:15— ui/src/modules/databases/databases-page-toolbar.tsx:15 · ui/src/modules/schemas/schemas-page-toolbar.tsx:15 · ui/src/modules/tables/tables-page-toolbar.tsx:15 · ui/src/modules/volumes/volumes-page-toolbar.tsx:15 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (27 lines × 2 locations) ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:40— ui/src/modules/shared/create-database-dialog/create-database-dialog-form.tsx:40 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:204 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) ui/src/modules/columns/columns-page.tsx:34— ui/src/modules/columns/columns-page.tsx:34 · ui/src/modules/data-preview/data-preview-page.tsx:52 — 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 (24 lines × 2 locations) ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:49— ui/src/modules/shared/create-schema-dialog/create-schema-dialog.tsx:49 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog.tsx:44 — 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 (22 lines × 2 locations) ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-databases.tsx:16— ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-databases.tsx:16 · ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown-schemas.tsx:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (19 lines × 2 locations) ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx:17— ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx:17 · ui/src/modules/editor/editor-center-panel/editor-center-panel-header/editor-center-panel-header.tsx:14 — 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 (16 lines × 2 locations) ui/src/modules/columns/columns-page.tsx:99— ui/src/modules/columns/columns-page.tsx:99 · ui/src/modules/data-preview/data-preview-page.tsx:118 — 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 (15 lines × 3 locations) ui/src/modules/databases/databases-page-table.tsx:15— ui/src/modules/databases/databases-page-table.tsx:15 · ui/src/modules/tables/tables-page-table.tsx:17 · ui/src/modules/volumes/volumes-page-table.tsx:13 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (14 lines × 8 locations) ui/src/components/ui/alert-dialog.tsx:60— ui/src/components/ui/alert-dialog.tsx:60 · ui/src/components/ui/alert.tsx:30 · ui/src/components/ui/breadcrumb.tsx:17 · ui/src/components/ui/card.tsx:23 · +4 more site(s) not listed — the 8 copies are spread across 7 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 (13 lines × 4 locations) ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:260— ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:260 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:276 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:289 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:302 — all 4 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (13 lines × 3 locations) ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:279— ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:279 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:292 · ui/src/modules/shared/create-volume-dialog/create-volume-dialog-form.tsx:305 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (12 lines × 4 locations) ui/src/modules/home/home-dashboard-metrics.tsx:20— ui/src/modules/home/home-dashboard-metrics.tsx:20 · ui/src/modules/home/home-dashboard-metrics.tsx:32 · ui/src/modules/home/home-dashboard-metrics.tsx:44 · ui/src/modules/home/home-dashboard-metrics.tsx:56 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 2 locations) ui/src/modules/databases/databases-page.tsx:30— ui/src/modules/databases/databases-page.tsx:30 · ui/src/modules/volumes/volumes-page.tsx:26 — 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 (9 lines × 2 locations) ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:53— ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:53 · ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx:72 — 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 (9 lines × 3 locations) ui/src/modules/columns/columns-page-table.tsx:3— ui/src/modules/columns/columns-page-table.tsx:3 · ui/src/modules/queries/queries-history-table.tsx:8 · ui/src/modules/volumes/volumes-page-table.tsx:4 — the 3 copies are spread across 3 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 (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-beautify-button.tsx:7— ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-beautify-button.tsx:7 · ui/src/modules/editor/editor.tsx:29 — the two spans are one implementation copied and then locally edited — 69 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 (6 lines × 5 locations) ui/src/components/ui/alert-dialog.tsx:3— ui/src/components/ui/alert-dialog.tsx:3 · ui/src/components/ui/dialog.tsx:2 · ui/src/components/ui/dropdown-menu.tsx:2 · ui/src/components/ui/hover-card.tsx:3 · +1 more site(s) not listed — the 5 copies are spread across 5 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.
Complex function EditorCenterBottomPanel (cyclomatic 15, cognitive 14) ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx:23— EditorCenterBottomPanel has cyclomatic complexity 15 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.
Complex function TableDataUploadDialog (cyclomatic 15, cognitive 10) ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dialog.tsx:32— TableDataUploadDialog has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getDisplayValue (cyclomatic 13, cognitive 17) ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx:7— getDisplayValue has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function EditorLeftBottomPanel (cyclomatic 12, cognitive 9) ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx:12— EditorLeftBottomPanel has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· ui/src/components/ui/sidebar.tsx · ×1
ui/src/components/ui/sidebar.tsx: 604 lines of code ui/src/components/ui/sidebar.tsx:1— ui/src/components/ui/sidebar.tsx has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~234 LoC) ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~231 LoC) ui/src/components/ui/dropdown-menu.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx, ui/src/app/layout/sidebar/app-sidebar-org-menu.tsx, ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~211 LoC) ui/src/modules/editor/editor-panels-state-provider.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (ui/src/app/routes/sql-editor/$worksheetId.index.tsx, ui/src/modules/editor/editor-center-panel/editor-center-panel-footer.tsx, ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~185 LoC) ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~164 LoC) ui/src/modules/editor/editor.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx, ui/src/modules/editor/editor-right-panel/editor-right-panel-query/editor-right-panel-query.tsx, ui/src/modules/query/query-sql.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~161 LoC) ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion-types.ts— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~143 LoC) ui/src/modules/editor/editor-theme.ts— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts, ui/src/modules/editor/editor.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~142 LoC) ui/src/modules/editor/editor-left-panel/editor-left-panel-trees/editor-left-panel-trees.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~141 LoC) ui/src/components/ui/alert-dialog.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/shared/delete-worksheet-alert-dialog/delete-worksheet-alert-dialog.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~137 LoC) ui/src/app/layout/sidebar/app-sidebar.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/__root.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~133 LoC) ui/src/modules/data-preview/data-preview-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.$tableName.data-preview.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~129 LoC) ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~121 LoC) ui/src/modules/tables/tables-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.$schemaName.tables.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~107 LoC) ui/src/modules/shared/data-page/data-page-trees.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/shared/data-page/data-page-layout.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~103 LoC) ui/src/components/ui/tabs.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (ui/src/modules/columns/columns-page.tsx, ui/src/modules/data-preview/data-preview-page.tsx, ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~102 LoC) ui/src/modules/auth/sign-in-form.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/auth/sign-in-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~101 LoC) ui/src/components/ui/breadcrumb.tsx— no import path from any entry point (8 application, 9 tooling, 8 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
Dead file (~99 LoC) ui/src/app/layout/sidebar/app-sidebar-avatar-menu.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~93 LoC) ui/src/modules/editor/editor-left-panel/editor-left-panel.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~90 LoC) ui/src/modules/shared/delete-worksheet-alert-dialog/delete-worksheet-alert-dialog.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-worksheets/editor-left-panel-worksheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~89 LoC) ui/src/modules/editor/editor-center-panel/editor-context-dropdown/editor-context-dropdown.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~88 LoC) ui/src/modules/queries/queries-history-table.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/queries/queries-history-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~79 LoC) ui/src/modules/databases/databases-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~76 LoC) ui/src/modules/schemas/schemas-page.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/app/routes/databases/_dataPagesLayout.$databaseName.schemas.index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~73 LoC) ui/src/components/ui/card.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/auth/sign-in-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~70 LoC) ui/src/modules/editor/editor-extensions/editor-autocomplete/icons-svg.ts— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-extensions/editor-autocomplete/auto-completion.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~66 LoC) ui/src/app/layout/sidebar/app-sidebar-group.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (ui/src/app/layout/sidebar/app-sidebar-sql-group.tsx, ui/src/app/layout/sidebar/app-sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~65 LoC) ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-panel-table-columns-toolbar.tsx— no import path from any entry point (8 application, 9 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/modules/editor/editor-left-panel/editor-left-panel-table-columns/editor-left-bottom-panel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency '@tidbcloud/codemirror-extension-events' ui/package.json:55— Declared in ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'npm-check-updates' ui/package.json:100— Declared in ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X12 · Unreachable branch· Statement is unreachable · ×1
Statement is unreachable — control never gets past the statement before it crates/core-sqlite/src/vfs/mod.rs:796— `sqlite_plugin::vars::SQLITE_OK_LOAD_PERMANENTLY` follows `{ return err; }` (line 792) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
Orphaned file crates/embucket-functions/src/conversion/to_timestamp.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-metastore/src/metastore.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/json.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-executor/src/datafusion/physical_plan/merge.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-executor/src/service.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 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 crates/core-history/src/sqlite_history_store.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-sqlite/src/vfs/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-sqlite/src/vfs/sqlite-plugin/src/vfs.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/string-binary/substr.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/datetime/timestamp_from_parts.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-executor/src/snowflake_error.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/errors.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/datetime/date_part_extract.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/conversion/to_varchar.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/df-catalog/src/catalog_list.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core-executor/src/error.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucketd/src/main.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ui/src/components/ui/sidebar.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 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 crates/core-utils/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/df-catalog/src/catalogs/embucket/iceberg_catalog.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/aggregate/object_agg.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/df-catalog/src/information_schema/config.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/embucket-functions/src/table/flatten/provider.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Documentation: no build, run or usage example crates/api-iceberg-rest/README.md:1— `api-iceberg-rest` is a published crate (`[package]` without `publish = false`) and neither `crates/api-iceberg-rest/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.
Documentation: no build, run or usage example crates/api-sessions/README.md:1— `api-sessions` is a published crate (`[package]` without `publish = false`) and neither `crates/api-sessions/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.
Documentation: no build, run or usage example crates/api-ui/README.md:1— `api-ui` is a published crate (`[package]` without `publish = false`) and neither `crates/api-ui/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.
Documentation: no build, run or usage example crates/api-ui-static-assets/README.md:1— `api-ui-static-assets` is a published crate (`[package]` without `publish = false`) and neither `crates/api-ui-static-assets/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.
Documentation: no build, run or usage example crates/core-history/README.md:1— `core-history` is a published crate (`[package]` without `publish = false`) and neither `crates/core-history/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.
Documentation: no build, run or usage example crates/core-metastore/README.md:1— `core-metastore` is a published crate (`[package]` without `publish = false`) and neither `crates/core-metastore/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.
Documentation: no build, run or usage example crates/core-sqlite/src/vfs/sqlite-plugin/README.md:1— `sqlite-plugin` is a published crate (`[package]` without `publish = false`) and neither `crates/core-sqlite/src/vfs/sqlite-plugin/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.
Documentation: no build, run or usage example crates/core-utils/README.md:1— `core-utils` is a published crate (`[package]` without `publish = false`) and neither `crates/core-utils/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.
Documentation: no build, run or usage example crates/df-catalog/README.md:1— `df-catalog` is a published crate (`[package]` without `publish = false`) and neither `crates/df-catalog/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.
Documentation: no build, run or usage example crates/embucket-functions/README.md:1— `embucket-functions` is a binary crate (`[[bin]]` in `Cargo.toml`) and neither `crates/embucket-functions/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.
Documentation: no build, run or usage example crates/embucketd/README.md:1— `embucketd` is a binary crate (`src/main.rs`) and neither `crates/embucketd/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.
Interpolated log message defeats structured logging crates/core-sqlite/src/lib.rs:64— `debug!` at line 64 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/lib.rs:66— `debug!` at line 66 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/init.rs:25— `info!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/init.rs:46— `info!` at line 46 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/init.rs:76— `error!` at line 76 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/mod.rs:655— `error!` at line 655 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/mod.rs:759— `error!` at line 759 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-sqlite/src/vfs/mod.rs:766— `error!` at line 766 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-history/src/sqlite_history_store.rs:461— `info!` at line 461 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-history/src/entities/result_set.rs:110— `error!` at line 110 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core-executor/src/service.rs:741— `error!` at line 741 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Silent fallback default on Err crates/df-catalog/src/catalogs/embucket/catalog.rs:63— `schema_names` turns every `Err` into `vec![]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/datetime/date_diff.rs:69— `week_start` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/datetime/date_part_extract.rs:89— `week_start` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/datetime/date_part_extract.rs:96— `week_of_year_policy` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/datetime/last_day.rs:70— `week_start` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/conversion/to_timestamp.rs:473— `try_parse_with_regex` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/string-binary/substr.rs:302— `compute_substr_string` turns every `Err` into `String::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/embucket-functions/src/string-binary/substr.rs:342— `compute_substr_binary` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Duplicated predicate ui/src/modules/queries/queries-history-table.tsx:39— `status === 'successful' && 'text-green-500'` appears character-identically in 2 files — ui/src/modules/queries/queries-history-table.tsx, ui/src/modules/query/query-details.tsx. 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 crates/embucket-functions/src/encryption/decrypt_raw.rs:108— `matches!(coerced_types[0], DataType::Binary) && matches!(coerced_types[1], DataType::Binary) && matches!(coerced_types[2], DataType::Binary)` appears character-identically in 2 files — crates/embucket-functions/src/encryption/decrypt_raw.rs, crates/embucket-functions/src/encryption/encrypt_raw.rs. 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 crates/embucket-functions/src/encryption/decrypt_raw.rs:122— `matches!(coerced_types[0], DataType::Binary) && matches!(coerced_types[1], DataType::Binary) && matches!(coerced_types[2], DataType::Binary)…` appears character-identically in 2 files — crates/embucket-functions/src/encryption/decrypt_raw.rs, crates/embucket-functions/src/encryption/encrypt_raw.rs. 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 crates/embucket-functions/src/encryption/decrypt_raw.rs:137— `matches!(coerced_types[0], DataType::Binary) && matches!(coerced_types[1], DataType::Binary) && matches!(coerced_types[2], DataType::Binary)…` appears character-identically in 2 files — crates/embucket-functions/src/encryption/decrypt_raw.rs, crates/embucket-functions/src/encryption/encrypt_raw.rs. 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 crates/embucket-functions/src/aggregate/any_value.rs:179— `states.is_empty() || states[0].is_empty()` appears character-identically in 2 files — crates/embucket-functions/src/aggregate/any_value.rs, crates/embucket-functions/src/aggregate/percentile_cont.rs. 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 crates/embucket-functions/src/semi-structured/array/array_cat.rs:147— `string_array1.is_null(i) || string_array2.is_null(i)` appears character-identically in 2 files — crates/embucket-functions/src/semi-structured/array/array_cat.rs, crates/embucket-functions/src/semi-structured/array/arrays_overlap.rs. 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.
redundant comment ui/src/components/ui/sidebar.tsx:64— "This sets the cookie to keep the sidebar state." repeats the code it sits on: 4 of its 5 words (sets, cookie, sidebar, state) are already in `document.cookie = `${SIDEBAR_COOKIE_NAME}=${openState}; path=/; max-age=${SIDEBAR_COOKIE_MAX_AGE}`;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/ui/toggle.tsx:6— "data-[state=on]:bg-accent" repeats the code it sits on: 4 of its 4 words (data, state, bg, accent) are already in `const toggleVariants = cva(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/modules/editor/editor-theme.ts:142— "Extension to enable the One Dark theme (both the editor theme and the highlight style)." repeats the code it sits on: 6 of its 7 words (extension, dark, theme, editor, highlight, style) are already in `export const SQL_EDITOR_THEME: Extension = [theme, syntaxHighlighting(oneDarkHighlightStyle)];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion crates/embucket-functions/Cargo.toml:1— `crates/embucket-functions` (36430 LoC, 277 module-visible types across 29 directories) overshoots its size bounds. 3 of 18 build unit(s) (Cargo, npm) overshoot their size bounds, lowering Project Cohesion to 7.1/10. 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.
Projects may be oversized for their cohesion ui/package.json:1— `ui` (10769 LoC, 293 module-visible types across 46 directories) overshoots its size bounds. 3 of 18 build unit(s) (Cargo, npm) overshoot their size bounds, lowering Project Cohesion to 7.1/10. 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.
Projects may be oversized for their cohesion crates/api-ui/Cargo.toml:1— `crates/api-ui` (5237 LoC, 124 module-visible types across 11 directories) overshoots its size bounds. 3 of 18 build unit(s) (Cargo, npm) overshoot their size bounds, lowering Project Cohesion to 7.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file REDACTED:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file crates/core-executor/src/utils.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file crates/core-executor/src/dedicated_executor.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
No ADRs found crates/embucketd/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `crates/embucketd/src/main.rs` makes this repository a deployable product (line 1).
Dormant codebase — 325 of 325 significant files have no living knowledge — the codebase as a whole is dormant, not 325 separate risks. Counted over 325 of the 598 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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.
README/code drift test/README.md:1— test/README.md links to `test/README.md`, but `test/test/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 15/17 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/benchmarks`.
R8 · Dependency Hygiene· Type-only dependency '@tidbcloud/codemirror-extension-sql-parser' in production deps · ×1
Type-only dependency '@tidbcloud/codemirror-extension-sql-parser' in production deps ui/src/modules/editor/editor-center-panel/editor-center-panel-toolbar/editor-center-panel-toolbar-run-sql-button.tsx:3— Every import is type-only — move it to devDependencies.
No app-layer HTTPS enforcement detected — This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `axum::serve(` (crates/embucketd/src/main.rs:331).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (crates/embucketd/src/main.rs:331).
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 0/5 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.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state ui/src/modules/shared/table-data-upload-dialog/table-data-upload-dropzone.tsx:85— The view draws `<div class="flex flex-col items-center justify-center gap-4 sm:px-5">` under `isAnimating`, but `isAnimating` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default in catch ui/src/modules/editor/editor-center-panel/editor-center-bottom-panel/editor-center-bottom-panel-selected-cell.tsx:28— `getDisplayValue` swallows every exception into `return '[Unserializable]'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated: aes — `aes` is locked at 0.9.0-rc.1 but 0.9.4 is the current stable release on crates.io, and it already satisfies the `"0.9.0-rc.1"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aes` and commit the updated REDACTED.
Outdated: aes-gcm — `aes-gcm` is locked at 0.11.0-rc.1 but 0.11.1 is the current stable release on crates.io, and it already satisfies the `"0.11.0-rc.1"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aes-gcm` and commit the updated REDACTED.
Outdated: async-trait — `async-trait` is locked at 0.1.89 but 0.1.92 is the current stable release on crates.io, and it already satisfies the `"0.1.84"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-trait` and commit the updated REDACTED.
Outdated: aws-config — `aws-config` is locked at 1.8.8 but 1.13.3 is the current stable release on crates.io, and it already satisfies the `"1.5.17"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-config` and commit the updated REDACTED.
Outdated: aws-credential-types — `aws-credential-types` is locked at 1.2.8 but 1.3.1 is the current stable release on crates.io, and it already satisfies the `"1.2.1"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-credential-types` and commit the updated REDACTED.
Outdated: axum — `axum` is locked at 0.8.6 but 0.8.9 is the current stable release on crates.io, and it already satisfies the `"0.8.1"` requirement declared in crates/api-iceberg-rest/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p axum` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.10.1 but 1.12.2 is the current stable release on crates.io, and it already satisfies the `"1.8.0"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: cfg-if — `cfg-if` is locked at 1.0.4 but 1.0.5 is the current stable release on crates.io, and it already satisfies the `"1.0.3"` requirement declared in crates/api-snowflake-rest/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cfg-if` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.42 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4.41"` requirement declared in crates/api-ui/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
Outdated: clang-sys — `clang-sys` is locked at 1.8.1 but 1.9.1 is the current stable release on crates.io, and it already satisfies the `"1.8.1"` requirement declared in crates/core-sqlite/src/vfs/sqlite-plugin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clang-sys` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.5.50 but 4.6.8 is the current stable release on crates.io, and it already satisfies the `"4.5.27"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: cookie — `cookie` is locked at 0.18.1 but 0.18.2 is the current stable release on crates.io, and it already satisfies the `"0.18.1"` requirement declared in crates/embucket-seed/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cookie` and commit the updated REDACTED.
Outdated: dashmap — `dashmap` is locked at 6.1.0 but 6.2.1 is the current stable release on crates.io, and it already satisfies the `"6.1.0"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p dashmap` and commit the updated REDACTED.
Outdated: env_logger — `env_logger` is locked at 0.11.8 but 0.11.11 is the current stable release on crates.io, and it already satisfies the `"0.11.8"` requirement declared in crates/benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p env_logger` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.4 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/api-snowflake-rest/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.31 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/core-executor/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: geo-types — `geo-types` is locked at 0.7.17 but 0.7.20 is the current stable release on crates.io, and it already satisfies the `"0.7.15"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p geo-types` and commit the updated REDACTED.
Outdated: geohash — `geohash` is locked at 0.13.1 but 0.13.2 is the current stable release on crates.io, and it already satisfies the `"0.13.1"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p geohash` and commit the updated REDACTED.
Outdated: http — `http` is locked at 1.3.1 but 1.5.0 is the current stable release on crates.io, and it already satisfies the `"1.2"` requirement declared in crates/api-iceberg-rest/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p http` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.12.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2.7.1"` requirement declared in crates/api-snowflake-rest/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: ipnet — `ipnet` is locked at 2.11.0 but 2.12.2 is the current stable release on crates.io, and it already satisfies the `"2.11.0"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ipnet` and commit the updated REDACTED.
Outdated: lazy_static — `lazy_static` is locked at 1.5.0 but 1.5.1 is the current stable release on crates.io, and it already satisfies the `"1.5.0"` requirement declared in crates/embucket-functions/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p lazy_static` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.28 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4.28"` requirement declared in crates/benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: mimalloc — `mimalloc` is locked at 0.1.48 but 0.1.52 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mimalloc` and commit the updated REDACTED.
Outdated: once_cell — `once_cell` is locked at 1.21.3 but 1.21.4 is the current stable release on crates.io, and it already satisfies the `"1.20.2"` requirement declared in crates/df-catalog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p once_cell` and commit the updated REDACTED.
+ 19 more in this group — see findings.md.
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) — `ui/orval.config.ts`, `ui/src/app/types/vite-env.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1eb58-89ef-7767-b93e-73aa2ced13be · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 151 · Warnings: 752 · Recommendations: 389 · Info: 44 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 21:10 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.