Public report of farm-fe/farm, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 18:56 UTC · Survey ID cd_ec7b26a70ba742b180721bbd2598f820
farm-fe/farm
Measured 14 November 2026, 18:54 UTC, at code version 1d63e29
CAI scoreAt riskUp 12 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 214,039 lines of product code in 372 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Production Readiness, 36
Findings by how serious they are
487 critical1432 serious515 minor
20 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 18:54 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 ▸
69of 69 dimensions measured by tools.
2346of 2434 findings point to an exact file and line, so you can open each one in the code. The other 88 concern the repository as a whole, such as missing documentation.
69dimensions across 7 lenses, read from 214,039 lines of product code in 372 projects.
farm-fe/farm is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because three passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 48 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 10 points. Tidying the declared packages comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 57.
281 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. 113 known security holes in the packages the code depends on can be used by attackers, and seventeen secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the seven security weaknesses in the code, and the five places where the code runs text as code or as a command need a direct call instead. The 15 form fields without a label need a label.
The product code is 214,039 lines, about €240,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 Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 48 to about 57.
Code composition: what the lines of code are
Product code 80%Tests 20%
New since the last survey: 934 findings
These 934 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 439 findings
These 439 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.
Secrets (history) · High secret: WD-SECRET-0005 REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Rebuild cost: about €240,000 · Estimate
Cost to rebuild
€80,000 to €400,000, for 1,340 to 4,250 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 214,039 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 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
Raises the score by about 10 points · Low effort · REDACTED Scanning
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 1 point · 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 €240,000 to build again, about 1.7 person-years of work. Its weakest lens is Production Readiness, at 36 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for low effort, because it clears the 3 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 434,670 lines over the last 90 days, which is about 1,762,828 lines a year. At that pace, the extra work comes to an estimated 179.9 to 1079.4 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.
883 modules, with 1541 dependencies between them. 10 loops run through 48 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 843 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.
farmfe_core.config.config_regex uses serde.core.de, so a change to serde.core.de can break farmfe_core.config.config_regex, while a change to farmfe_core.config.config_regex can't break serde.core.de.
Position
Below the diagonal: farmfe_core.config.config_regex uses a module listed above it, which is the healthy direction.
farmfe_core.module.meta_data.script uses farmfe_core.module.meta_data.script.statement, so a change to farmfe_core.module.meta_data.script.statement can break farmfe_core.module.meta_data.script, while a change to farmfe_core.module.meta_data.script can't break farmfe_core.module.meta_data.script.statement.
Position
Below the diagonal: farmfe_core.module.meta_data.script uses a module listed above it, which is the healthy direction.
farmfe_docs_config.types uses serde.core.de, so a change to serde.core.de can break farmfe_docs_config.types, while a change to farmfe_docs_config.types can't break serde.core.de.
Position
Below the diagonal: farmfe_docs_config.types uses a module listed above it, which is the healthy direction.
farmfe_grass.builtin.modules uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.builtin.modules, while a change to farmfe_grass.builtin.modules can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.builtin.modules uses a module listed above it, which is the healthy direction.
9→14 farmfe_grass.builtin.modules uses farmfe_grass.evaluate.envpart of a loop✕
Connections
1 pair of types, where a type in farmfe_grass.builtin.modules uses a type in farmfe_grass.evaluate.env.
farmfe_grass.builtin.modules uses farmfe_grass.evaluate.env, so a change to farmfe_grass.evaluate.env can break farmfe_grass.builtin.modules, while a change to farmfe_grass.builtin.modules can't break farmfe_grass.evaluate.env.
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.
9→23 farmfe_grass.builtin.modules uses farmfe_grass.valuepart of a loop✕
Connections
1 pair of types, where a type in farmfe_grass.builtin.modules uses a type in farmfe_grass.value.
farmfe_grass.builtin.modules uses farmfe_grass.value, so a change to farmfe_grass.value can break farmfe_grass.builtin.modules, while a change to farmfe_grass.builtin.modules can't break farmfe_grass.value.
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.
packages.docs.src uses packages.core.src.config.types, so a change to packages.core.src.config.types can break packages.docs.src, while a change to packages.docs.src can't break packages.core.src.config.types.
Position
Below the diagonal: packages.docs.src uses a module listed above it, which is the healthy direction.
farmfe_core.config uses farmfe_core.config.config_regex, so a change to farmfe_core.config.config_regex can break farmfe_core.config, while a change to farmfe_core.config can't break farmfe_core.config.config_regex.
Position
Below the diagonal: farmfe_core.config uses a module listed above it, which is the healthy direction.
farmfe_docs_config.validate uses farmfe_docs_config.types, so a change to farmfe_docs_config.types can break farmfe_docs_config.validate, while a change to farmfe_docs_config.validate can't break farmfe_docs_config.types.
Position
Below the diagonal: farmfe_docs_config.validate uses a module listed above it, which is the healthy direction.
farmfe_docs_plan.types uses farmfe_docs_config.types, so a change to farmfe_docs_config.types can break farmfe_docs_plan.types, while a change to farmfe_docs_plan.types can't break farmfe_docs_config.types.
Position
Below the diagonal: farmfe_docs_plan.types uses a module listed above it, which is the healthy direction.
farmfe_grass.evaluate.env uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.evaluate.env, while a change to farmfe_grass.evaluate.env can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.evaluate.env uses a module listed above it, which is the healthy direction.
farmfe_grass.evaluate.env uses farmfe_grass.builtin.modules, so a change to farmfe_grass.builtin.modules can break farmfe_grass.evaluate.env, while a change to farmfe_grass.evaluate.env can't break farmfe_grass.builtin.modules.
Position
Below the diagonal: farmfe_grass.evaluate.env uses a module listed above it, which is the healthy direction.
14→16 farmfe_grass.evaluate.env uses farmfe_grass.evaluate.visitorpart of a loop✕
Connections
1 pair of types, where a type in farmfe_grass.evaluate.env uses a type in farmfe_grass.evaluate.visitor.
farmfe_grass.evaluate.env uses farmfe_grass.evaluate.visitor, so a change to farmfe_grass.evaluate.visitor can break farmfe_grass.evaluate.env, while a change to farmfe_grass.evaluate.env can't break farmfe_grass.evaluate.visitor.
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.
14→23 farmfe_grass.evaluate.env uses farmfe_grass.valuepart of a loop✕
Connections
1 pair of types, where a type in farmfe_grass.evaluate.env uses a type in farmfe_grass.value.
farmfe_grass.evaluate.env uses farmfe_grass.value, so a change to farmfe_grass.value can break farmfe_grass.evaluate.env, while a change to farmfe_grass.evaluate.env can't break farmfe_grass.value.
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.
farmfe_core.module uses serde.core.de, so a change to serde.core.de can break farmfe_core.module, while a change to farmfe_core.module can't break serde.core.de.
Position
Below the diagonal: farmfe_core.module uses a module listed above it, which is the healthy direction.
farmfe_core.module uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_core.module, while a change to farmfe_core.module can't break farmfe_core.config.
Position
Below the diagonal: farmfe_core.module uses a module listed above it, which is the healthy direction.
farmfe_grass.evaluate.visitor uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.evaluate.visitor, while a change to farmfe_grass.evaluate.visitor can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.evaluate.visitor uses a module listed above it, which is the healthy direction.
farmfe_grass.evaluate.visitor uses farmfe_grass.evaluate.env, so a change to farmfe_grass.evaluate.env can break farmfe_grass.evaluate.visitor, while a change to farmfe_grass.evaluate.visitor can't break farmfe_grass.evaluate.env.
Position
Below the diagonal: farmfe_grass.evaluate.visitor uses a module listed above it, which is the healthy direction.
16→23 farmfe_grass.evaluate.visitor uses farmfe_grass.valuepart of a loop✕
Connections
1 pair of types, where a type in farmfe_grass.evaluate.visitor uses a type in farmfe_grass.value.
farmfe_grass.evaluate.visitor uses farmfe_grass.value, so a change to farmfe_grass.value can break farmfe_grass.evaluate.visitor, while a change to farmfe_grass.evaluate.visitor can't break farmfe_grass.value.
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.
16→26 farmfe_grass.evaluate.visitor uses farmfe_grass.ast.argspart of a loop✕
Connections
3 pairs of types, where a type in farmfe_grass.evaluate.visitor uses a type in farmfe_grass.ast.args.
farmfe_grass.evaluate.visitor uses farmfe_grass.ast.args, so a change to farmfe_grass.ast.args can break farmfe_grass.evaluate.visitor, while a change to farmfe_grass.evaluate.visitor can't break farmfe_grass.ast.args.
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.
farmfe_core.plugin.hooks.load uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.load, while a change to farmfe_core.plugin.hooks.load can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.load uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.process_module uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.process_module, while a change to farmfe_core.plugin.hooks.process_module can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.process_module uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.resolve uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.resolve, while a change to farmfe_core.plugin.hooks.resolve can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.resolve uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.transform uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.transform, while a change to farmfe_core.plugin.hooks.transform can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.transform uses a module listed above it, which is the healthy direction.
farmfe_core.resource uses serde.core.de, so a change to serde.core.de can break farmfe_core.resource, while a change to farmfe_core.resource can't break serde.core.de.
Position
Below the diagonal: farmfe_core.resource uses a module listed above it, which is the healthy direction.
farmfe_core.resource uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.resource, while a change to farmfe_core.resource can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.resource uses a module listed above it, which is the healthy direction.
farmfe_core.resource.resource_pot uses serde.core.de, so a change to serde.core.de can break farmfe_core.resource.resource_pot, while a change to farmfe_core.resource.resource_pot can't break serde.core.de.
Position
Below the diagonal: farmfe_core.resource.resource_pot uses a module listed above it, which is the healthy direction.
farmfe_core.resource.resource_pot uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.resource.resource_pot, while a change to farmfe_core.resource.resource_pot can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.resource.resource_pot uses a module listed above it, which is the healthy direction.
farmfe_grass.value uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.value, while a change to farmfe_grass.value can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.value uses a module listed above it, which is the healthy direction.
farmfe_grass.value uses farmfe_grass.evaluate.visitor, so a change to farmfe_grass.evaluate.visitor can break farmfe_grass.value, while a change to farmfe_grass.value can't break farmfe_grass.evaluate.visitor.
Position
Below the diagonal: farmfe_grass.value uses a module listed above it, which is the healthy direction.
farmfe_core.module.module_graph uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.module.module_graph, while a change to farmfe_core.module.module_graph can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.module.module_graph uses a module listed above it, which is the healthy direction.
farmfe_core.module.module_graph uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_core.module.module_graph, while a change to farmfe_core.module.module_graph can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_core.module.module_graph uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.analyze_deps uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.analyze_deps, while a change to farmfe_core.plugin.hooks.analyze_deps can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.analyze_deps uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.analyze_deps uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_core.plugin.hooks.analyze_deps, while a change to farmfe_core.plugin.hooks.analyze_deps can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_core.plugin.hooks.analyze_deps uses a module listed above it, which is the healthy direction.
farmfe_grass.ast.args uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.ast.args, while a change to farmfe_grass.ast.args can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.ast.args uses a module listed above it, which is the healthy direction.
farmfe_grass.ast.args uses farmfe_grass.value, so a change to farmfe_grass.value can break farmfe_grass.ast.args, while a change to farmfe_grass.ast.args can't break farmfe_grass.value.
Position
Below the diagonal: farmfe_grass.ast.args uses a module listed above it, which is the healthy direction.
farmfe_grass.serializer uses farmfe_grass.common, so a change to farmfe_grass.common can break farmfe_grass.serializer, while a change to farmfe_grass.serializer can't break farmfe_grass.common.
Position
Below the diagonal: farmfe_grass.serializer uses a module listed above it, which is the healthy direction.
farmfe_grass.serializer uses farmfe_grass.value, so a change to farmfe_grass.value can break farmfe_grass.serializer, while a change to farmfe_grass.serializer can't break farmfe_grass.value.
Position
Below the diagonal: farmfe_grass.serializer uses a module listed above it, which is the healthy direction.
farmfe_core.cache.module_cache uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.cache.module_cache, while a change to farmfe_core.cache.module_cache can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.cache.module_cache uses a module listed above it, which is the healthy direction.
farmfe_core.cache.module_cache uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.cache.module_cache, while a change to farmfe_core.cache.module_cache can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.cache.module_cache uses a module listed above it, which is the healthy direction.
farmfe_core.module.module_group uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.module.module_group, while a change to farmfe_core.module.module_group can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.module.module_group uses a module listed above it, which is the healthy direction.
farmfe_core.module.module_group uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.module.module_group, while a change to farmfe_core.module.module_group can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.module.module_group uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.config.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
farmfe_core.plugin uses farmfe_core.plugin.hooks.analyze_deps, so a change to farmfe_core.plugin.hooks.analyze_deps can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.analyze_deps.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
30→31 farmfe_core.plugin uses farmfe_core.statspart of a loop✕
Connections
1 pair of types, where a type in farmfe_core.plugin uses a type in farmfe_core.stats.
farmfe_core.plugin uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.stats.
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.
30→32 farmfe_core.plugin uses farmfe_core.contextpart of a loop✕
Connections
1 pair of types, where a type in farmfe_core.plugin uses a type in farmfe_core.context.
farmfe_core.plugin uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.context.
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.
farmfe_core.stats uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.stats, while a change to farmfe_core.stats can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.stats uses a module listed above it, which is the healthy direction.
farmfe_core.stats uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.stats, while a change to farmfe_core.stats can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.stats uses a module listed above it, which is the healthy direction.
farmfe_core.stats uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_core.stats, while a change to farmfe_core.stats can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_core.stats uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.config.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.resource, so a change to farmfe_core.resource can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.resource.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.cache.module_cache, so a change to farmfe_core.cache.module_cache can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.cache.module_cache.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.module.module_group, so a change to farmfe_core.module.module_group can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.module.module_group.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_core.context uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.stats.
Position
Below the diagonal: farmfe_core.context uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.config.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.module.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_compiler uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_compiler, while a change to farmfe_compiler can't break farmfe_core.context.
Position
Below the diagonal: farmfe_compiler uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.config.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.stats.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_node.plugin_adapters.js_plugin_adapter, while a change to farmfe_node.plugin_adapters.js_plugin_adapter can't break farmfe_core.context.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook, while a change to farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook, while a change to farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook can't break farmfe_core.context.
Position
Below the diagonal: farmfe_node.plugin_adapters.js_plugin_adapter.thread_safe_js_plugin_hook uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.config.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.module.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin.hooks.analyze_deps, so a change to farmfe_core.plugin.hooks.analyze_deps can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.hooks.analyze_deps.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.stats.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_node.plugin_adapters.rust_plugin_adapter uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_node.plugin_adapters.rust_plugin_adapter, while a change to farmfe_node.plugin_adapters.rust_plugin_adapter can't break farmfe_core.context.
Position
Below the diagonal: farmfe_node.plugin_adapters.rust_plugin_adapter uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin.hooks.analyze_deps, so a change to farmfe_core.plugin.hooks.analyze_deps can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.hooks.analyze_deps.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_css uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_docs_config.validate, so a change to farmfe_docs_config.validate can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_docs_config.validate.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_docs_plan.types, so a change to farmfe_docs_plan.types can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_docs_plan.types.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_docs, while a change to farmfe_plugin_docs can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_docs uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_docs_plan.types, so a change to farmfe_docs_plan.types can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_docs_plan.types.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.stats.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_docs_snapshot uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_docs_snapshot, while a change to farmfe_plugin_docs_snapshot can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_docs_snapshot uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.plugin.hooks.process_module, so a change to farmfe_core.plugin.hooks.process_module can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.plugin.hooks.process_module.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.plugin.hooks.analyze_deps, so a change to farmfe_core.plugin.hooks.analyze_deps can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.plugin.hooks.analyze_deps.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_script uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 66% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
344
High / Critical
A03:2025 — Software Supply Chain Failures
249
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
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.
Dependency Vulnerabilities: High vulnerability: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.6
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.5
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.2
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
How the grades work
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 — 487
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 — 1432
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 — 515
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 20
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 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 69 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, 2346 of 2434 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 JavaScript/TypeScript half could not be measured — the dependency install for the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,063 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 253 test source file(s) (.py, .rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in crates/create-farm-rs/templates/nestjs/ was NOT MEASURED: the dependency install for crates/create-farm-rs/templates/nestjs/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in examples/commerce-lab/ was NOT MEASURED: the dependency install for examples/commerce-lab/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/nestjs/ was NOT MEASURED: the dependency install for examples/nestjs/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in js-plugins/dts/ was NOT MEASURED: the dependency install for js-plugins/dts/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#t…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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 REDACTED, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — 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. 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.
D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `crates/create-farm-rs/templates/electron/preact/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/react/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/solid/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/svelte/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/vanilla/electron/electron-env.d.ts`, … (+18 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> farm-fe@0.0.0 start / > pnpm --filter @farmfe/cli start / sh: 1: pnpm: not found" No runtime evidence was gathered.
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 DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> farm-fe@0.0.0 start / > pnpm --filter @farmfe/cli start / sh: 1: pnpm: not found" No runtime evidence was gathered.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust, Svelte components, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust, Svelte components, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
PF3 Async & latency hygiene — 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 55 further occurrence(s) are not listed individually; the score already reflects all 95.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 129 further occurrence(s) are not listed individually; the score already reflects all 169.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 161 further occurrence(s) are not listed individually; the score already reflects all 201.
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. 77 further occurrence(s) are not listed individually; the score already reflects all 117.
R8 Dependency Hygiene — 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. 186 further occurrence(s) are not listed individually; the score already reflects all 226.
X10 Duplicated predicate — 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
161 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was farmfe_ecosystem_glob::compile::compile_body_with_context at 119. A further 3 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 farmfe_ecosystem_tailwindcss::variants::resolve_named at 48 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/create-farm-rs/src/template.rs (Template::display_text at 30), rust-ecosystem/tailwindcss/src/utils/infer_data_type.rs (farmfe_ecosystem_tailwindcss::utils::infer_data_type::check at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 96 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with farmfe_ecosystem_glob::compile::compile_body_with_context (cyclomatic 119), farmfe_ecosystem_glob::scan::scan (cyclomatic 91), SfcParser::try_parse_directive (cyclomatic 82). — 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 5 together lifts Cyclomatic Complexity from 4.9 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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.
+ 151 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 32 bodies over 60 down to 60 or less in Cognitive Complexity — start with farmfe_ecosystem_glob::compile::compile_body_with_context (cognitive 306), farmfe_ecosystem_glob::scan::scan (cognitive 253), farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements (cognitive 161). — 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 32 together lifts Cognitive Complexity from 2.0 to about 4.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 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 52 FunctionTooLong finding(s) in God Classes — start with compile.rs (2), REDACTED (2), prepare.rs. — One of this dimension's main actionable groups (52 warning-level).
Resolve the 26 MethodTooLong finding(s) in God Classes — start with lib.rs (10), resolve_type.rs (4), utilities.rs (2). — One of this dimension's main actionable groups (26 warning-level).
Resolve the 22 FileTooLong finding(s) in God Classes — start with lib.rs (6), compile.rs, utilities.rs. — One of this dimension's main actionable groups (22 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.
139 duplicated block group(s) detected. 2.4 % of the production lines (5,137 of 214,039) are in a reported copy. A further 81 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 13 of the 220 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts (18% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 80 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 21 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with lib.rs (4), svg_builder.rs (4), machine_markdown.rs (3). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with module_group.rs, esm.rs, source_replacer.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with lib.rs (4), utilities.rs (2), analyze_module_graph.rs. — One of this dimension's main actionable groups (10 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.2 / 10Adequategated by 1 critical finding✓ 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.
372 production modules (Cargo+npm), 1 dependency cycle(s), 13 unstable depended-on module(s). Read from the build's own module declarations; 14 module(s) off the main sequence, with abstractness counted on 90 of the 372 (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).
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 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs (3), mod.rs (2), unique_idents.rs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1063 tests. Measured on the JavaScript/TypeScript suite only — at least 253 test source file(s) (.py, .rs) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: Binding - should parse config to rust correctly · ×2packages/core/tests/binding.spec.ts:13
Mock-dominated test: retains a retired route when its response finishes before the upstream request closespackages/core/tests/runtime-proxy-lifecycle.spec.ts:17
What to do
Resolve the 2 No assertions finding(s) in Test Quality — start with binding.spec.ts, index.spec.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Mock-dominated test finding(s) in Test Quality — start with runtime-proxy-lifecycle.spec.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
29 outdated, 0 yanked direct Cargo dependencies. 125 of 137 direct crates were graded against crates.io (0 not published there, 12 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×29
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.
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 941 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 8 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. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 23 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), incremental-release-entry.py, incremental-release-producer.mjs. — One of this dimension's main actionable groups (23 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects/test.rs. Counted over 554 of the 880 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
82 deducted task-comment markers across 214039 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 79 TodoComment finding(s) in Explicit Debt — start with mod.rs (13), lib.rs (9), REDACTED (7). — One of this dimension's main actionable groups (79 warning-level).
Resolve the 3 XxxComment finding(s) in Explicit Debt — start with REDACTED (2), unique_idents.rs. — One of this dimension's main actionable groups (3 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. 409 document(s) read across 303 unit(s).
Documentation: no build, run or usage example · ×224packages/core/npm/darwin-arm64/README.md:1
What to do
Resolve the 224 Documentation finding(s) in Documentation Quality — start with README.md (224). — One of this dimension's main actionable groups (224 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 47 declarations measured against a convention their peers follow.
`doImportCSSReplace` spells `CSS` where 14 names in the project spell it `Css`packages/core/src/utils/rebase-url.ts:182
`moduleID` spells `ID` where 31 names in the project spell it `Id`rust-plugins/react/src/is_react_refresh_boundary.ts:199
What to do
Resolve the 1 `doImportCSSReplace` spells `CSS` where 14 names in the project spell it… finding(s) in Naming Consistency — start with rebase-url.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `moduleID` spells `ID` where 31 names in the project spell it `Id` finding(s) in Naming Consistency — start with is_react_refresh_boundary.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×4packages/cli/src/utils.ts:86
What to do
Resolve the 65 redundant comment finding(s) in Comment Value — start with output.js (27), output.cjs.js (6), main.ts (6). — One of this dimension's main actionable groups (65 recommendation-level).
Detailed fixes: d24_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.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
344 finding(s): 0 critical, 314 high, 28 medium, 2 low. 277 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 54 file(s) — `.agents/skills/agent-browser/templates/authenticated-session.sh` (line 27), `.agents/skills/agent-browser/templates/capture-workflow.sh` (line 16), `.agents/skills/agent-browser/templates/form-automation.sh` (line 16), `.claude/skills/agent-browser/templates/authenticated-session.sh` (line 27), `.claude/skills/agent-browser/templates/capture-workflow.sh` (line 16), … (+49 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 17 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
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) charged to Static Analysis (SAST) — the other 277 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (281 issue-level, 4 of them charged here).
Resolve the 13 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (13 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).
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 99 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (98), REDACTED. — One of this dimension's main actionable groups (99 issue-level).
Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
106 of 554 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is patches/serde/src/private/de.rs. Counted over 554 of the 880 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 12 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs (3), impls.rs (2), de.rs. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 94 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (15), mod.rs (4), svg_builder.rs (2). — One of this dimension's main actionable groups (94 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with index.d.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
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. — 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 53 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives7.4 / 10Strong✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — website/src/components/ui/beam.tsx:122
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.5 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — crates/create-farm-rs/templates/electron/vanilla/src/main.ts:16, crates/create-farm-rs/templates/vanilla/src/main.ts:16
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×6) — crates/create-farm-rs/templates/tauri/preact/src/App.tsx:41, crates/create-farm-rs/templates/tauri/react/src/App.tsx:41, crates/create-farm-rs/templates/tauri/solid/src/App.tsx:41, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×7) — crates/create-farm-rs/templates/tauri/svelte/src/lib/Greet.svelte:15, crates/create-farm-rs/templates/tauri/vanilla/index.html:47, crates/create-farm-rs/templates/tauri/vue/src/components/Greet.vue:16, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — js-plugins/visualizer/src/client/src/pages/analysis/Compilation.vue:33, js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:4
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — .agents/skills/brainstorming/scripts/frame-template.html:2, .claude/skills/brainstorming/scripts/frame-template.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — .agents/skills/brainstorming/scripts/frame-template.html:2, .claude/skills/brainstorming/scripts/frame-template.html:2, crates/create-farm-rs/templates/lit/index.html:2, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
The repo's own CSS styles .card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — crates/create-farm-rs/templates/electron/svelte/src/App.svelte:18, crates/create-farm-rs/templates/svelte/src/App.svelte:18
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — js-plugins/visualizer/src/client/src/components/ModuleList.vue:8, js-plugins/visualizer/src/client/src/components/ResourcePots.vue:8
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — website/src/components/TeamMembersItem/index.tsx:9
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.option .letter` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:120, .claude/skills/brainstorming/scripts/frame-template.html:120
`.option.selected .letter` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:128, .claude/skills/brainstorming/scripts/frame-template.html:128
`.mockup-header` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:158, .claude/skills/brainstorming/scripts/frame-template.html:158
`.placeholder` sets color: #aeaeb2 on background-color: #e5e5e7 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:180, .claude/skills/brainstorming/scripts/frame-template.html:180
`.mock-nav` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:190, .claude/skills/brainstorming/scripts/frame-template.html:190
`.mock-button` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — .agents/skills/brainstorming/scripts/frame-template.html:193, .claude/skills/brainstorming/scripts/frame-template.html:193
`.window` sets color: #ccc on background-color: #ffffff — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/runtime-plugin-hmr/src/overlay.ts:42
`.farm-docs-navbar > .farm-docs-search-trigger` sets color: #b2acbd on background-color: #ebedf0 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/docs-theme-default/src/style.css:110
`.farm-docs-breadcrumbs > span:last-child` sets color: #d4a1e5 on background-color: #f5f5f6 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/docs-theme-default/src/style.css:180
`.jsx-card button` sets color: #fff on background-color: #40916c — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/vue/src/views/HomeView.vue:43
`&-draft, &-refunded` sets color: #8a7250 on background-color: #f2ede3 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/commerce-lab/apps/admin/styles/workspace.scss:40
`.farmButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — website/src/pages/index.module.css:55
`.farmButton2` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — website/src/pages/index.module.css:123
`.sp .sp-link.link:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — website/src/components/TeamMembersItem/index.module.css:122
`a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/vite-adapter-vue/src/style.css:19
`.card` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — examples/react-sass-js/src/components/card/index.css:3, examples/react/src/components/card/index.css:3, examples/public-path/src/components/card/index.css:3, …
`input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×12) — crates/create-farm-rs/templates/tauri2/vue/src/App.vue:133, crates/create-farm-rs/templates/tauri2/vanilla/src/styles.css:92, crates/create-farm-rs/templates/tauri2/svelte/src/routes/+page.svelte:129, …
`.farmButton:before` moves (`animation: glowing 120s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/pages/index.module.css:87
`.farmButton2:before` moves (`animation: glowing 100s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/pages/index.module.css:155
`#__docusaurus .menu__list` moves (`transition: height 0.35s cubic-bezier(0.36, 0.66, 0.04, 1) 25ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/css/_doc.siderbar.scss:98
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The projects @farmfe/docs-theme-default → @farmfe/docs → @farmfe/docs-theme-default form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/docs-theme-default/REDACTED:31
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
js-plugins/less/README.md names Less 3, but the manifest declares `less` ^4.1.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — js-plugins/less/README.md:155
js-plugins/postcss/README.md names Less 3, but the manifest declares `less` ^4.1.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — js-plugins/postcss/README.md:154
website/docs/features/css.md names TailwindCSS 3, but the manifest declares `tailwindcss` 4.1.12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — website/docs/features/css.md:213
website/docs/features/script.md names Vite 8, but the manifest declares `vite` ^5.2.6. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — website/docs/features/script.md:166
What to do
Reconcile the README with reality: js-plugins/less/README.md names Less 3, but the manifest declares `less` ^4.1.3; js-plugins/postcss/README.md names Less 3, but the manifest declares `less` ^4.1.3; website/docs/features/css.md names TailwindCSS 3, but the manifest declares `tailwindcss` 4.1.12; website/docs/features/script.md names Vite 8, but the manifest declares `vite` ^5.2.6.
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.
`cargo fmt` invokes cargo fmt in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:23
What to do
Add `--check` to the cargo fmt step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability4.7 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 6/25 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/create-farm-rs`, `crates/create-farm-rs/templates/tauri/preact/src-tauri`, `crates/create-farm-rs/templates/tauri/react/src-tauri`, `crates/create-farm-rs/templates/tauri/solid/src-tauri`, `crates/create-farm-rs/templates/tauri/svelte/src-tauri` and 14 more.
`js-plugins/dts/src/options.ts` reports through `console.*` at line 4 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — js-plugins/dts/src/options.ts:4
`js-plugins/dts/src/utils.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — js-plugins/dts/src/utils.ts:29
`js-plugins/dts/src/utils.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — js-plugins/dts/src/utils.ts:34
`js-plugins/dts/src/utils.ts` reports through `console.*` at line 80 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — js-plugins/dts/src/utils.ts:80
`js-plugins/dts/src/utils.ts` reports through `console.*` at line 366 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — js-plugins/dts/src/utils.ts:366
`packages/core/src/utils/share.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/utils/share.ts:66
`packages/core/src/utils/share.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/utils/share.ts:70
`packages/core/src/utils/share.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/utils/share.ts:105
`packages/core/src/server/preview.ts` reports through `console.*` at line 307 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/server/preview.ts:307
`packages/core/src/plugin/js/farm-to-vite-context.ts` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/plugin/js/farm-to-vite-context.ts:30
`packages/core/src/plugin/js/utils.ts` reports through `console.*` at line 314 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/plugin/js/utils.ts:314
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:34
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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::get(` 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. — rust-plugins/icons/src/cache/mod.rs:92
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 the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`existsSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — js-plugins/less/src/index.ts:73, js-plugins/sass/src/index.ts:85, packages/core/src/plugin/js/adapter-plugins/default-load.ts:31
`existsSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — js-plugins/sass/src/index.ts:197, js-plugins/sass/src/index.ts:204
`statSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — js-plugins/sass/src/index.ts:197, js-plugins/sass/src/index.ts:204
`fse.existsSync` in `readConfigFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/config/load-config-file.ts:162
`fse.rmSync` in `readConfigFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/config/load-config-file.ts:243
`fse.existsSync` in `checkCompilationInputValue` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/core/src/config/normalize-config/index.ts:205, packages/core/src/config/normalize-config/index.ts:218
`existsSync` in `normalizePersistentCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/config/normalize-config/normalize-persistent-cache.ts:87
`readFileSync` in `normalizePersistentCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/config/normalize-config/normalize-persistent-cache.ts:88
`readFileSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/plugin/js/adapter-plugins/default-load.ts:48
`fse.existsSync` in `prepareHmrUpdate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/server/hmr-engine.ts:312
`existsSync` in `callback to paths.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/server/middlewares/lazyCompilation.ts:39
`existsSync` in `#resolveOptions` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/server/preview.ts:229
`fs.readdirSync` in `isCacheDirExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/cacheDir.ts:5
`fs.existsSync` in `recursiveReaddir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/file.ts:80
`fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/plugin-utils.ts:29
`fs.existsSync` in `checkPublicFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/publicDir.ts:32
`fs.existsSync` in `traceDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/trace-dependencies.ts:21
`fs.statSync` in `traceDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/src/utils/trace-dependencies.ts:21
`execSync` in `prepublish` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/plugin-tools/src/prepublish.ts:29
`execSync` in `installDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:58
`fs.readdirSync` in `buildExamples` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:83
`existsSync` in `hasPrebuiltRustPluginArtifact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build.mjs:94, scripts/build.mjs:103
`fs.readdirSync` in `hasPrebuiltRustPluginArtifact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:98
`existsSync` in `resolveRustPluginsForExample` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build.mjs:119, scripts/build.mjs:140
`fs.readFileSync` in `resolveRustPluginsForExample` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:124
`existsSync` in `buildExamples` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — scripts/build.mjs:181, scripts/build.mjs:194, scripts/build.mjs:219
`fs.readFileSync` in `buildExamples` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build.mjs:182, scripts/build.mjs:231
`fs.statSync` in `buildExamples` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:230
`fs.readdirSync` in `buildJsPlugins` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:310
`fs.statSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build.mjs:312
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety10.0 / 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.7 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
9 duplicated blocks under crates/create-farm-rs/templates/ have copies in at least two of the sibling directories electron, preact, react, solid, tauri, tauri2 (+1 more sibling(s) not listed) — 6 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — crates/create-farm-rs/templates/tauri/react/src/App.tsx:7
8 of the duplicated blocks reported below have copies in at least two of the sibling directories preact, react, solid, svelte, vanilla, vue under crates/create-farm-rs/templates/electron/. 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. — crates/create-farm-rs/templates/electron/preact/electron/main.ts:5
6 duplicated blocks under js-plugins/ have copies in at least two of the sibling directories babel, dts, less, postcss, react-compiler, sass (+1 more sibling(s) not listed) — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — js-plugins/less/src/index.ts:39
5 duplicated blocks under the repository root have copies in at least two of the sibling directories js-plugins, packages, rust-plugins, scripts — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/create-farm-plugin/templates/rust/scripts/index.js:69
rust-plugins/dts/scripts/index.js:1 · rust-plugins/replace-dirname/scripts/index.js:1 · rust-plugins/svgr/scripts/index.js:1 · rust-plugins/vue-jsx/scripts/index.js:1 — these 4 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — rust-plugins/dts/scripts/index.js:1
packages/create-farm-plugin/templates/rust/scripts/index.js:69 · rust-plugins/auto-import/scripts/index.js:69 · rust-plugins/compress/scripts/index.js:69 · rust-plugins/dsv/scripts/index.js:69 · +17 more site(s) not listed — the 21 copies are spread across 21 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/create-farm-plugin/templates/rust/scripts/index.js:69
packages/docs-theme-default/src/index.tsx:42 · packages/docs-theme-default/src/search.tsx:9 — the two spans are one implementation copied and then locally edited — 517 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/docs-theme-default/src/index.tsx:42
crates/create-farm-rs/templates/tauri/preact/src/App.tsx:7 · crates/create-farm-rs/templates/tauri/react/src/App.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. — crates/create-farm-rs/templates/tauri/preact/src/App.tsx:7
js-plugins/less/src/index.ts:39 · js-plugins/sass/src/index.ts:56 — the two spans are one implementation copied and then locally edited — 254 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. — js-plugins/less/src/index.ts:39
packages/core/src/server/type.ts:9 · packages/runtime-plugin-hmr/src/types.ts:55 — the two spans are one implementation copied and then locally edited — 168 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/server/type.ts:9
crates/create-farm-rs/templates/tauri/react/src/App.tsx:7 · crates/create-farm-rs/templates/tauri2/react/src/App.tsx:6 — 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. — crates/create-farm-rs/templates/tauri/react/src/App.tsx:7
crates/create-farm-rs/templates/tauri/solid/src/App.tsx:7 · crates/create-farm-rs/templates/tauri2/solid/src/App.tsx:6 — 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. — crates/create-farm-rs/templates/tauri/solid/src/App.tsx:7
js-plugins/copy/farm.config.ts:4 · js-plugins/vuetify/farm.config.ts:4 · packages/create-farm-plugin/templates/js/farm.config.ts: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. — js-plugins/copy/farm.config.ts:4
packages/create-farm-plugin/templates/rust/scripts/index.js:6 · rust-plugins/auto-import/scripts/index.js:6 · rust-plugins/compress/scripts/index.js:6 · rust-plugins/dsv/scripts/index.js:6 · +17 more site(s) not listed — the 21 copies are spread across 21 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 21 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. — packages/create-farm-plugin/templates/rust/scripts/index.js:6
packages/core/src/types/ws.ts:148 · packages/core/src/types/ws.ts:184 · packages/core/src/types/ws.ts:219 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/src/types/ws.ts:148
crates/create-farm-rs/templates/electron/preact/electron/main.ts:5 · crates/create-farm-rs/templates/electron/react/electron/main.ts:5 · crates/create-farm-rs/templates/electron/solid/electron/main.ts:5 · crates/create-farm-rs/templates/electron/svelte/electron/main.ts:5 · +2 more site(s) not listed — the 6 copies are spread across 6 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 6 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. — crates/create-farm-rs/templates/electron/preact/electron/main.ts:5
scripts/build.mjs:323 · scripts/build.mjs:373 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/build.mjs:323
packages/core/src/server/index.ts:1122 · packages/core/src/server/preview.ts:332 — the two spans are one implementation copied and then locally edited — 189 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/server/index.ts:1122
crates/create-farm-rs/templates/electron/solid/src/App.tsx:6 · crates/create-farm-rs/templates/solid/src/App.tsx:6 — 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. — crates/create-farm-rs/templates/electron/solid/src/App.tsx:6
crates/create-farm-rs/templates/tauri2/preact/src/App.tsx:17 · crates/create-farm-rs/templates/tauri2/react/src/App.tsx:17 · crates/create-farm-rs/templates/tauri2/solid/src/App.tsx:17 — the 3 copies are spread across 3 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported. — crates/create-farm-rs/templates/tauri2/preact/src/App.tsx:17
packages/core/binding/resolve-binding.cjs:169 · packages/core/binding/resolve-binding.cjs:200 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/binding/resolve-binding.cjs:169
packages/create-farm-plugin/templates/js/playground/src/main.tsx:5 · packages/create-farm-plugin/templates/rust/playground/src/main.tsx:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/create-farm-plugin/templates/js/playground/src/main.tsx:5
crates/create-farm-rs/templates/electron/react/src/main.tsx:5 · crates/create-farm-rs/templates/react/src/main.tsx:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — crates/create-farm-rs/templates/electron/react/src/main.tsx:5
crates/create-farm-rs/templates/electron/preact/src/app.tsx:6 · crates/create-farm-rs/templates/preact/src/app.tsx:6 — 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. — crates/create-farm-rs/templates/electron/preact/src/app.tsx:6
js-plugins/visualizer/src/client/src/components/CodeDiff.vue:25 · js-plugins/visualizer/src/client/src/components/CodeViewer.vue:24 — 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. — js-plugins/visualizer/src/client/src/components/CodeDiff.vue:25
REDACTED:521 · REDACTED:580 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:521
packages/runtime-plugin-hmr/src/overlay.ts:703 · packages/runtime-plugin-hmr/src/overlay.ts:742 — the two spans are one implementation copied and then locally edited — 145 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime-plugin-hmr/src/overlay.ts:703
packages/core/src/plugin/js/apply-html-transform.ts:68 · packages/core/src/plugin/js/apply-html-transform.ts:104 — the two spans are one implementation copied and then locally edited — 132 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/plugin/js/apply-html-transform.ts:68
packages/core/src/server/error.ts:5 · packages/runtime-plugin-hmr/src/utils.ts:32 — 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. — packages/core/src/server/error.ts:5
crates/create-farm-rs/templates/tauri2/preact/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/solid/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/svelte/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/vue/farm.config.ts:5 — 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. — crates/create-farm-rs/templates/tauri2/preact/farm.config.ts:5
packages/core/src/types/ws.ts:257 · packages/core/src/types/ws.ts:278 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/src/types/ws.ts:257
crates/create-farm-rs/templates/electron/preact/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/react/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/solid/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/svelte/electron/preload.ts:4 · +2 more site(s) not listed — the 6 copies are spread across 6 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. — crates/create-farm-rs/templates/electron/preact/electron/preload.ts:4
crates/create-farm-rs/templates/electron/preact/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/react/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/solid/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/svelte/forge.config.cjs:13 · +2 more site(s) not listed — the 6 copies are spread across 6 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 6 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. — crates/create-farm-rs/templates/electron/preact/forge.config.cjs:13
crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 · crates/create-farm-rs/templates/electron/svelte/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 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. — crates/create-farm-rs/templates/electron/solid/farm.config.ts:3
crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 · crates/create-farm-rs/templates/electron/vue/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 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. — crates/create-farm-rs/templates/electron/solid/farm.config.ts:3
js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:112 · js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:131 — 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. — js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:112
packages/core/src/plugin/js/js-plugin-schema.ts:256 · packages/core/src/plugin/js/js-plugin-schema.ts:275 · packages/core/src/plugin/js/js-plugin-schema.ts:294 · packages/core/src/plugin/js/js-plugin-schema.ts:313 · +2 more site(s) not listed — all 6 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. — packages/core/src/plugin/js/js-plugin-schema.ts:256
packages/core/src/server/index.ts:443 · packages/core/src/watcher/index.ts:299 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/server/index.ts:443
crates/create-farm-rs/templates/electron/preact/farm.config.ts:3 · crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 52 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. — crates/create-farm-rs/templates/electron/preact/farm.config.ts:3
crates/create-farm-rs/templates/electron/preact/farm.config.ts:3 · crates/create-farm-rs/templates/electron/svelte/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 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. — crates/create-farm-rs/templates/electron/preact/farm.config.ts: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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
js-plugins/electron/src/index.ts:5 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — js-plugins/electron/src/index.ts:5
js-plugins/postcss/tests/cache.integration.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/core/src/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — js-plugins/postcss/tests/cache.integration.ts:8
js-plugins/postcss/tests/cache.integration.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../tailwindcss/src/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — js-plugins/postcss/tests/cache.integration.ts:13
js-plugins/visualizer/src/client/src/api/index.ts:2 imports @farmfe/core/binding/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — js-plugins/visualizer/src/client/src/api/index.ts:2
js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue:51 imports @farmfe/core/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue:51
js-plugins/visualizer/src/client/src/components/ModuleList.vue:32 imports @farmfe/core/binding/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — js-plugins/visualizer/src/client/src/components/ModuleList.vue:32
js-plugins/visualizer/src/client/src/components/ProcessRecord.vue:33 imports @farmfe/core/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — js-plugins/visualizer/src/client/src/components/ProcessRecord.vue:33
packages/cli/src/index.ts:1 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/cli/src/index.ts:1
packages/cli/src/utils.ts:4 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/cli/src/utils.ts:4
packages/cli/src/utils.ts:26 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/cli/src/utils.ts:26
scripts/performance-correctness-worker.mjs:5 reaches into another package with a relative path (../examples/commerce-lab/benchmark/business-correctness.mjs) — import the package by name instead. — scripts/performance-correctness-worker.mjs:5
scripts/performance-graph-worker.mjs:4 reaches into another package with a relative path (../examples/commerce-lab/benchmark/graph-summary.mjs) — import the package by name instead. — scripts/performance-graph-worker.mjs:4
REDACTED:11 reaches into another package with a relative path (../examples/commerce-lab/benchmark/statistics.mjs) — import the package by name instead. — REDACTED:11
REDACTED:12 reaches into another package with a relative path (../examples/commerce-lab/benchmark/extension-generator.mjs) — import the package by name instead. — REDACTED:12
REDACTED:14 reaches into another package with a relative path (../examples/commerce-lab/benchmark/business-correctness.mjs) — import the package by name instead. — REDACTED:14
REDACTED:15 reaches into another package with a relative path (../examples/commerce-lab/benchmark/scale-profiles.mjs) — import the package by name instead. — REDACTED:15
REDACTED:262 reaches into another package with a relative path (../examples/commerce-lab/benchmark/native-provenance.mjs) — import the package by name instead. — REDACTED:262
scripts/test-e2e-worker.mjs:15 reaches into another package with a relative path (../e2e/farm-runner.mjs) — import the package by name instead. — scripts/test-e2e-worker.mjs:15
scripts/test-e2e-worker.mjs:15 imports e2e/farm-runner.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e-worker.mjs:15
scripts/test-e2e-worker.mjs:21 reaches into another package with a relative path (../e2e/runner.mjs) — import the package by name instead. — scripts/test-e2e-worker.mjs:21
scripts/test-e2e-worker.mjs:21 imports e2e/runner.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e-worker.mjs:21
scripts/test-e2e-worker.mjs:22 reaches into another package with a relative path (../e2e/utils.mjs) — import the package by name instead. — scripts/test-e2e-worker.mjs:22
scripts/test-e2e-worker.mjs:22 imports e2e/utils.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e-worker.mjs:22
scripts/test-e2e-worker.mjs:23 reaches into another package with a relative path (../e2e/worker-finish.mjs) — import the package by name instead. — scripts/test-e2e-worker.mjs:23
scripts/test-e2e-worker.mjs:23 imports e2e/worker-finish.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e-worker.mjs:23
scripts/test-e2e.mjs:21 reaches into another package with a relative path (../e2e/runner.mjs) — import the package by name instead. — scripts/test-e2e.mjs:21
scripts/test-e2e.mjs:21 imports e2e/runner.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e.mjs:21
scripts/test-e2e.mjs:22 reaches into another package with a relative path (../e2e/process-cleanup.mjs) — import the package by name instead. — scripts/test-e2e.mjs:22
scripts/test-e2e.mjs:22 imports e2e/process-cleanup.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e.mjs:22
scripts/test-e2e.mjs:24 reaches into another package with a relative path (../e2e/worker-outcome.mjs) — import the package by name instead. — scripts/test-e2e.mjs:24
scripts/test-e2e.mjs:24 imports e2e/worker-outcome.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e.mjs:24
scripts/test-e2e.mjs:25 reaches into another package with a relative path (../e2e/utils.mjs) — import the package by name instead. — scripts/test-e2e.mjs:25
scripts/test-e2e.mjs:25 imports e2e/utils.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/test-e2e.mjs:25
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (21 rows); move the shared test helper into a source directory production code may depend on (8 rows); declare the workspace packages these files import in the importing package's own REDACTED dependencies (4 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
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.
main has cyclomatic complexity 64 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:221
discoverSuiteInventory has cyclomatic complexity 51 and cognitive complexity 91; 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. — scripts/ci-suite-inventory.mjs:48
resolveNativeBindingPath has cyclomatic complexity 47 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/binding/resolve-binding.cjs:3
main has cyclomatic complexity 45 and cognitive complexity 83; 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. — scripts/incremental-release-producer.mjs:373
verifyCandidateSeal has cyclomatic complexity 44 and cognitive complexity 80; 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. — scripts/verify-v2-candidate-seal.mjs:22
makePublicationManifest has cyclomatic complexity 43 and cognitive complexity 47; 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. — scripts/incremental-release-producer.mjs:287
validateSummary has cyclomatic complexity 42 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/performance-pr-reporter.mjs:24
normalizePersistentCache has cyclomatic complexity 39 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/config/normalize-config/normalize-persistent-cache.ts:21
classifyVersionDiff has cyclomatic complexity 39 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/changesets-version-only.mjs:151
validateReleaseSet has cyclomatic complexity 38 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-registry-consumer.mjs:24
viteConfigToFarmConfig has cyclomatic complexity 37 and cognitive complexity 83; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/plugin/js/farm-to-vite-config.ts:321
runDockerCargoBuild has cyclomatic complexity 37 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/v2-docker-cargo-cache.mjs:79
applyHotUpdates has cyclomatic complexity 34 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:231
signature has cyclomatic complexity 32 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/ci-attempt-producers.mjs:27
assertRegistryLock has cyclomatic complexity 31 and cognitive complexity 63; 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. — scripts/farm-docs-vercel-build.mjs:185
readSafeZip has cyclomatic complexity 31 and cognitive complexity 32; 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. — scripts/performance-cohorts.mjs:76
resolveVersionEvidence has cyclomatic complexity 30 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/changesets-version-runtime.mjs:58
materializeRegistry has cyclomatic complexity 29 and cognitive complexity 47; 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. — scripts/sdk-candidate-registry.mjs:42
docker has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/v2-docker-cargo-cache.test.mjs:16
preparePlatformPackages has cyclomatic complexity 25 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/plugin-tools/src/prepare.ts:5
captureProducts has cyclomatic complexity 25 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/ci-native-capture.mjs:51
sameArtifact has cyclomatic complexity 25 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/plugin-tools/src/copy-artifacts.ts:4
drainWatchUpdates has cyclomatic complexity 24 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/server/hmr-engine.ts:204
executor has cyclomatic complexity 23 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — js-plugins/copy/src/index.ts:133
buildPublishedDocs has cyclomatic complexity 23 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-vercel-build.mjs:260
runConsumer has cyclomatic complexity 23 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-registry-consumer.mjs:142
report has cyclomatic complexity 22 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/performance-pr-reporter.mjs:118
deploymentPlan has cyclomatic complexity 21 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-vercel-build.mjs:63
normalizeTargetEnv has cyclomatic complexity 21 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/config/normalize-config/normalize-output.ts:141
cargoManifest has cyclomatic complexity 21 and cognitive complexity 32; 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. — scripts/changesets-version-only.mjs:92
collectReleaseDiagnostics has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/v2-release-diagnostics.mjs:45
assertLockResolution has cyclomatic complexity 21 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-vercel-build.mjs:150
normalizeUserCompilationConfig has cyclomatic complexity 21 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/config/normalize-config/index.ts:43
changesetsPublication has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/v2-release-inventory.mjs:131
validateCollectedSuites has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/ci-suite-execution.mjs:175
cleanupStaleE2EProcesses has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — e2e/process-cleanup.mjs:278
normalizeRuntimeConfig has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/config/normalize-config/normalize-runtime.ts:20
installedPackages has cyclomatic complexity 20 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-registry-consumer.mjs:119
buildExamples has cyclomatic complexity 20 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/build.mjs:82
validateConsumer has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/farm-docs-registry-consumer.mjs:54
Do you agree with this assessment?
R3 · Large Files8.9 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/core/src/server/index.ts has 1124 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/server/index.ts:1
REDACTED has 874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/runtime-plugin-hmr/src/overlay.ts has 697 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime-plugin-hmr/src/overlay.ts:1
packages/core/src/types/ws.ts has 515 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/types/ws.ts:1
REDACTED has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/core/src/types/binding.ts has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/types/binding.ts:1
packages/core/src/plugin/js/js-plugin-schema.ts has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/plugin/js/js-plugin-schema.ts:1
packages/core/src/config/schema.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/config/schema.ts:1
packages/core/src/server/ws.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/server/ws.ts:1
packages/core/src/config/types.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/config/types.ts:1
packages/core/src/plugin/js/farm-to-vite-config.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/plugin/js/farm-to-vite-config.ts:1
js-plugins/tailwindcss/src/index.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js-plugins/tailwindcss/src/index.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage3.1 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
vitest.config.ts declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 182 unreached component module(s) can be tested as written, however the suite is authored: js-plugins/visualizer/src/client/src/pages/analysis/Compilation.vue, js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue, examples/rust-plugin-worker/src/index.tsx, examples/react-antd/src/antd-layout.tsx, examples/tailwind-next/src/App.tsx, examples/solid-ssr/src/main.tsx and 176 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each. — vitest.config.ts:1
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×39) — packages/core/src/types/ws.ts:1, js-plugins/sass/src/index.ts:1, packages/create-farm-plugin/index.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code7.9 / 10Strong✓ 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.
252 file(s) (~21272 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: scripts/farm-docs-config-alias.test.mjs imports '../packages/docs/dist/resolve-alias.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
3 file(s) (~91 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: examples/decorators/test.mjs imports './dist/main.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — examples/decorators
1 file(s) (~5 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — examples/docs-features
2 file(s) (~39 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — examples/env
6 file(s) (~70 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: examples/runtime-plugin/test.mjs imports './dist/index.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — examples/runtime-plugin
5 file(s) (~272 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: examples/script-entry/test.mjs imports './dist/esm/index.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — examples/script-entry
2 file(s) (~74 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — examples/server-proxy
6 file(s) (~82 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: examples/tree-shake-antd/src/index.tsx imports '../build/index', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — examples/tree-shake-antd
Unreachable from the 565 application, 396 tooling and 525 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (565 application, 396 tooling, 525 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 (×28) — examples/arcgis/e2e.mock.mjs, examples/arco-pro/src/components/MessageBox/index.tsx, examples/commerce-lab/benchmark/hmr-sampler.mjs, …
no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (examples/arco-pro/src/components/MessageBox/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 — examples/arco-pro/src/components/MessageBox/list.tsx
no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (js-plugins/visualizer/src/client/src/pages/analysis/Module.vue) — 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 — js-plugins/visualizer/src/client/src/components/ModuleList.vue
no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (examples/arco-pro/src/components/Chart/area-polar.tsx, examples/arco-pro/src/components/Chart/horizontal-interval.tsx, examples/arco-pro/src/components/Chart/multi-area-line.tsx and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — examples/arco-pro/src/components/Chart/customer-tooltip.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.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×13) — scripts/prepare-v2-stable-versions.mjs:63, scripts/prepare-v2-stable-versions.mjs:48, scripts/prepare-v2-stable-versions.mjs:49, …
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×7) — examples/rust-plugin-auto-import-react/auto_import.d.ts:18, examples/rust-plugin-auto-import-react/auto_import.d.ts:4, examples/rust-plugin-auto-import-vue/src/types/auto_import.d.ts:6, …
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×9)
Declared in crates/create-farm-rs/templates/nestjs/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in crates/create-farm-rs/templates/react/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in crates/create-farm-rs/templates/react/REDACTED but never imported anywhere in that package or its workspace members — while rust-plugins/react/src/is_react_refresh_boundary.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in crates/create-farm-rs/templates/solid/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in crates/create-farm-rs/templates/svelte/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in crates/create-farm-rs/templates/tauri/react/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in crates/create-farm-rs/templates/tauri/react/REDACTED but never imported anywhere in that package or its workspace members — while rust-plugins/react/src/is_react_refresh_boundary.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in crates/create-farm-rs/templates/tauri/solid/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in crates/create-farm-rs/templates/tauri/svelte/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports4.8 / 10Weak✓ Tool-verified
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.
packages/core/src/utils/index.ts → packages/core/src/utils/fsUtils.ts → packages/core/src/config/index.ts → packages/core/src/config/env.ts → packages/core/src/utils/index.ts (one verified cycle inside a mutually-dependent group of 37 files) — packages/core/src/utils/index.ts:5
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
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 commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are read from a Rust server this repository starts itself, and its production Rust starts none. What serves its HTTP is outside the Rust source, and only what this card names about it was assessed.
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.
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 configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — website/vercel.json:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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 · 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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`wasmHelper` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — rust-plugins/wasm/src/wasm_runtime.js:3
`create` holds an AbortSignal but calls `replace(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `replace(…, { signal })`. — packages/docs/src/development.ts:177
`resources` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/docs/src/page-loader-core.ts:109
`run` holds an AbortSignal but calls `fs.readFile(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fs.readFile(…, { signal })`. — packages/docs/src/workflow.ts:251
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
144/175 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.4 `!` null assertions per 1k TypeScript source lines — 49 assertion(s) across the 33905 source line(s) of the 280 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/core/src/server/index.ts (10), packages/core/src/server/preview.ts (8), rust-plugins/react/src/is_react_refresh_boundary.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 5 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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 29 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 2 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 — 54 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
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 34% of this repository's production lines — rust (116,655 lines), python (10,954 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> farm-fe@0.0.0 start / > pnpm --filter @farmfe/cli start / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 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.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 23 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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 52 value object(s); a Domain/Aggregates/ValueObjects layer
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X12 Unreachable branch — X12 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 34% of this repository's production lines — rust (116,655 lines), python (10,954 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — X17 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X18 Disposal-pattern correctness — X18 reached only 34% of this repository's production lines — rust (116,655 lines), python (10,954 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — X19 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — X23 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — X24 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 40% of this repository's production lines — rust (116,655 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×12
<input> without a programmatic label crates/create-farm-rs/templates/tauri/preact/src/App.tsx:41— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri/react/src/App.tsx:41— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri/solid/src/App.tsx:41— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri/svelte/src/lib/Greet.svelte:15— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri/vanilla/index.html:47— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri/vue/src/components/Greet.vue:16— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/preact/src/App.tsx:39— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/react/src/App.tsx:39— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/solid/src/App.tsx:39— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/svelte/src/routes/+page.svelte:31— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/vanilla/index.html:37— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label crates/create-farm-rs/templates/tauri2/vue/src/App.vue:32— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
Orphaned knowledge patches/serde/src/private/de.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/core/de/impls.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/core/de/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/core/ser/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge rust-ecosystem/tailwindcss/src/utilities.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/core/de/value.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/private/ser.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge rust-ecosystem/tailwindcss/src/theme.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge patches/serde/src/core/ser/impls.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge rust-plugins/vue/src/lib.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge rust-ecosystem/tailwindcss/src/variants.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge rust-ecosystem/svgr-rs/src/transform_svg_component/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
AC2 · Forms & labels· <select> without a programmatic label · ×3
<select> without a programmatic label js-plugins/visualizer/src/client/src/pages/analysis/Compilation.vue:33— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label js-plugins/visualizer/src/client/src/pages/analysis/Compilation.vue:75— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<select> without a programmatic label js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:4— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
REDACTED
REDACTED
REDACTED
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text crates/create-farm-rs/templates/electron/vanilla/src/main.ts:16— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text crates/create-farm-rs/templates/vanilla/src/main.ts:16— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<html> without a lang .agents/skills/brainstorming/scripts/frame-template.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .claude/skills/brainstorming/scripts/frame-template.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×2
Clickable element isn't keyboard-operable crates/create-farm-rs/templates/electron/svelte/src/App.svelte:18— The repo's own CSS styles .card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Clickable element isn't keyboard-operable crates/create-farm-rs/templates/svelte/src/App.svelte:18— The repo's own CSS styles .card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×2
Click handler on a non-interactive <div> js-plugins/visualizer/src/client/src/components/ModuleList.vue:8— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> js-plugins/visualizer/src/client/src/components/ResourcePots.vue:8— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Unlisted import '@sveltejs/vite-plugin-svelte' crates/create-farm-rs/templates/electron/solid/svelte.config.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@sveltejs/vite-plugin-svelte' crates/create-farm-rs/templates/electron/vanilla/svelte.config.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative website/src/components/ui/beam.tsx:122— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics· Click handler on a non-interactive <figure> · ×1
Click handler on a non-interactive <figure> website/src/components/TeamMembersItem/index.tsx:9— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Project dependency cycle packages/docs-theme-default/REDACTED:31— The projects @farmfe/docs-theme-default → @farmfe/docs → @farmfe/docs-theme-default form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
Unlisted import '@changesets/apply-release-plan' scripts/prepare-v2-stable-versions.mjs:63— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@changesets/config' scripts/prepare-v2-stable-versions.mjs:48— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@changesets/get-release-plan' scripts/prepare-v2-stable-versions.mjs:49— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@electron-forge/cli' scripts/v2-electron-download.test.mjs:12— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@manypkg/get-packages' scripts/prepare-v2-stable-versions.mjs:47— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'electron' scripts/v2-electron-download.test.mjs:88— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@babel/core' examples/commerce-lab/adapters/modular-ui.mjs:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@svgr/core' examples/commerce-lab/adapters/commerce-icons.mjs:27— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@svgr/plugin-jsx' examples/commerce-lab/adapters/commerce-icons.mjs:28— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'tailwindcss-animate' examples/vite-adapter-vue-css/tailwind.config.js:80— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-refresh' rust-plugins/react/src/is_react_refresh_boundary.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
TodoComment rust-plugins/svgr/src/react_compiler.rs:9— // TODO custom react component compiler — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment rust-plugins/react/src/react_refresh.rs:18— // TODO namespace window.$RefreshReg$ and window.$RefreshSig$ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment rust-plugins/dts/src/lib.rs:272— // 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 rust-plugins/dts/src/lib.rs:290— // TODO emit_file baseDir — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment rust-plugins/auto-import/src/parser/parse.rs:21— // 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 rust-ecosystem/tailwindcss/tests/variants.rs:314— // as its own at-rule; if unsupported, this test acts as a future 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 rust-ecosystem/svgr-rs/src/transform_svg_component/mod.rs:685— // TODO: custom templates — 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 patches/fervid_parser/src/attributes.rs:111— // TODO Should the span be narrower? (It can be narrowed with lo = lo + name.len() + 1 and hi = hi - 1) — 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 patches/fervid_parser/src/attributes.rs:476— // TODO Report an 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 patches/fervid_parser/src/lib.rs:29— // TODO When should it fail? What do we do with errors?.. — 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 patches/fervid_parser/src/lib.rs:349— // TODO Implement :slotted and ::v-slotted detection — 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 patches/fervid_parser/src/sfc.rs:119— // TODO 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 patches/fervid_parser/src/sfc.rs:211— // TODO Check for serious errors (because it may parse regardless) ??? — 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 patches/fervid_parser/src/template.rs:13— // TODO Errors in template — 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 patches/fervid_parser/src/template.rs:77— // TODO Add `tag_name_span` to `StartingTag` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:187— // TODO Do you want to do an elegant cleaning? — 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 packages/runtime-plugin-hmr/src/overlay.ts:576— // TODO Optimize hmr boundaries and return values to match vite hmr mode socket return values — 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 packages/core/src/index.ts:109— // TODO move to rust — 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 packages/core/src/utils/logger.ts:228— // TODO: impl ILogger — 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 packages/core/src/utils/plugin-utils.ts:65— // TODO add support for customResolver — 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 packages/core/src/server/middlewares/static.ts:51— // TODO FS.allow FS.deny server.fs.allow server.fs.deny — 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 packages/core/src/plugin/index.ts:290— // TODO The priority needs to be redefined. — 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 packages/core/src/plugin/js/farm-to-vite-config.ts:419— // TODO think about vite has two watch options `server.watch` | `build.watch` — 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 packages/core/src/plugin/js/farm-to-vite-context.ts:165— // TODO these 2 options are not supported in farm — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:392— // TODO support order, if a hook has order, it should be split into two plugins — 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.
+ 54 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×53
FunctionTooLong: farmfe_ecosystem_glob::compile::compile_body_with_context rust-ecosystem/glob/src/compile.rs:766— FunctionTooLong — farmfe_ecosystem_glob::compile::compile_body_with_context runs 517 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 417 over it, 5.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_docs_plan::prepare::prepare_inner rust-ecosystem/docs-plan/src/prepare.rs:259— FunctionTooLong — farmfe_docs_plan::prepare::prepare_inner runs 480 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 380 over it, 4.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: workflow.run packages/docs/src/workflow.ts:251— FunctionTooLong — run runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.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.
FunctionTooLong: farmfe_docs_config::validate::validate rust-ecosystem/docs-config/src/validate.rs:210— FunctionTooLong — farmfe_docs_config::validate::validate runs 348 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 248 over it, 3.48× 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: farmfe_ecosystem_glob::scan::scan rust-ecosystem/glob/src/scan.rs:142— FunctionTooLong — farmfe_ecosystem_glob::scan::scan runs 278 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 178 over it, 2.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_docs_content::preprocess::prepare rust-ecosystem/docs-content/src/preprocess.rs:36— FunctionTooLong — farmfe_docs_content::preprocess::prepare runs 237 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 137 over it, 2.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_docs_plan::script_pages::parse rust-ecosystem/docs-plan/src/script_pages.rs:170— FunctionTooLong — farmfe_docs_plan::script_pages::parse runs 214 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 114 over it, 2.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.
FunctionTooLong: farmfe_svgr_rs::transform_svg_component::variables::get_variables rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:42— FunctionTooLong — farmfe_svgr_rs::transform_svg_component::variables::get_variables runs 214 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 114 over it, 2.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.
FunctionTooLong: farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:217— FunctionTooLong — farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs runs 206 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 106 over it, 2.06× 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: resolve-binding.resolveNativeBindingPath packages/core/binding/resolve-binding.cjs:3— FunctionTooLong — resolveNativeBindingPath runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: proxy.proxyMiddleware REDACTED:28— FunctionTooLong — proxyMiddleware runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× 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: farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements crates/plugin_tree_shake/src/tree_shake_modules.rs:314— FunctionTooLong — farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements runs 183 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 83 over it, 1.83× 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: ssg-pool.renderPages packages/docs/src/ssg-pool.ts:31— FunctionTooLong — renderPages 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: farmfe_plugin_css::transform_css_to_script::transform_css_to_script_modules crates/plugin_css/src/transform_css_to_script.rs:37— FunctionTooLong — farmfe_plugin_css::transform_css_to_script::transform_css_to_script_modules runs 169 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 69 over it, 1.69× 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: farmfe_toolkit::script::concatenate_modules::strip_modules_asts crates/toolkit/src/script/concatenate_modules/mod.rs:239— FunctionTooLong — farmfe_toolkit::script::concatenate_modules::strip_modules_asts runs 165 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 65 over it, 1.65× 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: farmfe_ecosystem_glob::compile::parse_tokens rust-ecosystem/glob/src/compile.rs:1460— FunctionTooLong — farmfe_ecosystem_glob::compile::parse_tokens 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.
FunctionTooLong: farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl crates/plugin_mangle_exports/src/mangle_exports.rs:252— FunctionTooLong — farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl runs 160 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 60 over it, 1.60× 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: browser-runtime-core.BrowserRuntime packages/docs/src/browser-runtime-core.tsx:137— FunctionTooLong — BrowserRuntime runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_docs_snapshot::verify::verify_build rust-ecosystem/docs-snapshot/src/verify.rs:340— FunctionTooLong — farmfe_docs_snapshot::verify::verify_build runs 156 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 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.tailwindcss js-plugins/tailwindcss/src/index.ts:35— FunctionTooLong — tailwindcss runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps crates/compiler/src/update/diff_and_patch_module_graph.rs:268— FunctionTooLong — farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps runs 147 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 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_compiler::update::handle_update_modules::handle_update_modules crates/compiler/src/update/handle_update_modules.rs:109— FunctionTooLong — farmfe_compiler::update::handle_update_modules::handle_update_modules runs 141 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 41 over it, 1.41× 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: farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources crates/compiler/src/generate/render_resource_pots.rs:22— FunctionTooLong — farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources runs 139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: roadmap.TimelineCpm website/src/pages/roadmap.tsx:32— FunctionTooLong — TimelineCpm runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: machine-readable.validateMachineReadableResources packages/docs/src/machine-readable.ts:111— FunctionTooLong — validateMachineReadableResources runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Sync-over-async blocking js-plugins/less/src/index.ts:73— `existsSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking js-plugins/sass/src/index.ts:85— `existsSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking js-plugins/sass/src/index.ts:197— `existsSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking js-plugins/sass/src/index.ts:197— `statSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking js-plugins/sass/src/index.ts:204— `existsSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking js-plugins/sass/src/index.ts:204— `statSync` in `resolveDependency` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/load-config-file.ts:162— `fse.existsSync` in `readConfigFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/load-config-file.ts:243— `fse.rmSync` in `readConfigFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/normalize-config/index.ts:205— `fse.existsSync` in `checkCompilationInputValue` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/normalize-config/index.ts:218— `fse.existsSync` in `checkCompilationInputValue` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/normalize-config/normalize-persistent-cache.ts:87— `existsSync` in `normalizePersistentCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/config/normalize-config/normalize-persistent-cache.ts:88— `readFileSync` in `normalizePersistentCache` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/plugin/js/adapter-plugins/default-load.ts:31— `existsSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/plugin/js/adapter-plugins/default-load.ts:48— `readFileSync` in `executor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/server/hmr-engine.ts:312— `fse.existsSync` in `prepareHmrUpdate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/server/middlewares/lazyCompilation.ts:39— `existsSync` in `callback to paths.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/server/preview.ts:229— `existsSync` in `#resolveOptions` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/cacheDir.ts:5— `fs.readdirSync` in `isCacheDirExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/file.ts:80— `fs.existsSync` in `recursiveReaddir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/plugin-utils.ts:29— `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/publicDir.ts:32— `fs.existsSync` in `checkPublicFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/trace-dependencies.ts:21— `fs.existsSync` in `traceDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/src/utils/trace-dependencies.ts:21— `fs.statSync` in `traceDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/plugin-tools/src/prepublish.ts:29— `execSync` in `prepublish` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/build.mjs:58— `execSync` in `installDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×39
No test reaches this file packages/core/src/types/ws.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/sass/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-farm-plugin/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/copy/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/electron/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rust-plugins/react/src/is_react_refresh_boundary.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/plugin_lazy_compilation/src/dynamic_module.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/less/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rust-plugins/dts/scripts/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/lit/src/my-element.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/less/src/plugin-resolve.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/visualizer/src/client/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/core/src/server/error.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file examples/script-entry/test-cjs.cjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file examples/script-entry/test.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file examples/react/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/qiankun/src/qiankun-farm-plugin.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/preact/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/react/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/solid/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/svelte/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/vanilla/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/create-farm-rs/templates/electron/vue/electron/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file js-plugins/visualizer/src/client/src/http.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Boundary violation [package:undeclared-workspace-dep] js-plugins/electron/src/index.ts:5— js-plugins/electron/src/index.ts:5 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:test-cross-package-internals] js-plugins/postcss/tests/cache.integration.ts:8— js-plugins/postcss/tests/cache.integration.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/core/src/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] js-plugins/postcss/tests/cache.integration.ts:13— js-plugins/postcss/tests/cache.integration.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../tailwindcss/src/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:deep-import] js-plugins/visualizer/src/client/src/api/index.ts:2— js-plugins/visualizer/src/client/src/api/index.ts:2 imports @farmfe/core/binding/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue:51— js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue:51 imports @farmfe/core/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] js-plugins/visualizer/src/client/src/components/ModuleList.vue:32— js-plugins/visualizer/src/client/src/components/ModuleList.vue:32 imports @farmfe/core/binding/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] js-plugins/visualizer/src/client/src/components/ProcessRecord.vue:33— js-plugins/visualizer/src/client/src/components/ProcessRecord.vue:33 imports @farmfe/core/binding, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:undeclared-workspace-dep] packages/cli/src/index.ts:1— packages/cli/src/index.ts:1 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/cli/src/utils.ts:4— packages/cli/src/utils.ts:4 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/cli/src/utils.ts:26— packages/cli/src/utils.ts:26 imports @farmfe/core, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] scripts/performance-correctness-worker.mjs:5— scripts/performance-correctness-worker.mjs:5 reaches into another package with a relative path (../examples/commerce-lab/benchmark/business-correctness.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] scripts/performance-graph-worker.mjs:4— scripts/performance-graph-worker.mjs:4 reaches into another package with a relative path (../examples/commerce-lab/benchmark/graph-summary.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] REDACTED:11— REDACTED:11 reaches into another package with a relative path (../examples/commerce-lab/benchmark/statistics.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] REDACTED:12— REDACTED:12 reaches into another package with a relative path (../examples/commerce-lab/benchmark/extension-generator.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] REDACTED:14— REDACTED:14 reaches into another package with a relative path (../examples/commerce-lab/benchmark/business-correctness.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] REDACTED:15— REDACTED:15 reaches into another package with a relative path (../examples/commerce-lab/benchmark/scale-profiles.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] REDACTED:262— REDACTED:262 reaches into another package with a relative path (../examples/commerce-lab/benchmark/native-provenance.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] scripts/test-e2e-worker.mjs:15— scripts/test-e2e-worker.mjs:15 reaches into another package with a relative path (../e2e/farm-runner.mjs) — import the package by name instead.
Boundary violation [package:test-suite-dependency] scripts/test-e2e-worker.mjs:15— scripts/test-e2e-worker.mjs:15 imports e2e/farm-runner.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:relative-cross-package] scripts/test-e2e-worker.mjs:21— scripts/test-e2e-worker.mjs:21 reaches into another package with a relative path (../e2e/runner.mjs) — import the package by name instead.
Boundary violation [package:test-suite-dependency] scripts/test-e2e-worker.mjs:21— scripts/test-e2e-worker.mjs:21 imports e2e/runner.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:relative-cross-package] scripts/test-e2e-worker.mjs:22— scripts/test-e2e-worker.mjs:22 reaches into another package with a relative path (../e2e/utils.mjs) — import the package by name instead.
Boundary violation [package:test-suite-dependency] scripts/test-e2e-worker.mjs:22— scripts/test-e2e-worker.mjs:22 imports e2e/utils.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:relative-cross-package] scripts/test-e2e-worker.mjs:23— scripts/test-e2e-worker.mjs:23 reaches into another package with a relative path (../e2e/worker-finish.mjs) — import the package by name instead.
Boundary violation [package:test-suite-dependency] scripts/test-e2e-worker.mjs:23— scripts/test-e2e-worker.mjs:23 imports e2e/worker-finish.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
+ 8 more in this group — see findings.md.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×29
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/preact/REDACTED:12— crates/create-farm-rs/templates/electron/preact/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/react/REDACTED:12— crates/create-farm-rs/templates/electron/react/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/solid/REDACTED:12— crates/create-farm-rs/templates/electron/solid/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/svelte/REDACTED:12— crates/create-farm-rs/templates/electron/svelte/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/vanilla/REDACTED:12— crates/create-farm-rs/templates/electron/vanilla/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/electron/vue/REDACTED:12— crates/create-farm-rs/templates/electron/vue/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/lit/REDACTED:12— crates/create-farm-rs/templates/lit/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/nestjs/REDACTED:23— crates/create-farm-rs/templates/nestjs/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/preact/REDACTED:13— crates/create-farm-rs/templates/preact/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/react/REDACTED:11— crates/create-farm-rs/templates/react/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/solid/REDACTED:11— crates/create-farm-rs/templates/solid/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/svelte/REDACTED:13— crates/create-farm-rs/templates/svelte/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/preact/REDACTED:12— crates/create-farm-rs/templates/tauri/preact/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/react/REDACTED:11— crates/create-farm-rs/templates/tauri/react/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/solid/REDACTED:13— crates/create-farm-rs/templates/tauri/solid/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/svelte/REDACTED:13— crates/create-farm-rs/templates/tauri/svelte/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/vanilla/REDACTED:12— crates/create-farm-rs/templates/tauri/vanilla/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri/vue/REDACTED:12— crates/create-farm-rs/templates/tauri/vue/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/preact/REDACTED:12— crates/create-farm-rs/templates/tauri2/preact/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/react/REDACTED:12— crates/create-farm-rs/templates/tauri2/react/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/solid/REDACTED:14— crates/create-farm-rs/templates/tauri2/solid/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/svelte/REDACTED:15— crates/create-farm-rs/templates/tauri2/svelte/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/vanilla/REDACTED:12— crates/create-farm-rs/templates/tauri2/vanilla/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/tauri2/vue/REDACTED:12— crates/create-farm-rs/templates/tauri2/vue/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked crates/create-farm-rs/templates/vanilla/REDACTED:12— crates/create-farm-rs/templates/vanilla/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
MethodTooLong: FarmPluginDocs.finalize_resources rust-plugins/docs/src/lib.rs:705— MethodTooLong — finalize_resources runs 331 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 231 over it, 3.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UtilityRegistry.builtin rust-ecosystem/tailwindcss/src/utilities.rs:31— MethodTooLong — builtin runs 324 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 224 over it, 3.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SfcParser.try_parse_directive patches/fervid_parser/src/attributes.rs:72— MethodTooLong — try_parse_directive runs 307 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 207 over it, 3.07× 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: VueJsxTransformVisitor.resolve_indexed_access rust-plugins/vue-jsx/src/resolve_type.rs:641— MethodTooLong — resolve_indexed_access runs 278 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 178 over it, 2.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: VueJsxTransformVisitor.transform_attrs rust-plugins/vue-jsx/src/lib.rs:522— MethodTooLong — transform_attrs runs 260 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 160 over it, 2.60× 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: Index.resolve_inner rust-ecosystem/docs-plan/src/links.rs:201— MethodTooLong — resolve_inner runs 226 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 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FarmPluginRuntime.generate_resources crates/plugin_runtime/src/lib.rs:352— MethodTooLong — generate_resources runs 185 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 85 over it, 1.85× 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: ExportsVisitor.visit_module_decl rust-plugins/auto-import/src/parser/parse.rs:170— MethodTooLong — visit_module_decl runs 179 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 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.
MethodTooLong: VueJsxTransformVisitor.resolve_type_elements rust-plugins/vue-jsx/src/resolve_type.rs:369— MethodTooLong — resolve_type_elements runs 171 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 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Compiler.update_with_completion crates/compiler/src/update/mod.rs:398— MethodTooLong — update_with_completion runs 162 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ErrorOverlay.renderMessages packages/runtime-plugin-hmr/src/overlay.ts:611— MethodTooLong — renderMessages runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FarmPluginDocs.load rust-plugins/docs/src/lib.rs:528— MethodTooLong — load runs 143 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 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: VueJsxTransformVisitor.transform_children rust-plugins/vue-jsx/src/lib.rs:905— MethodTooLong — transform_children runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SideEffectsAnalyzer.visit_expr crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:434— MethodTooLong — visit_expr runs 134 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 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ImmutableModulesMemoryStore.write_cache_with_revisions crates/core/src/cache/module_cache/immutable_modules.rs:185— MethodTooLong — write_cache_with_revisions runs 125 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 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FarmPluginCss.transform crates/plugin_css/src/lib.rs:232— MethodTooLong — transform 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: FarmfePluginIcons.load rust-plugins/icons/src/lib.rs:125— MethodTooLong — load 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: Registry.resolve rust-ecosystem/docs-plan/src/assets.rs:96— MethodTooLong — resolve runs 117 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 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Compiler.build rust-ecosystem/tailwindcss/src/compiler.rs:163— MethodTooLong — build runs 115 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 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UtilityRegistry.generate_with_variants rust-ecosystem/tailwindcss/src/utilities.rs:499— MethodTooLong — generate_with_variants runs 114 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 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.
MethodTooLong: VueJsxTransformVisitor.extract_props_type rust-plugins/vue-jsx/src/resolve_type.rs:25— MethodTooLong — extract_props_type runs 114 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 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.
MethodTooLong: FarmPluginDocs.resolve rust-plugins/docs/src/lib.rs:381— MethodTooLong — resolve 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: VueJsxTransformVisitor.infer_runtime_type rust-plugins/vue-jsx/src/resolve_type.rs:994— MethodTooLong — infer_runtime_type 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: FarmPluginVue.compile_sfc rust-plugins/vue/src/lib.rs:124— MethodTooLong — compile_sfc 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: FarmPluginDocs.update_development rust-plugins/docs/src/development.rs:17— MethodTooLong — update_development runs 108 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 8 over it, 1.08× 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.
Hotspot: scripts/incremental-release-entry.py scripts/incremental-release-entry.py:295— scripts/incremental-release-entry.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in ReleaseVerifier.verify at line 295. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/incremental-release-entry.py`: 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: scripts/incremental-release-producer.mjs scripts/incremental-release-producer.mjs:373— scripts/incremental-release-producer.mjs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in incremental-release-producer.main at line 373. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/incremental-release-producer.mjs`: 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: scripts/incremental-release-publish.py scripts/incremental-release-publish.py:682— scripts/incremental-release-publish.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in incremental-release-publish.main at line 682. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/incremental-release-publish.py`: 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/plugin_mangle_exports/src/mangle_exports.rs crates/plugin_mangle_exports/src/mangle_exports.rs:252— crates/plugin_mangle_exports/src/mangle_exports.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl at line 252. 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 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/plugin_mangle_exports/src/mangle_exports.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/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:434— crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SideEffectsAnalyzer::visit_expr at line 434. 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 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.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: scripts/ci-impact-plan.py scripts/ci-impact-plan.py:225— scripts/ci-impact-plan.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in ci-impact-plan.plan_changes at line 225. 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 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/ci-impact-plan.py`: 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: scripts/build.mjs scripts/build.mjs:82— scripts/build.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in build.buildExamples at line 82. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/build.mjs`: 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/toolkit/src/script/concatenate_modules/mod.rs crates/toolkit/src/script/concatenate_modules/mod.rs:239— crates/toolkit/src/script/concatenate_modules/mod.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in farmfe_toolkit::script::concatenate_modules::strip_modules_asts at line 239. 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 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/toolkit/src/script/concatenate_modules/mod.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/toolkit/src/script/analyze_statement/statement_info.rs crates/toolkit/src/script/analyze_statement/statement_info.rs:32— crates/toolkit/src/script/analyze_statement/statement_info.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info at line 32. 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 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/toolkit/src/script/analyze_statement/statement_info.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: scripts/ci-native-evidence.py scripts/ci-native-evidence.py:36— scripts/ci-native-evidence.py changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in GitHubReadOnly.get at line 36. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/ci-native-evidence.py`: 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/compiler/src/update/handle_update_modules.rs crates/compiler/src/update/handle_update_modules.rs:109— crates/compiler/src/update/handle_update_modules.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in farmfe_compiler::update::handle_update_modules::handle_update_modules at line 109. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/compiler/src/update/handle_update_modules.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: scripts/sdk-candidate-registry.mjs scripts/sdk-candidate-registry.mjs:42— scripts/sdk-candidate-registry.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in sdk-candidate-registry.materializeRegistry at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/sdk-candidate-registry.mjs`: 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: scripts/farm-docs-vercel-build.mjs scripts/farm-docs-vercel-build.mjs:260— scripts/farm-docs-vercel-build.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in farm-docs-vercel-build.buildPublishedDocs at line 260. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/farm-docs-vercel-build.mjs`: 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: scripts/release-registry-selection.py scripts/release-registry-selection.py:381— scripts/release-registry-selection.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in release-registry-selection.presence_preparation at line 381. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/release-registry-selection.py`: 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: scripts/ci-execution-evidence.py scripts/ci-execution-evidence.py:176— scripts/ci-execution-evidence.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ci-execution-evidence.actual_producer at line 176. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/ci-execution-evidence.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/core/src/server/index.ts packages/core/src/server/index.ts:330— packages/core/src/server/index.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Server.#createWatcher at line 330. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- packages/core/src/server/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/cargo-source-release.py scripts/cargo-source-release.py:198— scripts/cargo-source-release.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in cargo-source-release.restore at line 198. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/cargo-source-release.py`: 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: scripts/run-sdk-consumer.mjs scripts/run-sdk-consumer.mjs:42— scripts/run-sdk-consumer.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in run-sdk-consumer.main at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/run-sdk-consumer.mjs`: 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: scripts/test-e2e.mjs scripts/test-e2e.mjs:248— scripts/test-e2e.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in test-e2e.main at line 248. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/test-e2e.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/core/src/server/middlewares/htmlFallback.ts packages/core/src/server/middlewares/htmlFallback.ts:9— packages/core/src/server/middlewares/htmlFallback.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in htmlFallback.htmlFallbackMiddleware.htmlFallbackMiddleware at line 9. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- packages/core/src/server/middlewares/htmlFallback.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/plugin_runtime/src/lib.rs crates/plugin_runtime/src/lib.rs:352— crates/plugin_runtime/src/lib.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in FarmPluginRuntime::generate_resources at line 352. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/plugin_runtime/src/lib.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/compiler/src/update/mod.rs crates/compiler/src/update/mod.rs:398— crates/compiler/src/update/mod.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Compiler::update_with_completion at line 398. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- crates/compiler/src/update/mod.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: scripts/ci-impact-summary.py scripts/ci-impact-summary.py:105— scripts/ci-impact-summary.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ci-impact-summary.main at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:53:20 +08:00' --until='2026-11-13 21:53:20 +08:00' --full-history --no-merges -- scripts/ci-impact-summary.py`: 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.
farmfe_ecosystem_tailwindcss::selector_parser::parse (cognitive 78) rust-ecosystem/tailwindcss/src/selector_parser.rs:90— farmfe_ecosystem_tailwindcss::selector_parser::parse has cognitive complexity 78 (threshold 15). Drivers by points: if/else 20 (61 pts), loops 5 (14 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators (cognitive 68) rust-ecosystem/tailwindcss/src/utils/math_operators.rs:41— farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators has cognitive complexity 68 (threshold 15). Drivers by points: if/else 25 (48 pts), boolean chains 16, loops 2 (4 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::attribute_selector_parser::parse (cognitive 54) rust-ecosystem/tailwindcss/src/attribute_selector_parser.rs:97— farmfe_ecosystem_tailwindcss::attribute_selector_parser::parse has cognitive complexity 54 (threshold 15). Drivers by points: if/else 22 (31 pts), boolean chains 10, loops 8 (10 pts), match/switch 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::compiler::apply_external_config_theme (cognitive 49) rust-ecosystem/tailwindcss/src/compiler.rs:629— farmfe_ecosystem_tailwindcss::compiler::apply_external_config_theme has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (33 pts), loops 4 (11 pts), match/switch 1 (5 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::candidate::parse_candidate (cognitive 40) rust-ecosystem/tailwindcss/src/candidate.rs:32— farmfe_ecosystem_tailwindcss::candidate::parse_candidate has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (33 pts), boolean chains 7 (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.
farmfe_ecosystem_tailwindcss::value_parser::parse (cognitive 37) rust-ecosystem/tailwindcss/src/value_parser.rs:73— farmfe_ecosystem_tailwindcss::value_parser::parse has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 3 (7 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::apply::process_nodes (cognitive 35) rust-ecosystem/tailwindcss/src/apply.rs:44— farmfe_ecosystem_tailwindcss::apply::process_nodes has cognitive complexity 35 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 4 (11 pts), match/switch 2 (7 pts), boolean chains 1 (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.
farmfe_ecosystem_tailwindcss::ast::optimize_ast (cognitive 32) rust-ecosystem/tailwindcss/src/ast.rs:234— farmfe_ecosystem_tailwindcss::ast::optimize_ast has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 15). 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.
farmfe_ecosystem_tailwindcss::compiler::scan_var_calls (cognitive 30) rust-ecosystem/tailwindcss/src/compiler.rs:477— farmfe_ecosystem_tailwindcss::compiler::scan_var_calls has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_ecosystem_tailwindcss::functions::replace_theme_functions (cognitive 30) rust-ecosystem/tailwindcss/src/functions.rs:25— farmfe_ecosystem_tailwindcss::functions::replace_theme_functions has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::utils::decode_arbitrary_value::recursively_decode_arbitrary_values (cognitive 26) rust-ecosystem/tailwindcss/src/utils/decode_arbitrary_value.rs:45— farmfe_ecosystem_tailwindcss::utils::decode_arbitrary_value::recursively_decode_arbitrary_values has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (2 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.
farmfe_ecosystem_tailwindcss::utils::segment::segment (cognitive 26) rust-ecosystem/tailwindcss/src/utils/segment.rs:23— farmfe_ecosystem_tailwindcss::utils::segment::segment has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::variants::resolve_functional (cognitive 25) rust-ecosystem/tailwindcss/src/variants.rs:508— farmfe_ecosystem_tailwindcss::variants::resolve_functional has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (25 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.
farmfe_ecosystem_tailwindcss::utils::escape::unescape (cognitive 23) rust-ecosystem/tailwindcss/src/utils/escape.rs:96— farmfe_ecosystem_tailwindcss::utils::escape::unescape has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::ast::stringify (cognitive 21) rust-ecosystem/tailwindcss/src/ast.rs:151— farmfe_ecosystem_tailwindcss::ast::stringify has cognitive complexity 21 (threshold 15). Drivers by points: loops 5 (12 pts), if/else 6 (8 pts), match/switch 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_sequence (cognitive 21) rust-ecosystem/tailwindcss/src/utils/brace_expansion.rs:126— farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_sequence has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::utils::compare::compare (cognitive 21) rust-ecosystem/tailwindcss/src/utils/compare.rs:14— farmfe_ecosystem_tailwindcss::utils::compare::compare has cognitive complexity 21 (threshold 15). Drivers by points: loops 3 (7 pts), match/switch 2 (7 pts), if/else 2 (4 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::utils::is_valid_arbitrary::is_valid_arbitrary (cognitive 20) rust-ecosystem/tailwindcss/src/utils/is_valid_arbitrary.rs:19— farmfe_ecosystem_tailwindcss::utils::is_valid_arbitrary::is_valid_arbitrary has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::candidate::normalize_arbitrary_value (cognitive 19) rust-ecosystem/tailwindcss/src/candidate.rs:378— farmfe_ecosystem_tailwindcss::candidate::normalize_arbitrary_value has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, loops 2 (4 pts), match/switch 1 (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.
farmfe_ecosystem_tailwindcss::utilities::resolve_spacing (cognitive 17) rust-ecosystem/tailwindcss/src/utilities.rs:761— farmfe_ecosystem_tailwindcss::utilities::resolve_spacing has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss::compiler::walk_features (cognitive 16) rust-ecosystem/tailwindcss/src/compiler.rs:743— farmfe_ecosystem_tailwindcss::compiler::walk_features has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 2 (5 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.
farmfe_ecosystem_tailwindcss::functions::closing_parenthesis (cognitive 16) rust-ecosystem/tailwindcss/src/functions.rs:84— farmfe_ecosystem_tailwindcss::functions::closing_parenthesis has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (3 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.
farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_inner (cognitive 16) rust-ecosystem/tailwindcss/src/utils/brace_expansion.rs:22— farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_inner has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 4 (5 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×23
FileTooLong: src/compile.rs rust-ecosystem/glob/src/compile.rs— FileTooLong — 1275 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 775 over it, 2.55× 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/lib.rs rust-plugins/vue-jsx/src/lib.rs— FileTooLong — 1174 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: VueJsxTransformVisitor (7 blocks, 42-1498). The bar is 500 significant lines; this is 674 over it, 2.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/utilities.rs rust-ecosystem/tailwindcss/src/utilities.rs— FileTooLong — 1147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 112 free functions. The bar is 500 significant lines; this is 647 over it, 2.29× 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/resolve_type.rs rust-plugins/vue-jsx/src/resolve_type.rs— FileTooLong — 961 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: VueJsxTransformVisitor (21-1247). The bar is 500 significant lines; this is 461 over it, 1.92× 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/lib.rs rust-plugins/docs/src/lib.rs— FileTooLong — 868 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: FarmPluginDocs (3 blocks, 106-1113). The bar is 500 significant lines; this is 368 over it, 1.74× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: server/index.ts packages/core/src/server/index.ts— FileTooLong — 787 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: Server (131-1236). The bar is 500 significant lines; this is 287 over it, 1.57× 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/lib.rs crates/swc_transformer_import_glob/src/lib.rs— FileTooLong — 781 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 281 over it, 1.56× 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: script/module2cjs.rs crates/toolkit/src/script/module2cjs.rs— FileTooLong — 764 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 264 over it, 1.53× 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: plugin/plugin_driver.rs crates/core/src/plugin/plugin_driver.rs— FileTooLong — 708 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: PluginDriver (2 blocks, 27-929). The bar is 500 significant lines; this is 208 over it, 1.42× 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/prepare.rs rust-ecosystem/docs-plan/src/prepare.rs— FileTooLong — 670 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 170 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: VitePluginAdapter (100-976). The bar is 500 significant lines; this is 164 over it, 1.33× 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/workflow.ts packages/docs/src/workflow.ts— FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: run (251-756). The bar is 500 significant lines; this is 109 over it, 1.22× 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: update/mod.rs crates/compiler/src/update/mod.rs— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: Compiler (306-995). The bar is 500 significant lines; this is 106 over it, 1.21× 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/resolver.rs crates/plugin_resolve/src/resolver.rs— FileTooLong — 591 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: Resolver (3 blocks, 52-864). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: concatenate_modules/handle_external_modules.rs crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs— FileTooLong — 588 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 88 over it, 1.18× 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/overlay.ts packages/runtime-plugin-hmr/src/overlay.ts— FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 84 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/machine_markdown.rs rust-ecosystem/docs-content/src/machine_markdown.rs— FileTooLong — 584 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 84 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/plugin_script/src/lib.rs— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: FarmPluginScript (3 blocks, 76-702). The bar is 500 significant lines; this is 68 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/plugin_css/src/lib.rs— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: FarmPluginCss (3 blocks, 169-738). The bar is 500 significant lines; this is 62 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: plugin_exports/expand_exports.rs crates/plugin_script_meta/src/plugin_exports/expand_exports.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: src/types.rs rust-ecosystem/docs-config/src/types.rs— FileTooLong — 531 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 31 over it, 1.06× 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/lib.rs rust-plugins/vue/src/lib.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), about 72% of them inside a single declaration: FarmPluginVue (3 blocks, 67-689). The bar is 500 significant lines; this is 3 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (6 lines × 2) crates/core/src/module/module_graph.rs:689— crates/core/src/module/module_graph.rs:689-694 | crates/core/src/module/module_group.rs:139-144 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `entry` to `&ModuleId` in one and `&ModuleGroupId` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) crates/core/src/module/module_graph.rs:697— crates/core/src/module/module_graph.rs:697-702 | crates/core/src/module/module_group.rs:155-160 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `entry` to `&ModuleId` in one and `&ModuleGroupId` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) crates/plugin_runtime/src/import_meta_visitor.rs:78— crates/plugin_runtime/src/import_meta_visitor.rs:78-83 | crates/plugin_tree_shake/src/remove_hot_update.rs:29-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/toolkit/src/script/concatenate_modules/unique_idents.rs:221— crates/toolkit/src/script/concatenate_modules/unique_idents.rs:221-226 | crates/toolkit/src/script/concatenate_modules/unique_idents.rs:239-244 — 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/toolkit/src/script/concatenate_modules/unique_idents.rs:221` 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) rust-ecosystem/docs-content/src/machine_markdown.rs:296— rust-ecosystem/docs-content/src/machine_markdown.rs:296-301 | rust-plugins/docs-snippets/src/transform/values.rs:74-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-content/src/machine_markdown.rs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/docs-content/src/machine_markdown.rs:760— rust-ecosystem/docs-content/src/machine_markdown.rs:760-765 | rust-plugins/vue/src/list_blocks.rs:23-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-content/src/machine_markdown.rs:760` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-plugins/auto-import/src/parser/scan_dirs_exports.rs:42— rust-plugins/auto-import/src/parser/scan_dirs_exports.rs:42-47 | rust-plugins/react-components/src/find_local_components.rs:364-369 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/auto-import/src/parser/scan_dirs_exports.rs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-plugins/image/src/lib.rs:46— rust-plugins/image/src/lib.rs:46-51 | rust-plugins/react-components/src/lib.rs:157-162 — 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. 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 (6 lines × 2) rust-plugins/vue-jsx/src/lib.rs:1058— rust-plugins/vue-jsx/src/lib.rs:1058-1063 | rust-plugins/vue-jsx/src/lib.rs:1130-1135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/lib.rs:1058` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/docs-content/src/machine_markdown.rs:270— rust-ecosystem/docs-content/src/machine_markdown.rs:270-275 | rust-plugins/docs-snippets/src/transform/values.rs:47-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-content/src/machine_markdown.rs:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/syntax-highlight/src/theme_config.rs:130— rust-ecosystem/syntax-highlight/src/theme_config.rs:130-135 | rust-ecosystem/syntax-highlight/src/theme_config.rs:184-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/syntax-highlight/src/theme_config.rs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-plugins/auto-import/src/lib.rs:44— rust-plugins/auto-import/src/lib.rs:44-49 | rust-plugins/react-components/src/lib.rs:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:33— rust-plugins/icons/src/loader/svg_builder.rs:33-38 | rust-plugins/svgr/src/svg_builder.rs:46-51 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:50— rust-plugins/icons/src/loader/svg_builder.rs:50-55 | rust-plugins/svgr/src/svg_builder.rs:63-68 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:57— rust-plugins/icons/src/loader/svg_builder.rs:57-62 | rust-plugins/svgr/src/svg_builder.rs:70-75 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:74— rust-plugins/icons/src/loader/svg_builder.rs:74-79 | rust-plugins/svgr/src/svg_builder.rs:87-92 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) rust-plugins/docs/src/lib.rs:632— rust-plugins/docs/src/lib.rs:632-641 | rust-plugins/docs/src/lib.rs:658-663 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/docs/src/lib.rs:632` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/docs-config/src/types.rs:89— rust-ecosystem/docs-config/src/types.rs:89-94 | rust-ecosystem/docs-config/src/types.rs:355-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-config/src/types.rs:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/syntax-highlight/src/editor_theme.rs:52— rust-ecosystem/syntax-highlight/src/editor_theme.rs:52-57 | rust-ecosystem/syntax-highlight/src/farm_theme.rs:55-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/syntax-highlight/src/editor_theme.rs:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) rust-ecosystem/tailwindcss/src/utilities.rs:1264— rust-ecosystem/tailwindcss/src/utilities.rs:1264-1269 | rust-ecosystem/tailwindcss/src/utilities.rs:1295-1300 — 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) scripts/release-npm-best-effort.py:237— scripts/release-npm-best-effort.py:237-242 | scripts/release-npm-version-presence.py:163-168 — 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. 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×20
Focus outline removed in CSS without a :focus replacement website/src/pages/index.module.css:55— `.farmButton` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement website/src/pages/index.module.css:123— `.farmButton2` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement website/src/components/TeamMembersItem/index.module.css:122— `.sp .sp-link.link:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/vite-adapter-vue/src/style.css:19— `a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/react-sass-js/src/components/card/index.css:3— `.card` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/react/src/components/card/index.css:3— `.card` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/public-path/src/components/card/index.css:3— `.card` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/less/src/components/card/index.less:3— `.card` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/vue/src/App.vue:133— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/vanilla/src/styles.css:92— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/svelte/src/routes/+page.svelte:129— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/solid/src/App.css:92— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/react/src/App.css:92— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/preact/src/App.css:92— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/vue/src/styles.css:84— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/vanilla/src/styles.css:84— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/svelte/src/styles.css:84— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/solid/src/styles.css:84— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/react/src/styles.css:80— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/preact/src/styles.css:84— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×18
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×17
farmfe_docs_content::preprocess::prepare (cognitive 115) rust-ecosystem/docs-content/src/preprocess.rs:36— farmfe_docs_content::preprocess::prepare has cognitive complexity 115 (threshold 15). Drivers by points: if/else 35 (87 pts), boolean chains 16, loops 5 (8 pts), match/switch 1 (4 pts) (nesting depth added 58). Of this number, 106 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_docs_content::code_blocks::apply::rewrite (cognitive 38) rust-ecosystem/docs-content/src/code_blocks.rs:278— farmfe_docs_content::code_blocks::apply::rewrite has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (29 pts), loops 3 (9 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_docs_content::headings::visit (cognitive 36) rust-ecosystem/docs-content/src/headings.rs:34— farmfe_docs_content::headings::visit has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_docs_content::references::collect::visit (cognitive 36) rust-ecosystem/docs-content/src/references.rs:144— farmfe_docs_content::references::collect::visit has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (26 pts), loops 3 (8 pts), match/switch 1 (2 pts) (nesting depth added 25). 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. This shape REPEATS in the file: one other method here (farmfe_docs_content::references::rewrite) 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.
farmfe_docs_content::references::rewrite (cognitive 36) rust-ecosystem/docs-content/src/references.rs:179— farmfe_docs_content::references::rewrite has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (26 pts), loops 3 (8 pts), match/switch 1 (2 pts) (nesting depth added 25). 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. This shape REPEATS in the file: one other method here (farmfe_docs_content::references::collect::visit) 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.
farmfe_docs_content::machine_markdown::highlighted_inline_text (cognitive 33) rust-ecosystem/docs-content/src/machine_markdown.rs:69— farmfe_docs_content::machine_markdown::highlighted_inline_text has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 5, loops 3 (5 pts), match/switch 1 (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.
farmfe_docs_content::code_blocks::inline_code (cognitive 30) rust-ecosystem/docs-content/src/code_blocks.rs:154— farmfe_docs_content::code_blocks::inline_code has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 4 (6 pts), loops 1 (2 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.
farmfe_docs_content::code_blocks::decode_title (cognitive 27) rust-ecosystem/docs-content/src/code_blocks.rs:46— farmfe_docs_content::code_blocks::decode_title has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 1 (5 pts), boolean chains 1, loops 1 (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.
farmfe_docs_content::jsx_attributes::preserve (cognitive 26) rust-ecosystem/docs-content/src/jsx_attributes.rs:15— farmfe_docs_content::jsx_attributes::preserve has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). Of this number, 16 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::machine_markdown::export (cognitive 26) rust-ecosystem/docs-content/src/machine_markdown.rs:743— farmfe_docs_content::machine_markdown::export has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 1 (5 pts), loops 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::machine_markdown::static_commands (cognitive 23) rust-ecosystem/docs-content/src/machine_markdown.rs:376— farmfe_docs_content::machine_markdown::static_commands has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::code_blocks::metadata (cognitive 20) rust-ecosystem/docs-content/src/code_blocks.rs:85— farmfe_docs_content::code_blocks::metadata has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::markdown_html::style (cognitive 19) rust-ecosystem/docs-content/src/markdown_html.rs:144— farmfe_docs_content::markdown_html::style has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::machine_markdown::static_codeblock (cognitive 18) rust-ecosystem/docs-content/src/machine_markdown.rs:315— farmfe_docs_content::machine_markdown::static_codeblock has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_content::markdown_html::convert (cognitive 18) rust-ecosystem/docs-content/src/markdown_html.rs:205— farmfe_docs_content::markdown_html::convert has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
farmfe_docs_content::preprocess::wrap_admonitions (cognitive 18) rust-ecosystem/docs-content/src/preprocess.rs:407— farmfe_docs_content::preprocess::wrap_admonitions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements (cognitive 78) crates/toolkit/src/script/concatenate_modules/strip_module_decl.rs:255— farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements has cognitive complexity 78 (threshold 15). Drivers by points: if/else 13 (42 pts), match/switch 4 (21 pts), loops 4 (15 pts) (nesting depth added 57). 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.
farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info (cognitive 55) crates/toolkit/src/script/analyze_statement/statement_info.rs:32— farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info has cognitive complexity 55 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 8 (22 pts), loops 3 (10 pts) (nesting depth added 37). 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.
farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all (cognitive 43) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:596— farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3 (12 pts), boolean chains 6 (nesting depth added 22). 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.
farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_import_statements (cognitive 42) crates/toolkit/src/script/concatenate_modules/strip_module_decl.rs:118— farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_import_statements has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (30 pts), loops 3 (7 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::concatenate_modules::strip_modules_asts (cognitive 35) crates/toolkit/src/script/concatenate_modules/mod.rs:239— farmfe_toolkit::script::concatenate_modules::strip_modules_asts has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 6 (9 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::transform_to_esm::update_module_graph_edges_of_cjs_modules (cognitive 33) crates/toolkit/src/script/transform_to_esm/mod.rs:111— farmfe_toolkit::script::transform_to_esm::update_module_graph_edges_of_cjs_modules has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::entry_live_bindings::resolve_origin::resolve (cognitive 28) crates/toolkit/src/script/entry_live_bindings.rs:412— farmfe_toolkit::script::entry_live_bindings::resolve_origin::resolve has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (11 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::module2cjs::transform_export_named (cognitive 28) crates/toolkit/src/script/module2cjs.rs:578— farmfe_toolkit::script::module2cjs::transform_export_named has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::sourcemap::collapse_sourcemap_chain (cognitive 28) crates/toolkit/src/sourcemap.rs:305— farmfe_toolkit::sourcemap::collapse_sourcemap_chain has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (4 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.
farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_external_import (cognitive 27) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:92— farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_external_import has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (4 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::sourcemap::trace_module_sourcemap (cognitive 20) crates/toolkit/src/sourcemap.rs:114— farmfe_toolkit::sourcemap::trace_module_sourcemap has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (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.
farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_external_export (cognitive 19) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:413— farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_external_export has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::fs::normalize_file_name_as_variable (cognitive 18) crates/toolkit/src/fs.rs:104— farmfe_toolkit::fs::normalize_file_name_as_variable has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::module2cjs::transform_module_decls (cognitive 17) crates/toolkit/src/script/module2cjs.rs:278— farmfe_toolkit::script::module2cjs::transform_module_decls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 3 (6 pts), match/switch 2 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::script::merge_swc_globals::merge_sourcemap_and_comments (cognitive 16) crates/toolkit/src/script/merge_swc_globals.rs:70— farmfe_toolkit::script::merge_swc_globals::merge_sourcemap_and_comments has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 pts) (nesting depth added 10). 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.
farmfe_toolkit::script::module2cjs::transform_import_decl (cognitive 16) crates/toolkit/src/script/module2cjs.rs:397— farmfe_toolkit::script::module2cjs::transform_import_decl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps (cognitive 79) crates/compiler/src/update/diff_and_patch_module_graph.rs:268— farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps has cognitive complexity 79 (threshold 15). Drivers by points: if/else 24 (54 pts), loops 10 (22 pts), boolean chains 3 (nesting depth added 42). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources (cognitive 76) crates/compiler/src/generate/render_resource_pots.rs:22— farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources has cognitive complexity 76 (threshold 15). Drivers by points: if/else 25 (55 pts), loops 9 (20 pts), boolean chains 1 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::patch_module_group_graph::patch_removed_dynamic_import_and_dynamic_entry (cognitive 44) crates/compiler/src/update/patch_module_group_graph.rs:298— farmfe_compiler::update::patch_module_group_graph::patch_removed_dynamic_import_and_dynamic_entry has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 25). 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.
farmfe_compiler::update::handle_update_modules::handle_update_modules (cognitive 40) crates/compiler/src/update/handle_update_modules.rs:109— farmfe_compiler::update::handle_update_modules::handle_update_modules has cognitive complexity 40 (threshold 15). Drivers by points: if/else 18 (28 pts), loops 5 (10 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::patch_module_group_graph::patch_any_module_group_for_toposort_modules (cognitive 35) crates/compiler/src/update/patch_module_group_graph.rs:608— farmfe_compiler::update::patch_module_group_graph::patch_any_module_group_for_toposort_modules has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (25 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 24). 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.
farmfe_compiler::update::patch_module_group_graph::patch_module_group_graph (cognitive 34) crates/compiler/src/update/patch_module_group_graph.rs:16— farmfe_compiler::update::patch_module_group_graph::patch_module_group_graph has cognitive complexity 34 (threshold 15). Drivers by points: loops 9 (18 pts), if/else 5 (15 pts), boolean chains 1 (nesting depth added 19). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
farmfe_compiler::update::patch_module_group_graph::patch_existing_added_non_dynamic_children (cognitive 34) crates/compiler/src/update/patch_module_group_graph.rs:412— farmfe_compiler::update::patch_module_group_graph::patch_existing_added_non_dynamic_children has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::handle_enforce_resource_pots (cognitive 27) crates/compiler/src/update/regenerate_resources/generate_and_diff_resource_pots.rs:163— farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::handle_enforce_resource_pots has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::diff_and_patch_module_graph::patch_module_graph (cognitive 26) crates/compiler/src/update/diff_and_patch_module_graph.rs:122— farmfe_compiler::update::diff_and_patch_module_graph::patch_module_graph has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 7 (9 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.
farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::diff_and_patch_resource_pot_map (cognitive 26) crates/compiler/src/update/regenerate_resources/generate_and_diff_resource_pots.rs:317— farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::diff_and_patch_resource_pot_map has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (11 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::build::resolve_module (cognitive 17) crates/compiler/src/build/mod.rs:682— farmfe_compiler::build::resolve_module has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::generate::partial_bundling::generate_enforce_resource_pots (cognitive 17) crates/compiler/src/generate/partial_bundling.rs:201— farmfe_compiler::generate::partial_bundling::generate_enforce_resource_pots has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::build::module_cache::try_get_module_cache_by_timestamp (cognitive 16) crates/compiler/src/build/module_cache.rs:237— farmfe_compiler::build::module_cache::try_get_module_cache_by_timestamp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (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.
farmfe_compiler::update::regenerate_resources::regenerate_resources_for_affected_module_groups (cognitive 16) crates/compiler/src/update/regenerate_resources/mod.rs:147— farmfe_compiler::update::regenerate_resources::regenerate_resources_for_affected_module_groups has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 6). 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.
Off the main sequence: @farmfe/runtime-plugin-import-meta — @farmfe/runtime-plugin-import-meta: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @farmfe/utils — @farmfe/utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: farmfe_ecosystem_tailwindcss — farmfe_ecosystem_tailwindcss: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: farmfe_svgr_rs — farmfe_svgr_rs: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: farmfe_utils — farmfe_utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: fervid_parser — fervid_parser: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: farmfe_toolkit_plugin_types — farmfe_toolkit_plugin_types: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: farmfe_testing_helpers — farmfe_testing_helpers: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: farmfe_toolkit — farmfe_toolkit: abstractness 0.02, instability 0.07, distance 0.91 — zone of pain — concrete and depended on by 40 project(s), so it's rigid to change.
Off the main sequence: @farmfe/runtime-plugin-hmr — @farmfe/runtime-plugin-hmr: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: create-farm (Cargo) — create-farm (Cargo): abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: farmfe_core — farmfe_core: abstractness 0.06, instability 0.07, distance 0.87 — zone of pain — concrete and depended on by 54 project(s), so it's rigid to change.
Off the main sequence: farmfe_syntax_highlight — farmfe_syntax_highlight: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: farmfe_docs_config — farmfe_docs_config: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
farmfe_ecosystem_tailwindcss::attribute_selector_parser::parse (cyclomatic 44) rust-ecosystem/tailwindcss/src/attribute_selector_parser.rs:97— farmfe_ecosystem_tailwindcss::attribute_selector_parser::parse has cyclomatic complexity 44 (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.
farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators (cyclomatic 37) rust-ecosystem/tailwindcss/src/utils/math_operators.rs:41— farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_ecosystem_tailwindcss::selector_parser::parse (cyclomatic 33) rust-ecosystem/tailwindcss/src/selector_parser.rs:90— farmfe_ecosystem_tailwindcss::selector_parser::parse 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.
farmfe_ecosystem_tailwindcss::candidate::parse_candidate (cyclomatic 26) rust-ecosystem/tailwindcss/src/candidate.rs:32— farmfe_ecosystem_tailwindcss::candidate::parse_candidate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_ecosystem_tailwindcss::value_parser::parse (cyclomatic 19) rust-ecosystem/tailwindcss/src/value_parser.rs:73— farmfe_ecosystem_tailwindcss::value_parser::parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_ecosystem_tailwindcss::apply::process_nodes (cyclomatic 17) rust-ecosystem/tailwindcss/src/apply.rs:44— farmfe_ecosystem_tailwindcss::apply::process_nodes has cyclomatic complexity 17 (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.
farmfe_ecosystem_tailwindcss::ast::optimize_ast (cyclomatic 17) rust-ecosystem/tailwindcss/src/ast.rs:234— farmfe_ecosystem_tailwindcss::ast::optimize_ast 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.
farmfe_ecosystem_tailwindcss::compiler::apply_external_config_theme (cyclomatic 17) rust-ecosystem/tailwindcss/src/compiler.rs:629— farmfe_ecosystem_tailwindcss::compiler::apply_external_config_theme 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.
farmfe_ecosystem_tailwindcss::functions::replace_theme_functions (cyclomatic 17) rust-ecosystem/tailwindcss/src/functions.rs:25— farmfe_ecosystem_tailwindcss::functions::replace_theme_functions 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.
farmfe_ecosystem_tailwindcss::variants::resolve_functional (cyclomatic 17) rust-ecosystem/tailwindcss/src/variants.rs:508— farmfe_ecosystem_tailwindcss::variants::resolve_functional 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: farmfe_ecosystem_tailwindcss::variants::resolve_named (cyclomatic 48) 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.
farmfe_ecosystem_tailwindcss::utilities::resolve_spacing (cyclomatic 16) rust-ecosystem/tailwindcss/src/utilities.rs:761— farmfe_ecosystem_tailwindcss::utilities::resolve_spacing 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.
farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_sequence (cyclomatic 16) rust-ecosystem/tailwindcss/src/utils/brace_expansion.rs:126— farmfe_ecosystem_tailwindcss::utils::brace_expansion::expand_sequence 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.
farmfe_ecosystem_tailwindcss::utils::segment::segment (cyclomatic 16) rust-ecosystem/tailwindcss/src/utils/segment.rs:23— farmfe_ecosystem_tailwindcss::utils::segment::segment 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.
ClassTooLong: VueJsxTransformVisitor rust-plugins/vue-jsx/src/lib.rs:42— ClassTooLong — 1010 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 7 blocks, lines 42-1498. The bar is 400 significant lines; this is 610 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FarmPluginDocs rust-plugins/docs/src/lib.rs:106— ClassTooLong — 789 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 106-1113. The bar is 400 significant lines; this is 389 over it, 1.97× 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: Server packages/core/src/server/index.ts:131— ClassTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 286 over it, 1.72× 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: PluginDriver crates/core/src/plugin/plugin_driver.rs:27— ClassTooLong — 573 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, 2 blocks, lines 27-929. The bar is 400 significant lines; this is 173 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: VitePluginAdapter REDACTED:100— ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 169 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Resolver crates/plugin_resolve/src/resolver.rs:52— ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 3 blocks, lines 52-864. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UtilityRegistry rust-ecosystem/tailwindcss/src/utilities.rs:19— ClassTooLong — 454 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, 2 blocks, lines 19-661. The bar is 400 significant lines; this is 54 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FarmPluginScript crates/plugin_script/src/lib.rs:76— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 3 blocks, lines 76-702. The bar is 400 significant lines; this is 36 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ImportGlobVisitor crates/swc_transformer_import_glob/src/lib.rs:345— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 3 blocks, lines 345-971. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FarmPluginDocsSnapshot rust-plugins/docs-snapshot/src/lib.rs:96— ClassTooLong — 417 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 3 blocks, lines 96-653. The bar is 400 significant lines; this is 17 over it, 1.04× 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: FarmPluginCss crates/plugin_css/src/lib.rs:169— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 2 methods, 3 blocks, lines 169-738. The bar is 400 significant lines; this is 4 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.
Duplicated block (7 lines × 2) crates/core/src/module/module_group.rs:95— crates/core/src/module/module_group.rs:95-102 | crates/core/src/module/module_group.rs:256-262 — 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/src/module/module_group.rs:95` 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/plugin_library/src/formats/esm.rs:47— crates/plugin_library/src/formats/esm.rs:47-53 | crates/plugin_library/src/formats/umd.rs:40-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin_library/src/formats/esm.rs:47` 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/plugin_runtime/src/render_resource_pot/source_replacer.rs:141— crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:141-147 | crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:296-302 — 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/plugin_runtime/src/render_resource_pot/source_replacer.rs:141` 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/toolkit/src/script/concatenate_modules/utils.rs:389— crates/toolkit/src/script/concatenate_modules/utils.rs:389-395 | crates/toolkit/src/script/module2cjs.rs:433-439 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) rust-ecosystem/docs-config/src/validate.rs:296— rust-ecosystem/docs-config/src/validate.rs:296-302 | rust-ecosystem/docs-plan/src/assets.rs:176-182 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-config/src/validate.rs:296` 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/core/src/module/meta_data/mod.rs:111— crates/core/src/module/meta_data/mod.rs:111-117 | crates/core/src/resource/meta_data/mod.rs:72-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/plugin_html/src/deps_analyzer.rs:33— crates/plugin_html/src/deps_analyzer.rs:33-39 | crates/plugin_script/src/deps_analyzer.rs:45-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.
Duplicated block (7 lines × 2) rust-ecosystem/tailwindcss/src/selector_parser.rs:242— rust-ecosystem/tailwindcss/src/selector_parser.rs:242-248 | rust-ecosystem/tailwindcss/src/value_parser.rs:190-196 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/selector_parser.rs:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ast` to `&mut Vec<SelectorAstNode>` in one and `&mut Vec<ValueAstNode>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) rust-ecosystem/tailwindcss/src/utilities.rs:1418— rust-ecosystem/tailwindcss/src/utilities.rs:1418-1426 | rust-ecosystem/tailwindcss/src/utilities/effects.rs:28-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/utilities.rs:1418` 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 (7 lines × 2) rust-plugins/vue-jsx/src/directive.rs:83— rust-plugins/vue-jsx/src/directive.rs:83-89 | rust-plugins/vue-jsx/src/directive.rs:222-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/directive.rs:83` 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, `rust-plugins/vue-jsx/src/directive.rs:229` calls `is_none`, `Some`, `Lit` and `rust-plugins/vue-jsx/src/directive.rs:90` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) scripts/ci-impact-plan.py:293— scripts/ci-impact-plan.py:293-299 | scripts/ci-impact-plan.py:302-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) crates/plugin_partial_bundling/src/analyze_module_graph.rs:123— crates/plugin_partial_bundling/src/analyze_module_graph.rs:123-133 | crates/plugin_partial_bundling/src/analyze_module_graph.rs:166-176 — 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/plugin_partial_bundling/src/analyze_module_graph.rs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) rust-ecosystem/docs-seo/src/lib.rs:192— rust-ecosystem/docs-seo/src/lib.rs:192-202 | rust-ecosystem/docs-seo/src/syndication.rs:37-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) rust-ecosystem/docs-snapshot/src/verify.rs:411— rust-ecosystem/docs-snapshot/src/verify.rs:411-421 | rust-ecosystem/docs-snapshot/src/verify.rs:452-462 — 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 (11 lines × 2) rust-ecosystem/syntax-highlight/src/lib.rs:179— rust-ecosystem/syntax-highlight/src/lib.rs:179-189 | rust-ecosystem/syntax-highlight/src/lib.rs:245-255 — 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) rust-ecosystem/tailwindcss/src/utilities.rs:1661— rust-ecosystem/tailwindcss/src/utilities.rs:1661-1671 | rust-ecosystem/tailwindcss/src/utilities.rs:1695-1705 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/utilities.rs:1661` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:104— rust-plugins/icons/src/loader/svg_builder.rs:104-114 | rust-plugins/svgr/src/svg_builder.rs:117-127 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) crates/core/src/module/module_graph.rs:291— crates/core/src/module/module_graph.rs:291-301 | crates/core/src/module/module_graph.rs:429-440 — 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/src/module/module_graph.rs:291` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/create-farm-rs/src/lib.rs:118— crates/create-farm-rs/src/lib.rs:118-128 | crates/create-farm-rs/src/lib.rs:133-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.
Duplicated block (11 lines × 2) rust-plugins/docs/src/lib.rs:467— rust-plugins/docs/src/lib.rs:467-477 | rust-plugins/docs/src/lib.rs:487-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/docs/src/lib.rs:467` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) rust-ecosystem/tailwindcss/src/utilities.rs:1453— rust-ecosystem/tailwindcss/src/utilities.rs:1453-1463 | rust-ecosystem/tailwindcss/src/utilities.rs:1475-1485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/utilities.rs:1453` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `rust-ecosystem/tailwindcss/src/utilities.rs:1472` calls `Some`, `into` and `rust-ecosystem/tailwindcss/src/utilities.rs:1451` 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 × 2) crates/compiler/src/build/mod.rs:563— crates/compiler/src/build/mod.rs:563-571 | crates/compiler/src/update/mod.rs:789-797 — `crates/compiler/src/build/mod.rs` and `crates/compiler/src/update/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) crates/plugin_mangle_exports/src/mangle_exports.rs:171— crates/plugin_mangle_exports/src/mangle_exports.rs:171-180 | crates/plugin_mangle_exports/src/mangle_exports.rs:205-213 — 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/plugin_mangle_exports/src/mangle_exports.rs:171` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) rust-ecosystem/docs-plan/src/blog.rs:438— rust-ecosystem/docs-plan/src/blog.rs:438-446 | rust-ecosystem/docs-plan/src/sidebars.rs:327-335 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-plan/src/blog.rs:438` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) rust-plugins/auto-import/src/parser/scan_exports.rs:55— rust-plugins/auto-import/src/parser/scan_exports.rs:55-63 | rust-plugins/react-components/src/find_local_components.rs:50-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/auto-import/src/parser/scan_exports.rs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) rust-plugins/sass/src/rebase_urls.rs:62— rust-plugins/sass/src/rebase_urls.rs:62-70 | rust-plugins/sass/src/rebase_urls.rs:82-90 — 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) rust-plugins/auto-import/src/parser/scan_exports.rs:69— rust-plugins/auto-import/src/parser/scan_exports.rs:69-77 | rust-plugins/react-components/src/find_local_components.rs:169-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:40— rust-plugins/icons/src/loader/svg_builder.rs:40-48 | rust-plugins/svgr/src/svg_builder.rs:53-61 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:64— rust-plugins/icons/src/loader/svg_builder.rs:64-72 | rust-plugins/svgr/src/svg_builder.rs:77-85 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:133— rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:133-141 | rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:229-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) rust-ecosystem/tailwindcss-node/src/compile.rs:115— rust-ecosystem/tailwindcss-node/src/compile.rs:115-123 | rust-ecosystem/tailwindcss-node/src/compile.rs:132-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss-node/src/compile.rs:132` 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.
farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements (cognitive 161) crates/plugin_tree_shake/src/tree_shake_modules.rs:314— farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements has cognitive complexity 161 (threshold 15). Drivers by points: if/else 22 (111 pts), loops 10 (31 pts), match/switch 2 (18 pts), boolean chains 1 (nesting depth added 126). 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.
farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::remove_export_idents (cognitive 45) crates/plugin_tree_shake/src/tree_shake_modules/remove_export_idents.rs:286— farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::remove_export_idents has cognitive complexity 45 (threshold 15). Drivers by points: if/else 7 (28 pts), loops 6 (16 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::tree_shake_modules::find_dep_module_read_global_variables_dfs (cognitive 40) crates/plugin_tree_shake/src/tree_shake_modules.rs:613— farmfe_plugin_tree_shake::tree_shake_modules::find_dep_module_read_global_variables_dfs has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 5 (15 pts), boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_used_statements (cognitive 35) crates/plugin_tree_shake/src/tree_shake_modules.rs:211— farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_used_statements has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 18). 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.
farmfe_plugin_tree_shake::tree_shake_modules::traverse_tree_shake_modules (cognitive 32) crates/plugin_tree_shake/src/tree_shake_modules.rs:79— farmfe_plugin_tree_shake::tree_shake_modules::traverse_tree_shake_modules has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4 (11 pts), boolean chains 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.
farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::is_module_contains_reexport_ident (cognitive 32) crates/plugin_tree_shake/src/tree_shake_modules/remove_export_idents.rs:213— farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::is_module_contains_reexport_ident has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (5 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::tree_shake_modules::remove_useless_stmts::remove_useless_stmts (cognitive 24) crates/plugin_tree_shake/src/tree_shake_modules/remove_useless_stmts.rs:16— farmfe_plugin_tree_shake::tree_shake_modules::remove_useless_stmts::remove_useless_stmts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 2 (7 pts), loops 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::tree_shake_modules::set_pending_used_exports (cognitive 19) crates/plugin_tree_shake/src/tree_shake_modules.rs:161— farmfe_plugin_tree_shake::tree_shake_modules::set_pending_used_exports has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::statement_graph::analyze_written_imported_idents::find_written_imported_idents_dfs (cognitive 18) crates/plugin_tree_shake/src/statement_graph/analyze_written_imported_idents.rs:43— farmfe_plugin_tree_shake::statement_graph::analyze_written_imported_idents::find_written_imported_idents_dfs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 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.
farmfe_docs_plan::prepare::prepare_inner (cognitive 124) rust-ecosystem/docs-plan/src/prepare.rs:259— farmfe_docs_plan::prepare::prepare_inner has cognitive complexity 124 (threshold 15). Drivers by points: if/else 46 (101 pts), loops 10 (15 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 62). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_plan::script_pages::parse (cognitive 100) rust-ecosystem/docs-plan/src/script_pages.rs:170— farmfe_docs_plan::script_pages::parse has cognitive complexity 100 (threshold 15). Drivers by points: if/else 21 (61 pts), match/switch 8 (20 pts), loops 6 (14 pts), boolean chains 5 (nesting depth added 60). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_plan::verify (cognitive 43) rust-ecosystem/docs-plan/src/lib.rs:151— farmfe_docs_plan::verify has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 10, loops 6 (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.
farmfe_docs_plan::seo::heads (cognitive 38) rust-ecosystem/docs-plan/src/seo.rs:39— farmfe_docs_plan::seo::heads has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (29 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_plan::blog::metadata (cognitive 37) rust-ecosystem/docs-plan/src/blog.rs:176— farmfe_docs_plan::blog::metadata has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (7 pts), match/switch 3 (5 pts), boolean chains 3 (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.
farmfe_docs_plan::application::generate (cognitive 33) rust-ecosystem/docs-plan/src/application.rs:13— farmfe_docs_plan::application::generate has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 8 (11 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_plan::translations::expand (cognitive 33) rust-ecosystem/docs-plan/src/translations.rs:17— farmfe_docs_plan::translations::expand has cognitive complexity 33 (threshold 15). Drivers by points: if/else 4 (19 pts), loops 5 (13 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_plan::blog::index (cognitive 18) rust-ecosystem/docs-plan/src/blog.rs:348— farmfe_docs_plan::blog::index has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (7 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.
farmfe_docs_plan::prepare::collect (cognitive 16) rust-ecosystem/docs-plan/src/prepare.rs:43— farmfe_docs_plan::prepare::collect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VueJsxTransformVisitor::resolve_indexed_access (cognitive 122) rust-plugins/vue-jsx/src/resolve_type.rs:641— VueJsxTransformVisitor::resolve_indexed_access has cognitive complexity 122 (threshold 15). Drivers by points: if/else 32 (82 pts), match/switch 12 (40 pts) (nesting depth added 78). 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.
VueJsxTransformVisitor::transform_attrs (cognitive 79) rust-plugins/vue-jsx/src/lib.rs:522— VueJsxTransformVisitor::transform_attrs has cognitive complexity 79 (threshold 15). Drivers by points: if/else 32 (52 pts), match/switch 9 (20 pts), boolean chains 7 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VueJsxTransformVisitor::resolve_type_elements (cognitive 65) rust-plugins/vue-jsx/src/resolve_type.rs:369— VueJsxTransformVisitor::resolve_type_elements has cognitive complexity 65 (threshold 15). Drivers by points: match/switch 10 (36 pts), if/else 10 (24 pts), loops 2 (5 pts) (nesting depth added 43). 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.
VueJsxTransformVisitor::extract_props_type (cognitive 42) rust-plugins/vue-jsx/src/resolve_type.rs:25— VueJsxTransformVisitor::extract_props_type has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (24 pts), match/switch 7 (18 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.
VueJsxTransformVisitor::transform_children (cognitive 38) rust-plugins/vue-jsx/src/lib.rs:905— VueJsxTransformVisitor::transform_children has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 5 (10 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VueJsxTransformVisitor::infer_runtime_type (cognitive 38) rust-plugins/vue-jsx/src/resolve_type.rs:994— VueJsxTransformVisitor::infer_runtime_type has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 4 (8 pts), loops 1 (2 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
VueJsxTransformVisitor::build_props_type (cognitive 34) rust-plugins/vue-jsx/src/resolve_type.rs:190— VueJsxTransformVisitor::build_props_type has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VueJsxTransformVisitor::extract_emits_type (cognitive 26) rust-plugins/vue-jsx/src/resolve_type.rs:1156— VueJsxTransformVisitor::extract_emits_type has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 8 (21 pts), if/else 4 (5 pts) (nesting depth added 14). 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.
Duplicated block (14 lines × 2) crates/plugin_html/src/deps_analyzer.rs:115— crates/plugin_html/src/deps_analyzer.rs:115-128 | crates/plugin_html/src/deps_analyzer.rs:171-184 — 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/plugin_html/src/deps_analyzer.rs:115` 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 × 2) crates/plugin_library/src/lib.rs:467— crates/plugin_library/src/lib.rs:467-480 | crates/plugin_library/src/lib.rs:499-512 — 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 (14 lines × 2) crates/swc_transformer_import_glob/src/lib.rs:286— crates/swc_transformer_import_glob/src/lib.rs:286-299 | crates/swc_transformer_import_glob/src/lib.rs:312-325 — 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/swc_transformer_import_glob/src/lib.rs:286` 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) rust-ecosystem/glob/src/scan.rs:200— rust-ecosystem/glob/src/scan.rs:200-213 | rust-ecosystem/glob/src/scan.rs:305-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/glob/src/scan.rs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (14 lines × 2) rust-ecosystem/tailwindcss/src/candidate.rs:292— rust-ecosystem/tailwindcss/src/candidate.rs:292-305 | rust-ecosystem/tailwindcss/src/candidate.rs:309-322 — 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 (14 lines × 2) rust-plugins/auto-import/src/lib.rs:133— rust-plugins/auto-import/src/lib.rs:133-146 | rust-plugins/strip/src/lib.rs:61-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `param` to `&farmfe_core::plugin::PluginTransformHookParam` in one and `&PluginTransformHookParam` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) rust-plugins/vue-jsx/src/directive.rs:90— rust-plugins/vue-jsx/src/directive.rs:90-103 | rust-plugins/vue-jsx/src/directive.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 `rust-plugins/vue-jsx/src/directive.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 (14 lines × 2) crates/node/src/plugin_adapters/js_plugin_adapter/hooks/augment_resource_hash.rs:61— crates/node/src/plugin_adapters/js_plugin_adapter/hooks/augment_resource_hash.rs:61-74 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/process_rendered_resource_pot.rs:109-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `f` to `JsPluginAugmentResourceHashHookFilters` in one and `JsPluginProcessRenderedResourcePotHookFilters` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) crates/core/src/module/module_graph.rs:391— crates/core/src/module/module_graph.rs:391-403 | crates/core/src/module/module_graph.rs:425-437 — 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/plugin_runtime/src/render_resource_pot/external.rs:127— crates/plugin_runtime/src/render_resource_pot/external.rs:127-139 | crates/plugin_runtime/src/render_resource_pot/external.rs:171-183 — 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/plugin_runtime/src/render_resource_pot/external.rs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/plugin_script_meta/src/find_async_modules.rs:20— crates/plugin_script_meta/src/find_async_modules.rs:20-32 | crates/plugin_script_meta/src/find_async_modules.rs:71-83 — 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/toolkit/src/runtime.rs:74— crates/toolkit/src/runtime.rs:74-86 | crates/toolkit/src/runtime.rs:107-119 — 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/toolkit/src/runtime.rs:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) rust-ecosystem/docs-plan/src/lib.rs:179— rust-ecosystem/docs-plan/src/lib.rs:179-191 | rust-ecosystem/docs-seo/src/lib.rs:290-302 — 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 (13 lines × 2) rust-ecosystem/docs-plan/src/translations.rs:20— rust-ecosystem/docs-plan/src/translations.rs:20-32 | rust-ecosystem/docs-plan/src/translations.rs:156-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-plan/src/translations.rs:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) rust-plugins/docs-seo/src/lib.rs:111— rust-plugins/docs-seo/src/lib.rs:111-123 | rust-plugins/docs/src/lib.rs:726-738 — 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 (13 lines × 2) rust-ecosystem/tailwindcss/src/compiler.rs:239— rust-ecosystem/tailwindcss/src/compiler.rs:239-251 | rust-ecosystem/tailwindcss/src/compiler.rs:275-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/compiler.rs:239` 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/compiler/src/generate/resource_cache.rs:178— crates/compiler/src/generate/resource_cache.rs:178-188 | crates/toolkit/src/script/entry_live_bindings.rs:211-220 — 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/compiler/src/generate/resource_cache.rs:178` 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/core/src/module/module_graph.rs:243— crates/core/src/module/module_graph.rs:243-252 | crates/core/src/module/module_graph.rs:513-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/toolkit/src/script/analyze_statement/statement_info.rs:78— crates/toolkit/src/script/analyze_statement/statement_info.rs:78-87 | crates/toolkit/src/script/analyze_statement/statement_info.rs:89-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. 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 (10 lines × 2) rust-plugins/auto-import/src/finish_imports.rs:25— rust-plugins/auto-import/src/finish_imports.rs:25-34 | rust-plugins/react-components/src/finish_components.rs:29-38 — 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 (10 lines × 2) rust-plugins/docs/src/lib.rs:452— rust-plugins/docs/src/lib.rs:452-461 | rust-plugins/docs/src/lib.rs:556-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) crates/testing_helpers/src/lib.rs:247— crates/testing_helpers/src/lib.rs:247-256 | crates/testing_helpers/src/lib.rs:262-272 — 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/testing_helpers/src/lib.rs:247` 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/compiler/src/update/handle_update_modules.rs:145— crates/compiler/src/update/handle_update_modules.rs:145-154 | crates/compiler/src/update/handle_update_modules.rs:293-302 — 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/compiler/src/update/handle_update_modules.rs:145` 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) scripts/ci-unit-shadow-inputs.py:62— scripts/ci-unit-shadow-inputs.py:62-71 | scripts/ci-unit-shadow-inputs.py:107-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scripts/ci-unit-shadow-inputs.py:106` calls `get` and `scripts/ci-unit-shadow-inputs.py:61` 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.
VueJsxTransformVisitor::transform_attrs (cyclomatic 53) rust-plugins/vue-jsx/src/lib.rs:522— VueJsxTransformVisitor::transform_attrs has cyclomatic complexity 53 (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.
VueJsxTransformVisitor::resolve_indexed_access (cyclomatic 46) rust-plugins/vue-jsx/src/resolve_type.rs:641— VueJsxTransformVisitor::resolve_indexed_access has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VueJsxTransformVisitor::resolve_type_elements (cyclomatic 39) rust-plugins/vue-jsx/src/resolve_type.rs:369— VueJsxTransformVisitor::resolve_type_elements has cyclomatic complexity 39 (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.
VueJsxTransformVisitor::infer_runtime_type (cyclomatic 36) rust-plugins/vue-jsx/src/resolve_type.rs:994— VueJsxTransformVisitor::infer_runtime_type has cyclomatic complexity 36 (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.
VueJsxTransformVisitor::transform_children (cyclomatic 24) rust-plugins/vue-jsx/src/lib.rs:905— VueJsxTransformVisitor::transform_children 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.
VueJsxTransformVisitor::extract_props_type (cyclomatic 21) rust-plugins/vue-jsx/src/resolve_type.rs:25— VueJsxTransformVisitor::extract_props_type 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.
VueJsxTransformVisitor::extract_emits_type (cyclomatic 20) rust-plugins/vue-jsx/src/resolve_type.rs:1156— VueJsxTransformVisitor::extract_emits_type has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
farmfe_ecosystem_glob::compile::compile_body_with_context (cognitive 306) rust-ecosystem/glob/src/compile.rs:766— farmfe_ecosystem_glob::compile::compile_body_with_context has cognitive complexity 306 (threshold 15). Drivers by points: if/else 95 (254 pts), boolean chains 35, loops 4 (11 pts), match/switch 2 (6 pts) (nesting depth added 170). 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.
farmfe_ecosystem_glob::scan::scan (cognitive 253) rust-ecosystem/glob/src/scan.rs:142— farmfe_ecosystem_glob::scan::scan has cognitive complexity 253 (threshold 15). Drivers by points: if/else 69 (217 pts), loops 6 (17 pts), boolean chains 16, match/switch 1 (3 pts) (nesting depth added 161). 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.
farmfe_ecosystem_glob::compile::compile_bracket (cognitive 49) rust-ecosystem/glob/src/compile.rs:598— farmfe_ecosystem_glob::compile::compile_bracket has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 11, loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_glob::compile::parse_tokens (cognitive 32) rust-ecosystem/glob/src/compile.rs:1460— farmfe_ecosystem_glob::compile::parse_tokens has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6, loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_glob::compile::collect_bracket (cognitive 21) rust-ecosystem/glob/src/compile.rs:235— farmfe_ecosystem_glob::compile::collect_bracket has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), boolean chains 3 (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.
farmfe_ecosystem_glob::utils::remove_backslashes (cognitive 18) rust-ecosystem/glob/src/utils.rs:7— farmfe_ecosystem_glob::utils::remove_backslashes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_glob::compile::has_explicit_dot_segment (cognitive 16) rust-ecosystem/glob/src/compile.rs:562— farmfe_ecosystem_glob::compile::has_explicit_dot_segment has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/cache.rs:19— crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/cache.rs:19-34 | crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/cache.rs:38-50 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-ecosystem/docs-content/src/machine_markdown.rs:243— rust-ecosystem/docs-content/src/machine_markdown.rs:243-255 | rust-plugins/docs-snippets/src/transform/values.rs:3-17 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1224— rust-ecosystem/tailwindcss/src/utilities.rs:1224-1244 | rust-ecosystem/tailwindcss/src/utilities.rs:1259-1271 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-plugins/auto-import/src/parser/generate_dts.rs:39— rust-plugins/auto-import/src/parser/generate_dts.rs:39-53 | rust-plugins/react-components/src/generate_dts.rs:41-53 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-ecosystem/tailwindcss/src/utilities/effects.rs:12— rust-ecosystem/tailwindcss/src/utilities/effects.rs:12-24 | rust-ecosystem/tailwindcss/src/utilities/effects.rs:96-108 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-plugins/docs-snippets/src/transform/ast.rs:60— rust-plugins/docs-snippets/src/transform/ast.rs:60-77 | rust-plugins/docs-snippets/src/transform/ast.rs:80-92 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust-ecosystem/tailwindcss/src/selector_parser.rs:44— rust-ecosystem/tailwindcss/src/selector_parser.rs:44-59 | rust-ecosystem/tailwindcss/src/value_parser.rs:35-47 — 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.
Dead file (~56 LoC) crates/create-farm-rs/templates/electron/preact/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) crates/create-farm-rs/templates/electron/react/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) crates/create-farm-rs/templates/electron/solid/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) crates/create-farm-rs/templates/electron/svelte/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) crates/create-farm-rs/templates/electron/vanilla/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) crates/create-farm-rs/templates/electron/vue/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~56 LoC) examples/electron/electron/main.ts— no import path from any entry point (565 application, 396 tooling, 525 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
Low contrast colour pair in CSS (3.6:1) .agents/skills/brainstorming/scripts/frame-template.html:128— `.option.selected .letter` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) .agents/skills/brainstorming/scripts/frame-template.html:190— `.mock-nav` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) .agents/skills/brainstorming/scripts/frame-template.html:193— `.mock-button` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) .claude/skills/brainstorming/scripts/frame-template.html:128— `.option.selected .letter` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) .claude/skills/brainstorming/scripts/frame-template.html:190— `.mock-nav` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) .claude/skills/brainstorming/scripts/frame-template.html:193— `.mock-button` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
farmfe_docs_content::preprocess::prepare (cyclomatic 52) rust-ecosystem/docs-content/src/preprocess.rs:36— farmfe_docs_content::preprocess::prepare has cyclomatic complexity 52 (threshold 15). Of this number, 48 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_docs_content::machine_markdown::static_commands (cyclomatic 19) rust-ecosystem/docs-content/src/machine_markdown.rs:376— farmfe_docs_content::machine_markdown::static_commands has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_docs_content::code_blocks::inline_code (cyclomatic 18) rust-ecosystem/docs-content/src/code_blocks.rs:154— farmfe_docs_content::code_blocks::inline_code 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.
farmfe_docs_content::machine_markdown::highlighted_inline_text (cyclomatic 18) rust-ecosystem/docs-content/src/machine_markdown.rs:69— farmfe_docs_content::machine_markdown::highlighted_inline_text 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.
farmfe_docs_content::jsx_attributes::preserve (cyclomatic 17) rust-ecosystem/docs-content/src/jsx_attributes.rs:15— farmfe_docs_content::jsx_attributes::preserve has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_docs_content::code_blocks::apply::rewrite (cyclomatic 16) rust-ecosystem/docs-content/src/code_blocks.rs:278— farmfe_docs_content::code_blocks::apply::rewrite 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.
farmfe_docs_plan::prepare::prepare_inner (cyclomatic 52) rust-ecosystem/docs-plan/src/prepare.rs:259— farmfe_docs_plan::prepare::prepare_inner has cyclomatic complexity 52 (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.
farmfe_docs_plan::script_pages::parse (cyclomatic 47) rust-ecosystem/docs-plan/src/script_pages.rs:170— farmfe_docs_plan::script_pages::parse has cyclomatic complexity 47 (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.
farmfe_docs_plan::verify (cyclomatic 33) rust-ecosystem/docs-plan/src/lib.rs:151— farmfe_docs_plan::verify 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.
farmfe_docs_plan::blog::metadata (cyclomatic 21) rust-ecosystem/docs-plan/src/blog.rs:176— farmfe_docs_plan::blog::metadata 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.
farmfe_docs_plan::seo::heads (cyclomatic 19) rust-ecosystem/docs-plan/src/seo.rs:39— farmfe_docs_plan::seo::heads has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_docs_plan::application::generate (cyclomatic 18) rust-ecosystem/docs-plan/src/application.rs:13— farmfe_docs_plan::application::generate 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.
Duplicated block (15 lines × 2) crates/compiler/src/generate/render_resource_pots.rs:55— crates/compiler/src/generate/render_resource_pots.rs:55-69 | crates/compiler/src/generate/render_resource_pots.rs:166-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) crates/testing_helpers/src/lib.rs:78— crates/testing_helpers/src/lib.rs:78-92 | crates/testing_helpers/src/lib.rs:207-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) rust-plugins/compress/src/utils.rs:43— rust-plugins/compress/src/utils.rs:43-57 | rust-plugins/compress/src/utils.rs:61-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/compress/src/utils.rs:43` 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 × 2) rust-plugins/vue-jsx/src/directive.rs:155— rust-plugins/vue-jsx/src/directive.rs:155-169 | rust-plugins/vue-jsx/src/directive.rs:179-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 `rust-plugins/vue-jsx/src/directive.rs:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:376— rust-plugins/vue-jsx/src/resolve_type.rs:376-390 | rust-plugins/vue-jsx/src/resolve_type.rs:415-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:663— rust-plugins/vue-jsx/src/resolve_type.rs:663-677 | rust-plugins/vue-jsx/src/resolve_type.rs:825-839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:663` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:400— crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:400-411 | crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:441-452 — 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 (12 lines × 2) rust-ecosystem/docs-content/src/code_blocks.rs:168— rust-ecosystem/docs-content/src/code_blocks.rs:168-179 | rust-ecosystem/docs-content/src/code_blocks.rs:197-208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-content/src/code_blocks.rs:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rust-plugins/react-components/src/insert_import.rs:197— rust-plugins/react-components/src/insert_import.rs:197-208 | rust-plugins/react-components/src/insert_import.rs:213-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/react-components/src/insert_import.rs:197` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rust-plugins/icons/src/compiler/react.rs:5— rust-plugins/icons/src/compiler/react.rs:5-16 | rust-plugins/svgr/src/react_compiler.rs:10-22 — 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 (12 lines × 2) crates/core/src/plugin/plugin_driver.rs:220— crates/core/src/plugin/plugin_driver.rs:220-231 | crates/core/src/plugin/plugin_driver.rs:900-912 — 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/src/plugin/plugin_driver.rs:220` 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/compiler/src/build/module_cache.rs:259— crates/compiler/src/build/module_cache.rs:259-270 | crates/compiler/src/build/module_cache.rs:311-322 — 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/compiler/src/build/module_cache.rs:259` 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/plugin_mangle_exports/src/mangle_exports.rs:165— crates/plugin_mangle_exports/src/mangle_exports.rs:165-172 | crates/plugin_mangle_exports/src/mangle_exports.rs:560-567 — 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/plugin_mangle_exports/src/mangle_exports.rs:165` 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/plugin_runtime/src/render_resource_pot/source_replacer.rs:200— crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:200-207 | crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:297-304 — 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/plugin_runtime/src/render_resource_pot/source_replacer.rs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:443— rust-plugins/vue-jsx/src/resolve_type.rs:443-450 | rust-plugins/vue-jsx/src/resolve_type.rs:465-472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:443` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rust-ecosystem/syntax-highlight/src/editor_theme.rs:5— rust-ecosystem/syntax-highlight/src/editor_theme.rs:5-12 | rust-ecosystem/syntax-highlight/src/farm_theme.rs:3-10 — 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 (8 lines × 2) rust-plugins/auto-import/src/parser/generate_dts.rs:95— rust-plugins/auto-import/src/parser/generate_dts.rs:95-102 | rust-plugins/react-components/src/generate_dts.rs:98-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) rust-ecosystem/docs-plan/src/script_pages.rs:133— rust-ecosystem/docs-plan/src/script_pages.rs:133-140 | rust-ecosystem/docs-plan/src/script_pages.rs:345-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-plan/src/script_pages.rs:133` 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 (5 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:116— rust-plugins/icons/src/loader/svg_builder.rs:116-120 | rust-plugins/svgr/src/svg_builder.rs:144-148 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) rust-ecosystem/tailwindcss/src/utilities.rs:1545— rust-ecosystem/tailwindcss/src/utilities.rs:1545-1549 | rust-ecosystem/tailwindcss/src/utilities.rs:1559-1563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/utilities.rs:1545` 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/node/src/plugin_adapters/js_plugin_adapter/context.rs:242— crates/node/src/plugin_adapters/js_plugin_adapter/context.rs:242-246 | crates/node/src/plugin_adapters/js_plugin_adapter/context.rs:254-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_importers.rs:21— crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_importers.rs:21-25 | crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_modules_by_file.rs:38-42 — 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) rust-plugins/vue-jsx/src/resolve_type.rs:1163— rust-plugins/vue-jsx/src/resolve_type.rs:1163-1167 | rust-plugins/vue-jsx/src/resolve_type.rs:1169-1173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) scripts/ci-unit-shadow-inputs.py:54— scripts/ci-unit-shadow-inputs.py:54-58 | scripts/ci-unit-shadow-inputs.py:98-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: JsPluginAdapter (LCOM4 11) crates/node/src/plugin_adapters/js_plugin_adapter/mod.rs:60— JsPluginAdapter's methods fall into 11 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 11 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: FarmPluginScript (LCOM4 9) crates/plugin_script/src/lib.rs:76— FarmPluginScript's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FarmPluginCss (LCOM4 8) crates/plugin_css/src/lib.rs:169— FarmPluginCss's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FarmPluginLibrary (LCOM4 6) crates/plugin_library/src/lib.rs:61— FarmPluginLibrary's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RenameVisitor (LCOM4 6) crates/toolkit/src/script/concatenate_modules/unique_idents.rs:128— RenameVisitor's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CompilationContext (LCOM4 4) crates/core/src/context/mod.rs:60— CompilationContext'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.
farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps (cyclomatic 34) crates/compiler/src/update/diff_and_patch_module_graph.rs:268— farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources (cyclomatic 30) crates/compiler/src/generate/render_resource_pots.rs:22— farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources 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.
farmfe_compiler::update::handle_update_modules::handle_update_modules (cyclomatic 21) crates/compiler/src/update/handle_update_modules.rs:109— farmfe_compiler::update::handle_update_modules::handle_update_modules 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.
farmfe_compiler::update::patch_module_group_graph::patch_module_group_graph (cyclomatic 16) crates/compiler/src/update/patch_module_group_graph.rs:16— farmfe_compiler::update::patch_module_group_graph::patch_module_group_graph has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
farmfe_compiler::update::patch_module_group_graph::patch_removed_dynamic_import_and_dynamic_entry (cyclomatic 16) crates/compiler/src/update/patch_module_group_graph.rs:298— farmfe_compiler::update::patch_module_group_graph::patch_removed_dynamic_import_and_dynamic_entry 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.
FarmPluginDocs::finalize_resources (cyclomatic 34) rust-plugins/docs/src/lib.rs:705— FarmPluginDocs::finalize_resources has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FarmPluginDocs::update_development (cyclomatic 22) rust-plugins/docs/src/development.rs:17— FarmPluginDocs::update_development 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.
FarmPluginDocs::resolve (cyclomatic 21) rust-plugins/docs/src/lib.rs:381— FarmPluginDocs::resolve 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.
FarmPluginDocs::load (cyclomatic 17) rust-plugins/docs/src/lib.rs:528— FarmPluginDocs::load 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.
FarmPluginDocs::build_start (cyclomatic 16) rust-plugins/docs/src/lib.rs:231— FarmPluginDocs::build_start 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.
farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info (cyclomatic 33) crates/toolkit/src/script/analyze_statement/statement_info.rs:32— farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info has cyclomatic complexity 33 (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.
farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements (cyclomatic 25) crates/toolkit/src/script/concatenate_modules/strip_module_decl.rs:255— farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_toolkit::script::concatenate_modules::strip_modules_asts (cyclomatic 22) crates/toolkit/src/script/concatenate_modules/mod.rs:239— farmfe_toolkit::script::concatenate_modules::strip_modules_asts 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.
farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all (cyclomatic 20) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:596— farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all 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.
farmfe_toolkit::script::entry_live_bindings::resolve_origin::resolve (cyclomatic 17) crates/toolkit/src/script/entry_live_bindings.rs:412— farmfe_toolkit::script::entry_live_bindings::resolve_origin::resolve has cyclomatic complexity 17 (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.
farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl (cognitive 160) crates/plugin_mangle_exports/src/mangle_exports.rs:252— farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl has cognitive complexity 160 (threshold 15). Drivers by points: if/else 17 (81 pts), match/switch 8 (59 pts), loops 6 (20 pts) (nesting depth added 129). 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.
farmfe_plugin_mangle_exports::mangle_exports::find_imports_to_rename (cognitive 95) crates/plugin_mangle_exports/src/mangle_exports.rs:154— farmfe_plugin_mangle_exports::mangle_exports::find_imports_to_rename has cognitive complexity 95 (threshold 15). Drivers by points: if/else 13 (59 pts), loops 4 (21 pts), match/switch 2 (13 pts), boolean chains 2 (nesting depth added 74). 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.
farmfe_plugin_mangle_exports::mangle_exports::find_idents_can_not_be_mangled (cognitive 50) crates/plugin_mangle_exports/src/mangle_exports.rs:530— farmfe_plugin_mangle_exports::mangle_exports::find_idents_can_not_be_mangled has cognitive complexity 50 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 4 (13 pts), match/switch 2 (11 pts), boolean chains 1 (nesting depth added 35). 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.
farmfe_plugin_mangle_exports::mangle_exports::mangle_exports (cognitive 33) crates/plugin_mangle_exports/src/mangle_exports.rs:27— farmfe_plugin_mangle_exports::mangle_exports::mangle_exports has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 5 (10 pts), boolean chains 3 (nesting depth added 16). 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.
farmfe_plugin_mangle_exports::utils::transform_export_all_to_export_named (cognitive 20) crates/plugin_mangle_exports/src/utils.rs:50— farmfe_plugin_mangle_exports::utils::transform_export_all_to_export_named has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (5 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.
FarmPluginDocs::finalize_resources (cognitive 56) rust-plugins/docs/src/lib.rs:705— FarmPluginDocs::finalize_resources has cognitive complexity 56 (threshold 15). Drivers by points: if/else 28 (42 pts), loops 4 (7 pts), boolean chains 6, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginDocs::update_development (cognitive 30) rust-plugins/docs/src/development.rs:17— FarmPluginDocs::update_development has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 8, loops 5 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginDocs::resolve (cognitive 28) rust-plugins/docs/src/lib.rs:381— FarmPluginDocs::resolve has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 8, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginDocs::build_start (cognitive 25) rust-plugins/docs/src/lib.rs:231— FarmPluginDocs::build_start has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6, 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.
FarmPluginDocs::load (cognitive 23) rust-plugins/docs/src/lib.rs:528— FarmPluginDocs::load has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_docs_snippets::transform::lower_diagnostic (cognitive 32) rust-plugins/docs-snippets/src/transform.rs:81— farmfe_plugin_docs_snippets::transform::lower_diagnostic has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3 (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.
farmfe_plugin_docs_snippets::inventory::inspect_with_resolver (cognitive 24) rust-plugins/docs-snippets/src/inventory.rs:19— farmfe_plugin_docs_snippets::inventory::inspect_with_resolver has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_docs_snippets::transform::commands::lower (cognitive 24) rust-plugins/docs-snippets/src/transform/commands.rs:8— farmfe_plugin_docs_snippets::transform::commands::lower has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_docs_snippets::transform::codeblock::lower (cognitive 23) rust-plugins/docs-snippets/src/transform/codeblock.rs:6— farmfe_plugin_docs_snippets::transform::codeblock::lower has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (19 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_docs_snippets::inventory::literal (cognitive 18) rust-plugins/docs-snippets/src/inventory.rs:76— farmfe_plugin_docs_snippets::inventory::literal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×5
Edited copy of a member (16 corresponding lines) rust-plugins/compress/src/utils.rs:41— rust-plugins/compress/src/utils.rs:41-57 | rust-plugins/compress/src/utils.rs:59-75 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) rust-ecosystem/docs-content/src/machine_markdown.rs:295— rust-ecosystem/docs-content/src/machine_markdown.rs:295-314 | rust-plugins/docs-snippets/src/transform/values.rs:73-88 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1416— rust-ecosystem/tailwindcss/src/utilities.rs:1416-1432 | rust-ecosystem/tailwindcss/src/utilities/effects.rs:26-41 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/node/src/plugin_adapters/js_plugin_adapter/hooks/augment_resource_hash.rs:29— crates/node/src/plugin_adapters/js_plugin_adapter/hooks/augment_resource_hash.rs:29-45 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/process_rendered_resource_pot.rs:137-152 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/toolkit/src/script/concatenate_modules/utils.rs:181— crates/toolkit/src/script/concatenate_modules/utils.rs:181-196 | rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:354-369 — 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.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark .agents/skills/brainstorming/scripts/frame-template.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .claude/skills/brainstorming/scripts/frame-template.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark crates/create-farm-rs/templates/lit/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark crates/create-farm-rs/templates/tauri/vanilla/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (2.9:1) .agents/skills/brainstorming/scripts/frame-template.html:120— `.option .letter` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.9:1) .agents/skills/brainstorming/scripts/frame-template.html:158— `.mockup-header` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.9:1) .claude/skills/brainstorming/scripts/frame-template.html:120— `.option .letter` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.9:1) .claude/skills/brainstorming/scripts/frame-template.html:158— `.mockup-header` sets color: #86868b on background-color: #e5e5e7 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
farmfe_ecosystem_glob::compile::compile_body_with_context (cyclomatic 119) rust-ecosystem/glob/src/compile.rs:766— farmfe_ecosystem_glob::compile::compile_body_with_context has cyclomatic complexity 119 (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.
farmfe_ecosystem_glob::scan::scan (cyclomatic 91) rust-ecosystem/glob/src/scan.rs:142— farmfe_ecosystem_glob::scan::scan has cyclomatic complexity 91 (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.
farmfe_ecosystem_glob::compile::compile_bracket (cyclomatic 28) rust-ecosystem/glob/src/compile.rs:598— farmfe_ecosystem_glob::compile::compile_bracket has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_ecosystem_glob::compile::parse_tokens (cyclomatic 27) rust-ecosystem/glob/src/compile.rs:1460— farmfe_ecosystem_glob::compile::parse_tokens 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.
farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl (cyclomatic 33) crates/plugin_mangle_exports/src/mangle_exports.rs:252— farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl 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.
farmfe_plugin_mangle_exports::mangle_exports::find_imports_to_rename (cyclomatic 22) crates/plugin_mangle_exports/src/mangle_exports.rs:154— farmfe_plugin_mangle_exports::mangle_exports::find_imports_to_rename 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.
farmfe_plugin_mangle_exports::mangle_exports::mangle_exports (cyclomatic 17) crates/plugin_mangle_exports/src/mangle_exports.rs:27— farmfe_plugin_mangle_exports::mangle_exports::mangle_exports 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.
farmfe_plugin_mangle_exports::mangle_exports::find_idents_can_not_be_mangled (cyclomatic 16) crates/plugin_mangle_exports/src/mangle_exports.rs:530— farmfe_plugin_mangle_exports::mangle_exports::find_idents_can_not_be_mangled 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.
farmfe_plugin_docs_snippets::transform::lower_diagnostic (cyclomatic 19) rust-plugins/docs-snippets/src/transform.rs:81— farmfe_plugin_docs_snippets::transform::lower_diagnostic has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_docs_snippets::transform::codeblock::lower (cyclomatic 19) rust-plugins/docs-snippets/src/transform/codeblock.rs:6— farmfe_plugin_docs_snippets::transform::codeblock::lower has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_docs_snippets::transform::commands::lower (cyclomatic 19) rust-plugins/docs-snippets/src/transform/commands.rs:8— farmfe_plugin_docs_snippets::transform::commands::lower has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_docs_snippets::inventory::literal (cyclomatic 16) rust-plugins/docs-snippets/src/inventory.rs:76— farmfe_plugin_docs_snippets::inventory::literal 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.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs (cognitive 112) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:217— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs has cognitive complexity 112 (threshold 15). Drivers by points: if/else 25 (75 pts), loops 10 (21 pts), match/switch 3 (13 pts), boolean chains 3 (nesting depth added 71). 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.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_unresolved_import_dfs (cognitive 45) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:546— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_unresolved_import_dfs has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (31 pts), loops 3 (10 pts), boolean chains 4 (nesting depth added 25). 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.
farmfe_plugin_script_meta::plugin_exports::expand_exports::get_basic_module_export_ident (cognitive 34) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:101— farmfe_plugin_script_meta::plugin_exports::expand_exports::get_basic_module_export_ident has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 3 (10 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_script_meta::plugin_exports::expand_exports::complete_cyclic_exports (cognitive 22) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:169— farmfe_plugin_script_meta::plugin_exports::expand_exports::complete_cyclic_exports has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (8 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.
farmfe_docs_config::validate::validate (cognitive 111) rust-ecosystem/docs-config/src/validate.rs:210— farmfe_docs_config::validate::validate has cognitive complexity 111 (threshold 15). Drivers by points: if/else 33 (72 pts), loops 14 (24 pts), boolean chains 13, match/switch 1 (2 pts) (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_config::typescript::render (cognitive 39) rust-ecosystem/docs-config/src/typescript.rs:92— farmfe_docs_config::typescript::render has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 3 (5 pts), match/switch 2 (3 pts), boolean chains 2 (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.
farmfe_docs_config::syndication::validate (cognitive 21) rust-ecosystem/docs-config/src/syndication.rs:83— farmfe_docs_config::syndication::validate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_config::exclusions::resolve (cognitive 16) rust-ecosystem/docs-config/src/exclusions.rs:8— farmfe_docs_config::exclusions::resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_vue_jsx::hmr::inject (cognitive 78) rust-plugins/vue-jsx/src/hmr.rs:8— farmfe_plugin_vue_jsx::hmr::inject has cognitive complexity 78 (threshold 15). Drivers by points: if/else 12 (48 pts), loops 6 (15 pts), match/switch 6 (15 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.
farmfe_plugin_vue_jsx::directive::parse_directive (cognitive 36) rust-plugins/vue-jsx/src/directive.rs:37— farmfe_plugin_vue_jsx::directive::parse_directive has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 4 (9 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_plugin_vue_jsx::directive::parse_v_model_directive (cognitive 36) rust-plugins/vue-jsx/src/directive.rs:202— farmfe_plugin_vue_jsx::directive::parse_v_model_directive has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 3 (6 pts), boolean chains 3 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
farmfe_plugin_vue_jsx::util::dedupe_props (cognitive 21) rust-plugins/vue-jsx/src/util.rs:133— farmfe_plugin_vue_jsx::util::dedupe_props has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (10 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImportGlobVisitor::glob_and_filter_sources_with_options (cognitive 42) crates/swc_transformer_import_glob/src/lib.rs:589— ImportGlobVisitor::glob_and_filter_sources_with_options has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (30 pts), match/switch 2 (5 pts), loops 3 (4 pts), boolean chains 3 (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.
ImportGlobVisitor::visit_mut_expr (cognitive 37) crates/swc_transformer_import_glob/src/lib.rs:823— ImportGlobVisitor::visit_mut_expr has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 18). 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.
ImportGlobVisitor::try_alias (cognitive 30) crates/swc_transformer_import_glob/src/lib.rs:415— ImportGlobVisitor::try_alias has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 5, match/switch 2 (3 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.
ImportGlobVisitor::find_rel_source_in (cognitive 20) crates/swc_transformer_import_glob/src/lib.rs:513— ImportGlobVisitor::find_rel_source_in has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss_node::resolve::resolve_with_extensions (cognitive 40) rust-ecosystem/tailwindcss-node/src/resolve.rs:105— farmfe_ecosystem_tailwindcss_node::resolve::resolve_with_extensions has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 5 (9 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss_node::compile::resolve_imports (cognitive 20) rust-ecosystem/tailwindcss-node/src/compile.rs:279— farmfe_ecosystem_tailwindcss_node::compile::resolve_imports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss_node::normalize_path::normalize_path_base (cognitive 20) rust-ecosystem/tailwindcss-node/src/normalize_path.rs:26— farmfe_ecosystem_tailwindcss_node::normalize_path::normalize_path_base has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_ecosystem_tailwindcss_node::urls::rewrite_image_set_inner (cognitive 20) rust-ecosystem/tailwindcss-node/src/urls.rs:184— farmfe_ecosystem_tailwindcss_node::urls::rewrite_image_set_inner has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: Compiler crates/compiler/src/lib.rs:32— TooManyMethods — 48 methods, declared across 6 files: build/mod.rs (15), update/mod.rs (11), write/mod.rs (9), src/lib.rs (8), +2 more file(s). The bar is 30 methods; this is 18 over it, 1.60× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Server packages/core/src/server/index.ts:131— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ModuleGraph crates/core/src/module/module_graph.rs:181— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Compiler packages/core/src/compiler/index.ts:54— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1544— rust-ecosystem/tailwindcss/src/utilities.rs:1544-1555 | rust-ecosystem/tailwindcss/src/utilities.rs:1558-1569 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) rust-plugins/strip/src/lib.rs:182— rust-plugins/strip/src/lib.rs:182-193 | rust-plugins/strip/src/lib.rs:195-208 — 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/node/src/plugin_adapters/js_plugin_adapter/mod.rs:179— crates/node/src/plugin_adapters/js_plugin_adapter/mod.rs:179-190 | crates/node/src/plugin_adapters/js_plugin_adapter/mod.rs:197-208 — 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) scripts/incremental-release-publish.py:196— scripts/incremental-release-publish.py:196-207 | scripts/npm-release-diagnose.py:49-62 — 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) rust-ecosystem/docs-content/src/machine_markdown.rs:256— rust-ecosystem/docs-content/src/machine_markdown.rs:256-265 | rust-plugins/docs-snippets/src/transform/values.rs:19-28 — 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/compiler/src/build/mod.rs:110— crates/compiler/src/build/mod.rs:110-119 | crates/compiler/src/update/mod.rs:307-319 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust-ecosystem/tailwindcss/src/ast.rs:132— rust-ecosystem/tailwindcss/src/ast.rs:132-142 | rust-ecosystem/tailwindcss-node/src/css_origins.rs:164-173 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rust-ecosystem/docs-plan/src/blog.rs:89— rust-ecosystem/docs-plan/src/blog.rs:89-99 | rust-ecosystem/docs-plan/src/sidebars.rs:33-42 — 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 (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) crates/core/src/context/source_observation.rs:128— crates/core/src/context/source_observation.rs:128-136 | crates/core/src/context/source_observation.rs:419-425 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) rust-ecosystem/docs-content/src/markdown_html.rs:39— rust-ecosystem/docs-content/src/markdown_html.rs:39-45 | rust-ecosystem/docs-plan/src/seo.rs:30-37 — 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) scripts/incremental-chain-evidence.py:53— scripts/incremental-chain-evidence.py:53-61 | scripts/incremental-release-functional.py:25-31 — 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) scripts/release-registry-host-tool.py:73— scripts/release-registry-host-tool.py:73-80 | scripts/release-registry-selection.py:52-58 — 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.
Unused dependency 'core-js' — Declared in crates/create-farm-rs/templates/react/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in crates/create-farm-rs/templates/svelte/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in crates/create-farm-rs/templates/tauri/react/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in crates/create-farm-rs/templates/tauri/svelte/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X2 · Cancellation propagation· Async function without AbortSignal · ×4
Async function without AbortSignal: wasmHelper rust-plugins/wasm/src/wasm_runtime.js:3— `wasmHelper` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: create packages/docs/src/development.ts:177— `create` holds an AbortSignal but calls `replace(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `replace(…, { signal })`.
Async function without AbortSignal: resources packages/docs/src/page-loader-core.ts:109— `resources` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: run packages/docs/src/workflow.ts:251— `run` holds an AbortSignal but calls `fs.readFile(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fs.readFile(…, { signal })`.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×3
Animation without a prefers-reduced-motion guard website/src/pages/index.module.css:87— `.farmButton:before` moves (`animation: glowing 120s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/src/pages/index.module.css:155— `.farmButton2:before` moves (`animation: glowing 100s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/src/css/_doc.siderbar.scss:98— `#__docusaurus .menu__list` moves (`transition: height 0.35s cubic-bezier(0.36, 0.66, 0.04, 1) 25ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
ImportGlobVisitor::try_alias (cyclomatic 18) crates/swc_transformer_import_glob/src/lib.rs:415— ImportGlobVisitor::try_alias 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.
ImportGlobVisitor::glob_and_filter_sources_with_options (cyclomatic 17) crates/swc_transformer_import_glob/src/lib.rs:589— ImportGlobVisitor::glob_and_filter_sources_with_options 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.
ImportGlobVisitor::visit_mut_expr (cyclomatic 17) crates/swc_transformer_import_glob/src/lib.rs:823— ImportGlobVisitor::visit_mut_expr 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.
XxxComment js-plugins/sass/src/index.ts:293— // /xxx — 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.
XxxComment js-plugins/sass/src/index.ts:294— // ./xxx — 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.
XxxComment crates/toolkit/src/script/concatenate_modules/unique_idents.rs:369— // // xxx — 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.
SourceReplacer::visit_mut_url (cognitive 54) crates/plugin_css/src/source_replacer.rs:44— SourceReplacer::visit_mut_url has cognitive complexity 54 (threshold 15). Drivers by points: if/else 11 (41 pts), match/switch 2 (8 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 39). 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.
SourceReplacer::replace_source_with_id (cognitive 29) crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:123— SourceReplacer::replace_source_with_id has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (29 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.
SourceReplacer::visit_mut_stylesheet (cognitive 25) crates/plugin_css/src/source_replacer.rs:112— SourceReplacer::visit_mut_stylesheet has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 2 (9 pts), boolean chains 1, loops 1 (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.
farmfe_plugin_partial_bundling::merge_module_pots::handle_enforce_target_min_size (cognitive 41) crates/plugin_partial_bundling/src/merge_module_pots.rs:339— farmfe_plugin_partial_bundling::merge_module_pots::handle_enforce_target_min_size has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 6 (18 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.
farmfe_plugin_partial_bundling::merge_module_pots::merge_resource_pots_by_buckets (cognitive 33) crates/plugin_partial_bundling/src/merge_module_pots.rs:236— farmfe_plugin_partial_bundling::merge_module_pots::merge_resource_pots_by_buckets has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 3 (6 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_partial_bundling::analyze_module_graph::module_group_from_entry (cognitive 30) crates/plugin_partial_bundling/src/analyze_module_graph.rs:89— farmfe_plugin_partial_bundling::analyze_module_graph::module_group_from_entry has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 3 (8 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.
farmfe_plugin_runtime::handle_entry_resources::create_export_info_code (cognitive 37) crates/plugin_runtime/src/handle_entry_resources.rs:219— farmfe_plugin_runtime::handle_entry_resources::create_export_info_code has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 4 (9 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_runtime::render_resource_pot::scope_hoisting::build_scope_hoisted_module_groups (cognitive 34) crates/plugin_runtime/src/render_resource_pot/scope_hoisting.rs:78— farmfe_plugin_runtime::render_resource_pot::scope_hoisting::build_scope_hoisted_module_groups has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 5 (12 pts), boolean chains 2 (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.
farmfe_plugin_runtime::render_resource_pot::transform_async_module::transform_async_module (cognitive 34) crates/plugin_runtime/src/render_resource_pot/transform_async_module.rs:32— farmfe_plugin_runtime::render_resource_pot::transform_async_module::transform_async_module has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (25 pts), loops 3 (6 pts), match/switch 1 (3 pts) (nesting depth added 24). 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.
Resolver::try_alias (cognitive 34) crates/plugin_resolve/src/resolver.rs:426— Resolver::try_alias has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (27 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Resolver::_try_node_modules_internal (cognitive 25) crates/plugin_resolve/src/resolver.rs:536— Resolver::_try_node_modules_internal has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Resolver::try_package_entry (cognitive 24) crates/plugin_resolve/src/resolver.rs:705— Resolver::try_package_entry has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_auto_import::presets::parse_presets (cognitive 24) rust-plugins/auto-import/src/presets/mod.rs:48— farmfe_plugin_auto_import::presets::parse_presets has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (14 pts), match/switch 3 (10 pts) (nesting depth added 16). 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.
farmfe_plugin_auto_import::parser::inject_imports::inject_imports (cognitive 22) rust-plugins/auto-import/src/parser/inject_imports.rs:54— farmfe_plugin_auto_import::parser::inject_imports::inject_imports has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 2 (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.
farmfe_plugin_auto_import::parser::scan_exports::scan_exports (cognitive 20) rust-plugins/auto-import/src/parser/scan_exports.rs:79— farmfe_plugin_auto_import::parser::scan_exports::scan_exports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (9 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_syntax_highlight::highlight_with_themes (cognitive 17) rust-ecosystem/syntax-highlight/src/lib.rs:173— farmfe_syntax_highlight::highlight_with_themes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (farmfe_syntax_highlight::highlight_single_parse_with_themes) 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.
farmfe_syntax_highlight::highlight_single_parse_with_themes (cognitive 17) rust-ecosystem/syntax-highlight/src/lib.rs:239— farmfe_syntax_highlight::highlight_single_parse_with_themes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (farmfe_syntax_highlight::highlight_with_themes) 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.
farmfe_syntax_highlight::static_html::render_static_lines (cognitive 17) rust-ecosystem/syntax-highlight/src/static_html.rs:30— farmfe_syntax_highlight::static_html::render_static_lines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) rust-plugins/auto-import/src/parser/scan_exports.rs:54— rust-plugins/auto-import/src/parser/scan_exports.rs:54-67 | rust-plugins/react-components/src/find_local_components.rs:49-62 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) rust-plugins/sass/src/rebase_urls.rs:60— rust-plugins/sass/src/rebase_urls.rs:60-73 | rust-plugins/sass/src/rebase_urls.rs:80-94 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/compiler/src/build/module_cache.rs:513— crates/compiler/src/build/module_cache.rs:513-526 | crates/core/src/context/mod.rs:161-174 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) crates/plugin_tree_shake/src/tree_shake_modules/remove_useless_stmts.rs:133— crates/plugin_tree_shake/src/tree_shake_modules/remove_useless_stmts.rs:133-153 | crates/plugin_tree_shake/src/tree_shake_modules/remove_useless_stmts.rs:158-182 — 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) rust-ecosystem/tailwindcss/src/utils/decode_arbitrary_value.rs:22— rust-ecosystem/tailwindcss/src/utils/decode_arbitrary_value.rs:22-43 | rust-ecosystem/tailwindcss/src/variants.rs:660-680 — 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) scripts/release-registry-selection.py:195— scripts/release-registry-selection.py:195-221 | scripts/release-version-history.py:383-403 — 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 (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) crates/core/src/resource/mod.rs:68— crates/core/src/resource/mod.rs:68-78 | crates/core/src/resource/mod.rs:80-90 — 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/plugin_script/src/swc_plugins.rs:297— crates/plugin_script/src/swc_plugins.rs:297-307 | crates/plugin_script/src/swc_plugins.rs:309-319 — 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/node/src/lib.rs:462— crates/node/src/lib.rs:462-476 | crates/node/src/lib.rs:479-489 — 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 (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) crates/core/src/module/meta_data/custom.rs:47— crates/core/src/module/meta_data/custom.rs:47-54 | crates/core/src/module/meta_data/custom.rs:72-79 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust-ecosystem/docs-config/src/syndication.rs:73— rust-ecosystem/docs-config/src/syndication.rs:73-82 | rust-ecosystem/docs-seo/src/lib.rs:57-64 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust-ecosystem/tailwindcss/src/utils/is_color.rs:8— rust-ecosystem/tailwindcss/src/utils/is_color.rs:8-205 | rust-ecosystem/tailwindcss/src/utils/replace_shadow_colors.rs:9-16 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) crates/core/src/module/mod.rs:239— crates/core/src/module/mod.rs:239-244 | crates/core/src/resource/mod.rs:27-33 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust-ecosystem/tailwindcss/src/utils/infer_data_type.rs:108— rust-ecosystem/tailwindcss/src/utils/infer_data_type.rs:108-117 | rust-ecosystem/tailwindcss/src/utils/is_color.rs:207-212 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rust-plugins/docs-seo/src/lib.rs:37— rust-plugins/docs-seo/src/lib.rs:37-42 | rust-plugins/docs-snapshot/src/lib.rs:102-107 — 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 (21 lines × 2) rust-ecosystem/docs-seo/src/lib.rs:203— rust-ecosystem/docs-seo/src/lib.rs:203-223 | rust-ecosystem/docs-seo/src/syndication.rs:49-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-seo/src/lib.rs:203` 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 (21 lines × 2) rust-plugins/auto-import/src/lib.rs:57— rust-plugins/auto-import/src/lib.rs:57-77 | rust-plugins/react-components/src/lib.rs:73-93 — 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 (21 lines × 2) rust-plugins/icons/src/loader/svg_builder.rs:82— rust-plugins/icons/src/loader/svg_builder.rs:82-102 | rust-plugins/svgr/src/svg_builder.rs:95-115 — before extracting anything, compare `rust-plugins/icons/src/loader/svg_builder.rs` and `rust-plugins/svgr/src/svg_builder.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 6 locations) crates/create-farm-rs/templates/electron/preact/electron/preload.ts:4— crates/create-farm-rs/templates/electron/preact/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/react/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/solid/electron/preload.ts:4 · crates/create-farm-rs/templates/electron/svelte/electron/preload.ts:4 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (18 lines × 6 locations) crates/create-farm-rs/templates/electron/preact/forge.config.cjs:13— crates/create-farm-rs/templates/electron/preact/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/react/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/solid/forge.config.cjs:13 · crates/create-farm-rs/templates/electron/svelte/forge.config.cjs:13 · +2 more site(s) not listed — the 6 copies are spread across 6 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 6 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 (18 lines × 6 locations) packages/core/src/plugin/js/js-plugin-schema.ts:256— packages/core/src/plugin/js/js-plugin-schema.ts:256 · packages/core/src/plugin/js/js-plugin-schema.ts:275 · packages/core/src/plugin/js/js-plugin-schema.ts:294 · packages/core/src/plugin/js/js-plugin-schema.ts:313 · +2 more site(s) not listed — all 6 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.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×3
Duplicated block with local edits (18 matched lines × 2 locations) crates/create-farm-rs/templates/electron/solid/farm.config.ts:3— crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 · crates/create-farm-rs/templates/electron/svelte/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (18 matched lines × 2 locations) crates/create-farm-rs/templates/electron/solid/farm.config.ts:3— crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 · crates/create-farm-rs/templates/electron/vue/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (18 matched lines × 2 locations) packages/core/src/server/index.ts:443— packages/core/src/server/index.ts:443 · packages/core/src/watcher/index.ts:299 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Unlisted import 'react-router' examples/rust-plugin-auto-import-react/auto_import.d.ts:18— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'react-router' examples/rust-plugin-auto-import-vue/src/types/auto_import.d.ts:6— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'react-router' rust-plugins/auto-import/playground-vue/src/types/auto_import.d.ts:4— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Low contrast colour pair in CSS (1.8:1) .agents/skills/brainstorming/scripts/frame-template.html:180— `.placeholder` sets color: #aeaeb2 on background-color: #e5e5e7 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.8:1) .claude/skills/brainstorming/scripts/frame-template.html:180— `.placeholder` sets color: #aeaeb2 on background-color: #e5e5e7 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.9:1) packages/docs-theme-default/src/style.css:110— `.farm-docs-navbar > .farm-docs-search-trigger` sets color: #b2acbd on background-color: #ebedf0 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.9:1) packages/docs-theme-default/src/style.css:180— `.farm-docs-breadcrumbs > span:last-child` sets color: #d4a1e5 on background-color: #f5f5f6 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
SfcParser::try_parse_directive (cyclomatic 82) patches/fervid_parser/src/attributes.rs:72— SfcParser::try_parse_directive has cyclomatic complexity 82 (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.
SfcParser::parse_sfc (cyclomatic 17) patches/fervid_parser/src/sfc.rs:77— SfcParser::parse_sfc 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.
farmfe_docs_config::validate::validate (cyclomatic 61) rust-ecosystem/docs-config/src/validate.rs:210— farmfe_docs_config::validate::validate has cyclomatic complexity 61 (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.
farmfe_docs_config::typescript::render (cyclomatic 28) rust-ecosystem/docs-config/src/typescript.rs:92— farmfe_docs_config::typescript::render has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs (cyclomatic 42) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:217— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_unresolved_import_dfs (cyclomatic 20) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:546— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_unresolved_import_dfs 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.
farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements (cyclomatic 35) crates/plugin_tree_shake/src/tree_shake_modules.rs:314— farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_used_statements (cyclomatic 17) crates/plugin_tree_shake/src/tree_shake_modules.rs:211— farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_used_statements 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.
SideEffectsAnalyzer::visit_expr (cyclomatic 32) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:434— SideEffectsAnalyzer::visit_expr has cyclomatic complexity 32 (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.
SideEffectsAnalyzer::visit_class (cyclomatic 18) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:240— SideEffectsAnalyzer::visit_class 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.
Writer::element (cyclomatic 29) rust-ecosystem/docs-content/src/machine_markdown.rs:583— Writer::element has cyclomatic complexity 29 (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.
Writer::jsx (cyclomatic 22) rust-ecosystem/docs-content/src/machine_markdown.rs:490— Writer::jsx 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.
farmfe_svgr_rs::transform_svg_component::variables::get_variables (cyclomatic 28) rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:42— farmfe_svgr_rs::transform_svg_component::variables::get_variables has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_svgr_rs::hast_to_swc_ast::decode_xml::decode_xml (cyclomatic 19) rust-ecosystem/svgr-rs/src/hast_to_swc_ast/decode_xml.rs:1— farmfe_svgr_rs::hast_to_swc_ast::decode_xml::decode_xml has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Resolver::try_alias (cyclomatic 16) crates/plugin_resolve/src/resolver.rs:426— Resolver::try_alias 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.
Resolver::try_package_entry (cyclomatic 16) crates/plugin_resolve/src/resolver.rs:705— Resolver::try_package_entry 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.
No assertions: Binding - should parse config to rust correctly packages/core/tests/binding.spec.ts:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: recognizes a Windows Rust Vue binary path js-plugins/vuetify/src/index.spec.ts:87— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Parser::parse (cognitive 127) rust-ecosystem/tailwindcss/src/parser.rs:133— Parser::parse has cognitive complexity 127 (threshold 15). Drivers by points: if/else 37 (103 pts), boolean chains 19, match/switch 4, loops 1 (nesting depth added 66). 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.
Parser::consume_if (cognitive 21) crates/create-farm-rs/src/utils/lte.rs:301— Parser::consume_if has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (5 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SfcParser::try_parse_directive (cognitive 104) patches/fervid_parser/src/attributes.rs:72— SfcParser::try_parse_directive has cognitive complexity 104 (threshold 15). Drivers by points: if/else 28 (65 pts), match/switch 21 (35 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 52). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SfcParser::parse_sfc (cognitive 34) patches/fervid_parser/src/sfc.rs:77— SfcParser::parse_sfc has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_swc_transformer_import_glob::get_object_literal (cognitive 68) crates/swc_transformer_import_glob/src/lib.rs:1054— farmfe_swc_transformer_import_glob::get_object_literal has cognitive complexity 68 (threshold 15). Drivers by points: if/else 10 (35 pts), match/switch 7 (26 pts), loops 2 (7 pts) (nesting depth added 49). 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.
farmfe_swc_transformer_import_glob::transform_import_meta_glob_with_snapshot (cognitive 33) crates/swc_transformer_import_glob/src/lib.rs:100— farmfe_swc_transformer_import_glob::transform_import_meta_glob_with_snapshot has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TracedUsedImportStatement::from_import_info_and_used_idents (cognitive 57) crates/plugin_tree_shake/src/statement_graph/traced_used_import.rs:60— TracedUsedImportStatement::from_import_info_and_used_idents has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (40 pts), match/switch 3 (10 pts), loops 2 (7 pts) (nesting depth added 39). 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.
TracedUsedImportStatement::from_export_info_and_used_idents (cognitive 36) crates/plugin_tree_shake/src/statement_graph/traced_used_import.rs:136— TracedUsedImportStatement::from_export_info_and_used_idents has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 2 (7 pts), match/switch 1 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_svgr_rs::transform_svg_component::variables::get_variables (cognitive 56) rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:42— farmfe_svgr_rs::transform_svg_component::variables::get_variables has cognitive complexity 56 (threshold 15). Drivers by points: if/else 27 (48 pts), loops 1 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_svgr_rs::hast_to_swc_ast::decode_xml::decode_xml (cognitive 34) rust-ecosystem/svgr-rs/src/hast_to_swc_ast/decode_xml.rs:1— farmfe_svgr_rs::hast_to_swc_ast::decode_xml::decode_xml has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 2 (6 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_docs_snapshot::verify::verify_build (cognitive 53) rust-ecosystem/docs-snapshot/src/verify.rs:340— farmfe_docs_snapshot::verify::verify_build has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (34 pts), loops 7 (14 pts), boolean chains 5 (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.
farmfe_docs_snapshot::observations::validate_observation_scope (cognitive 19) rust-ecosystem/docs-snapshot/src/observations.rs:9— farmfe_docs_snapshot::observations::validate_observation_scope has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (5 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.
SideEffectsAnalyzer::visit_expr (cognitive 43) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:434— SideEffectsAnalyzer::visit_expr has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (28 pts), match/switch 3 (6 pts), boolean chains 5, loops 1 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SideEffectsAnalyzer::visit_class (cognitive 28) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:240— SideEffectsAnalyzer::visit_class has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Writer::jsx (cognitive 39) rust-ecosystem/docs-content/src/machine_markdown.rs:490— Writer::jsx has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 2 (4 pts), match/switch 2 (4 pts), boolean chains 3 (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.
Writer::element (cognitive 25) rust-ecosystem/docs-content/src/machine_markdown.rs:583— Writer::element has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (5 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatementGraph::traverse_dependents_dfs (cognitive 38) crates/plugin_tree_shake/src/statement_graph.rs:542— StatementGraph::traverse_dependents_dfs has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (31 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatementGraph::trace_and_mark_used_statements (cognitive 32) crates/plugin_tree_shake/src/statement_graph.rs:396— StatementGraph::trace_and_mark_used_statements has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 18). 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.
FarmPluginScript::update_modules (cognitive 33) crates/plugin_script/src/lib.rs:90— FarmPluginScript::update_modules has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 5 (11 pts), boolean chains 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.
FarmPluginScript::process_resource_pots (cognitive 22) crates/plugin_script/src/lib.rs:474— FarmPluginScript::process_resource_pots has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 2 (5 pts), boolean chains 1 (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.
farmfe_plugin_docs::html_template::order_page_styles (cognitive 28) rust-plugins/docs/src/html_template.rs:19— farmfe_plugin_docs::html_template::order_page_styles has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 5, match/switch 3, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_docs::page_resources::collect (cognitive 16) rust-plugins/docs/src/page_resources.rs:28— farmfe_plugin_docs::page_resources::collect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 3 (6 pts), match/switch 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_vue::list_blocks::normalize_vue_code (cognitive 23) rust-plugins/vue/src/list_blocks.rs:203— farmfe_plugin_vue::list_blocks::normalize_vue_code has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, loops 3 (5 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.
farmfe_plugin_vue::list_blocks::helpers (cognitive 18) rust-plugins/vue/src/list_blocks.rs:18— farmfe_plugin_vue::list_blocks::helpers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 1 (5 pts), loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_html::deps_analyzer::get_script_src_or_code (cognitive 20) crates/plugin_html/src/deps_analyzer.rs:108— farmfe_plugin_html::deps_analyzer::get_script_src_or_code has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (20 pts) (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. This shape REPEATS in the file: one other method here (farmfe_plugin_html::deps_analyzer::get_href_link_or_code) 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.
farmfe_plugin_html::deps_analyzer::get_href_link_or_code (cognitive 20) crates/plugin_html/src/deps_analyzer.rs:167— farmfe_plugin_html::deps_analyzer::get_href_link_or_code has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (20 pts) (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. This shape REPEATS in the file: one other method here (farmfe_plugin_html::deps_analyzer::get_script_src_or_code) 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.
Builder::autogenerated (cognitive 19) rust-ecosystem/docs-plan/src/sidebars.rs:101— Builder::autogenerated has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Builder::items (cognitive 16) rust-ecosystem/docs-plan/src/sidebars.rs:171— Builder::items has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_library::replace_internal_import_sources_with_placeholders (cognitive 18) crates/plugin_library/src/lib.rs:442— farmfe_plugin_library::replace_internal_import_sources_with_placeholders has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (2 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.
farmfe_plugin_library::utils::strip_runtime_module_helper_import (cognitive 16) crates/plugin_library/src/utils.rs:107— farmfe_plugin_library::utils::strip_runtime_module_helper_import has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 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.
TooManyFunctions: create_farm::utils::colors crates/create-farm-rs/src/utils/colors.rs:16— TooManyFunctions — 37 free functions. The bar is 30 free functions; this is 7 over it, 1.23× 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.
TooManyFunctions: farmfe_ecosystem_tailwindcss::utils::infer_data_type rust-ecosystem/tailwindcss/src/utils/infer_data_type.rs:35— TooManyFunctions — 32 free functions. The bar is 30 free functions; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×2
Edited copy of a member (52 corresponding lines) rust-ecosystem/docs-plan/src/brand_home.rs:20— rust-ecosystem/docs-plan/src/brand_home.rs:20-71 | rust-ecosystem/docs-plan/src/brand_home.rs:78-142 — These two members are one piece of code written twice and then edited apart: 52 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 (52 corresponding lines) rust-ecosystem/syntax-highlight/src/editor_theme.rs:13— rust-ecosystem/syntax-highlight/src/editor_theme.rs:13-64 | rust-ecosystem/syntax-highlight/src/farm_theme.rs:11-67 — These two members are one piece of code written twice and then edited apart: 52 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 (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) rust-plugins/auto-import/src/parser/generate_dts.rs:55— rust-plugins/auto-import/src/parser/generate_dts.rs:55-93 | rust-plugins/react-components/src/generate_dts.rs:55-96 — These two members are one piece of code written twice and then edited apart: 39 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 (39 corresponding lines) crates/node/src/plugin_adapters/js_plugin_adapter/hooks/freeze_module.rs:37— crates/node/src/plugin_adapters/js_plugin_adapter/hooks/freeze_module.rs:37-79 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/process_module.rs:38-76 — These two members are one piece of code written twice and then edited apart: 39 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 (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) crates/toolkit/src/script/module2cjs.rs:940— crates/toolkit/src/script/module2cjs.rs:940-983 | crates/toolkit/src/script/module2cjs.rs:992-1032 — These two members are one piece of code written twice and then edited apart: 41 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 (41 corresponding lines) crates/compiler/src/build/mod.rs:538— crates/compiler/src/build/mod.rs:538-580 | crates/compiler/src/update/mod.rs:765-805 — These two members are one piece of code written twice and then edited apart: 41 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) rust-ecosystem/docs-content/src/machine_markdown.rs:268— rust-ecosystem/docs-content/src/machine_markdown.rs:268-294 | rust-plugins/docs-snippets/src/transform/values.rs:45-71 — 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/core/src/module/module_graph.rs:390— crates/core/src/module/module_graph.rs:390-417 | crates/core/src/module/module_graph.rs:445-471 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) rust-ecosystem/tailwindcss/src/compiler.rs:406— rust-ecosystem/tailwindcss/src/compiler.rs:406-429 | rust-ecosystem/tailwindcss/src/compiler.rs:514-542 — 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/compiler/src/build/load.rs:13— crates/compiler/src/build/load.rs:13-39 | crates/compiler/src/build/parse.rs:14-37 — 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 copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1446— rust-ecosystem/tailwindcss/src/utilities.rs:1446-1463 | rust-ecosystem/tailwindcss/src/utilities.rs:1488-1498 | rust-ecosystem/tailwindcss/src/utilities.rs:1499-1509 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) crates/plugin_tree_shake/src/statement_graph.rs:317— crates/plugin_tree_shake/src/statement_graph.rs:317-328 | crates/plugin_tree_shake/src/statement_graph.rs:330-341 | crates/plugin_tree_shake/src/statement_graph.rs:351-361 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) crates/create-farm-rs/src/utils/theme.rs:301— crates/create-farm-rs/src/utils/theme.rs:301-322 | crates/create-farm-rs/src/utils/theme.rs:331-348 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/core/src/module/module_graph.rs:242— crates/core/src/module/module_graph.rs:242-259 | crates/core/src/module/module_graph.rs:561-578 — 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 copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) crates/toolkit/src/script/concatenate_modules/utils.rs:38— crates/toolkit/src/script/concatenate_modules/utils.rs:38-54 | crates/toolkit/src/script/module2cjs.rs:846-862 — 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) rust-plugins/auto-import/src/parser/parse.rs:456— rust-plugins/auto-import/src/parser/parse.rs:456-474 | rust-plugins/auto-import/src/parser/parse.rs:496-512 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1249— rust-ecosystem/tailwindcss/src/utilities.rs:1249-1258 | rust-ecosystem/tailwindcss/src/utilities.rs:1280-1292 | rust-ecosystem/tailwindcss/src/utilities.rs:1293-1302 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) crates/core/src/module/module_group.rs:162— crates/core/src/module/module_group.rs:162-171 | crates/core/src/module/module_group.rs:173-182 | crates/core/src/module/module_group.rs:184-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) rust-ecosystem/tailwindcss/src/utils/dimensions.rs:19— rust-ecosystem/tailwindcss/src/utils/dimensions.rs:19-22 | rust-ecosystem/tailwindcss/src/utils/infer_data_type.rs:73-76 | rust-ecosystem/tailwindcss/src/utils/replace_shadow_colors.rs:18-21 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) crates/core/src/module/mod.rs:148— crates/core/src/module/mod.rs:148-151 | crates/core/src/resource/mod.rs:49-52 | crates/core/src/resource/resource_pot.rs:160-163 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (23 lines × 2) rust-ecosystem/tailwindcss-node/src/resolve.rs:122— rust-ecosystem/tailwindcss-node/src/resolve.rs:122-144 | rust-ecosystem/tailwindcss-node/src/resolve.rs:156-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 (23 lines × 2) rust-plugins/auto-import/src/parser/generate_dts.rs:71— rust-plugins/auto-import/src/parser/generate_dts.rs:71-93 | rust-plugins/react-components/src/generate_dts.rs:74-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/auto-import/src/parser/generate_dts.rs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) crates/compiler/src/build/mod.rs:708— crates/compiler/src/build/mod.rs:708-724 | crates/compiler/src/update/mod.rs:1044-1060 — `crates/compiler/src/build/mod.rs` and `crates/compiler/src/update/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/compiler/src/build/mod.rs:708` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:204— rust-plugins/vue-jsx/src/resolve_type.rs:204-220 | rust-plugins/vue-jsx/src/resolve_type.rs:236-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:204` 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 (16 lines × 2) crates/compiler/src/build/mod.rs:169— crates/compiler/src/build/mod.rs:169-184 | crates/compiler/src/update/mod.rs:483-498 — `crates/compiler/src/build/mod.rs` and `crates/compiler/src/update/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/compiler/src/build/mod.rs:169` 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 (16 lines × 2) rust-ecosystem/tailwindcss/src/design_system.rs:194— rust-ecosystem/tailwindcss/src/design_system.rs:194-209 | rust-ecosystem/tailwindcss/src/design_system.rs:238-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/design_system.rs:194` 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–16 lines × 2) rust-plugins/react-components/src/find_local_components.rs:104— rust-plugins/react-components/src/find_local_components.rs:104-118 | rust-plugins/react-components/src/find_local_components.rs:124-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 2) rust-plugins/react-components/src/lib.rs:193— rust-plugins/react-components/src/lib.rs:193-208 | rust-plugins/strip/src/lib.rs:131-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/react-components/src/lib.rs:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) crates/plugin_css/src/lib.rs:671— crates/plugin_css/src/lib.rs:671-680 | crates/plugin_script/src/lib.rs:760-767 — 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/plugin_css/src/lib.rs:671` 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 before the matched lines, `crates/plugin_script/src/lib.rs:758` calls `trace_module_sourcemap` and `crates/plugin_css/src/lib.rs:671` 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–10 lines × 2) scripts/release-npm-best-effort.py:206— scripts/release-npm-best-effort.py:206-215 | scripts/release-npm-version-presence.py:112-119 — 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 (28 lines × 2 locations) crates/create-farm-rs/templates/electron/solid/src/App.tsx:6— crates/create-farm-rs/templates/electron/solid/src/App.tsx:6 · crates/create-farm-rs/templates/solid/src/App.tsx:6 — 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 × 2 locations) packages/core/binding/resolve-binding.cjs:169— packages/core/binding/resolve-binding.cjs:169 · packages/core/binding/resolve-binding.cjs:200 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×2
Duplicated block with local edits (17 matched lines × 2 locations) crates/create-farm-rs/templates/electron/preact/farm.config.ts:3— crates/create-farm-rs/templates/electron/preact/farm.config.ts:3 · crates/create-farm-rs/templates/electron/solid/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (17 matched lines × 2 locations) crates/create-farm-rs/templates/electron/preact/farm.config.ts:3— crates/create-farm-rs/templates/electron/preact/farm.config.ts:3 · crates/create-farm-rs/templates/electron/svelte/farm.config.ts:3 — the two spans are one implementation copied and then locally edited — 51 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.
Dead file (~60 LoC) examples/arco-pro/src/pages/visualization/multi-dimension-data-analysis/utils/map.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~60 LoC) js-plugins/visualizer/src/client/src/components/ModuleList.vue— no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (js-plugins/visualizer/src/client/src/pages/analysis/Module.vue) — 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 (~41 LoC) examples/arco-pro/src/components/PermissionWrapper/index.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~41 LoC) examples/arco-pro/src/utils/clipboard.ts— no import path from any entry point (565 application, 396 tooling, 525 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'react-refresh' — Declared in crates/create-farm-rs/templates/react/REDACTED but never imported anywhere in that package or its workspace members — while rust-plugins/react/src/is_react_refresh_boundary.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency 'react-refresh' — Declared in crates/create-farm-rs/templates/tauri/react/REDACTED but never imported anywhere in that package or its workspace members — while rust-plugins/react/src/is_react_refresh_boundary.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency 'solid-refresh' — Declared in crates/create-farm-rs/templates/solid/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'solid-refresh' — Declared in crates/create-farm-rs/templates/tauri/solid/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Low contrast colour pair in CSS (1.6:1) packages/runtime-plugin-hmr/src/overlay.ts:42— `.window` sets color: #ccc on background-color: #ffffff — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.8:1) examples/vue/src/views/HomeView.vue:43— `.jsx-card button` sets color: #fff on background-color: #40916c — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) examples/commerce-lab/apps/admin/styles/workspace.scss:40— `&-draft, &-refunded` sets color: #8a7250 on background-color: #f2ede3 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
content-tabs.Tabs (cyclomatic 71) packages/docs/src/content-tabs.tsx:12— content-tabs.Tabs has cyclomatic complexity 71 (threshold 15). Of this number, 25 points are the body's own statements and 46 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Parser::parse (cyclomatic 60) rust-ecosystem/tailwindcss/src/parser.rs:133— Parser::parse has cyclomatic complexity 60 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
workflow.run (cyclomatic 57) packages/docs/src/workflow.ts:251— workflow.run has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 8 of the 57 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 362, 330, 558, …). 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.
proxy.proxyMiddleware (cyclomatic 56) REDACTED:28— proxy.proxyMiddleware has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 13 of the 56 points are its own statements and the rest belongs to 11 function items inside it that branch (upgrade, dispose, middleware, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
machine-readable.validateMachineReadableResources (cyclomatic 56) packages/docs/src/machine-readable.ts:111— machine-readable.validateMachineReadableResources has cyclomatic complexity 56 (threshold 15). Of this number, 41 points are the body's own statements and 15 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
code-block-metadata.rewriteOwnedPreMetadata (cyclomatic 54) packages/docs/src/code-block-metadata.ts:117— code-block-metadata.rewriteOwnedPreMetadata has cyclomatic complexity 54 (threshold 15). Of this number, 52 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolve-binding.resolveNativeBindingPath (cyclomatic 50) packages/core/binding/resolve-binding.cjs:3— resolve-binding.resolveNativeBindingPath has cyclomatic complexity 50 (threshold 15). Of this number, 47 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Index::resolve_inner (cyclomatic 46) rust-ecosystem/docs-plan/src/links.rs:201— Index::resolve_inner has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
search.AlgoliaSearch (cyclomatic 42) packages/docs-theme-default/src/search.tsx:9— search.AlgoliaSearch has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 11 of the 42 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 52, a function literal at line 64, a function literal at line 44, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
preview.artifacts (cyclomatic 41) packages/docs/src/preview.ts:102— preview.artifacts has cyclomatic complexity 41 (threshold 15). Of this number, 19 points are the body's own statements and 22 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.farmPlugin (cyclomatic 38) REDACTED:102— index.farmPlugin has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
development.startDocsDevelopment (cyclomatic 38) packages/docs/src/development.ts:110— development.startDocsDevelopment has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 206, create, origin, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TokenColors::apply (cyclomatic 37) rust-ecosystem/syntax-highlight/src/theme_config.rs:62— TokenColors::apply has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farm-to-vite-config.viteConfigToFarmConfig (cyclomatic 36) packages/core/src/plugin/js/farm-to-vite-config.ts:321— farm-to-vite-config.viteConfigToFarmConfig has cyclomatic complexity 36 (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.
index.MobileNavigation (cyclomatic 36) packages/docs-theme-default/src/index.tsx:42— index.MobileNavigation has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 91, a function literal at line 81, a function literal at line 84, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
normalize-persistent-cache.normalizePersistentCache (cyclomatic 35) packages/core/src/config/normalize-config/normalize-persistent-cache.ts:21— normalize-persistent-cache.normalizePersistentCache has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HmrClient.applyHotUpdates (cyclomatic 35) REDACTED:231— HmrClient.applyHotUpdates has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
diagram-viewer.DiagramViewer (cyclomatic 34) packages/docs-theme-default/src/diagram-viewer.tsx:4— diagram-viewer.DiagramViewer has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 15, 48, 52, …). 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.
output-transaction.recover (cyclomatic 34) packages/docs/src/output-transaction.ts:181— output-transaction.recover has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
code-block-metadata.tagAt (cyclomatic 32) packages/docs/src/code-block-metadata.ts:42— code-block-metadata.tagAt has cyclomatic complexity 32 (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.
ExportsVisitor::visit_module_decl (cyclomatic 31) rust-plugins/auto-import/src/parser/parse.rs:170— ExportsVisitor::visit_module_decl has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_vue_jsx::hmr::inject (cyclomatic 31) rust-plugins/vue-jsx/src/hmr.rs:8— farmfe_plugin_vue_jsx::hmr::inject has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_docs_snapshot::verify::verify_build (cyclomatic 30) rust-ecosystem/docs-snapshot/src/verify.rs:340— farmfe_docs_snapshot::verify::verify_build 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.
WsServer.createWebSocketServer (cyclomatic 30) packages/core/src/server/ws.ts:177— WsServer.createWebSocketServer has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 262, 200, 303, …). 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.
output-transaction.withOutputTransaction (cyclomatic 29) packages/docs/src/output-transaction.ts:305— output-transaction.withOutputTransaction has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_modular_import::transform::rewrite_imports (cyclomatic 28) rust-plugins/modular-import/src/transform.rs:43— farmfe_plugin_modular_import::transform::rewrite_imports has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.tailwindcss (cyclomatic 27) js-plugins/tailwindcss/src/index.ts:35— index.tailwindcss has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
output-transaction.validRecord (cyclomatic 27) packages/docs/src/output-transaction.ts:78— output-transaction.validRecord has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
copy-artifacts.sameArtifact (cyclomatic 25) packages/plugin-tools/src/copy-artifacts.ts:4— copy-artifacts.sameArtifact has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
prepare.preparePlatformPackages (cyclomatic 25) packages/plugin-tools/src/prepare.ts:5— prepare.preparePlatformPackages has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_swc_transformer_import_glob::get_object_literal (cyclomatic 24) crates/swc_transformer_import_glob/src/lib.rs:1054— farmfe_swc_transformer_import_glob::get_object_literal 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.
index.farmPlugin (cyclomatic 24) js-plugins/copy/src/index.ts:116— index.farmPlugin has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 133, 217). 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.
HmrEngine.drainWatchUpdates (cyclomatic 24) packages/core/src/server/hmr-engine.ts:204— HmrEngine.drainWatchUpdates has cyclomatic complexity 24 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
create_farm::run_cli (cyclomatic 23) crates/create-farm-rs/src/lib.rs:29— create_farm::run_cli has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.proxyContext (cyclomatic 23) packages/core/src/plugin/index.ts:163— index.proxyContext has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 211, a function literal at line 249, proxyHookCallback::tryProxyMethod, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.BlogPage (cyclomatic 22) packages/docs-theme-default/src/index.tsx:189— index.BlogPage has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to 7 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Server.#createWatcher (cyclomatic 21) packages/core/src/server/index.ts:330— Server.#createWatcher has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 344, a function literal at line 385, a function literal at line 367, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ssg-pool.renderPages (cyclomatic 21) packages/docs/src/ssg-pool.ts:31— ssg-pool.renderPages has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ssg-pool.renderPages::receive) 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.
SourceObservationLedger::verify_snapshot (cyclomatic 20) crates/core/src/context/source_observation.rs:428— SourceObservationLedger::verify_snapshot has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TreeShakeModule::used_exports_idents_to_statement_idents (cyclomatic 20) crates/plugin_tree_shake/src/module.rs:335— TreeShakeModule::used_exports_idents_to_statement_idents 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.
Registry::resolve (cyclomatic 20) rust-ecosystem/docs-plan/src/assets.rs:96— Registry::resolve 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.
UtilityRegistry::generate_with_variants (cyclomatic 20) rust-ecosystem/tailwindcss/src/utilities.rs:499— UtilityRegistry::generate_with_variants 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.
farmfe_plugin_docs::html_template::order_page_styles (cyclomatic 20) rust-plugins/docs/src/html_template.rs:19— farmfe_plugin_docs::html_template::order_page_styles 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.
farmfe_plugin_icons::loader::icon_to_svg::icon_to_svg (cyclomatic 20) rust-plugins/icons/src/loader/icon_to_svg.rs:38— farmfe_plugin_icons::loader::icon_to_svg::icon_to_svg has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Server.#initializeMiddlewares (cyclomatic 20) packages/core/src/server/index.ts:925— Server.#initializeMiddlewares has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
browser-runtime-core.BrowserRuntime::commit (cyclomatic 20) packages/docs/src/browser-runtime-core.tsx:194— browser-runtime-core.BrowserRuntime::commit has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ssg-pool.renderPages::receive (cyclomatic 20) packages/docs/src/ssg-pool.ts:101— ssg-pool.renderPages::receive has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (ssg-pool.renderPages) 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.
module-system.farmRequire (cyclomatic 20) packages/runtime/src/module-system.ts:153— module-system.farmRequire has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farmfe_plugin_runtime::handle_entry_resources::create_export_info_code (cyclomatic 19) crates/plugin_runtime/src/handle_entry_resources.rs:219— farmfe_plugin_runtime::handle_entry_resources::create_export_info_code has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
normalize-resolvers.normalizeResolverDeclarations::visit (cyclomatic 19) js-plugins/vuetify/src/normalize-resolvers.ts:16— normalize-resolvers.normalizeResolverDeclarations::visit has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ImportMetaURLVisitor::transform_url (cyclomatic 18) crates/plugin_script/src/transform_import_meta_url/mod.rs:95— ImportMetaURLVisitor::transform_url 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.
FarmPluginDocsSnapshot::build_start (cyclomatic 18) rust-plugins/docs-snapshot/src/lib.rs:336— FarmPluginDocsSnapshot::build_start 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.
Inspector::visit_jsx_element (cyclomatic 18) rust-plugins/docs-snippets/src/inventory.rs:140— Inspector::visit_jsx_element 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.
htmlFallback.htmlFallbackMiddleware.htmlFallbackMiddleware (cyclomatic 18) packages/core/src/server/middlewares/htmlFallback.ts:9— htmlFallback.htmlFallbackMiddleware.htmlFallbackMiddleware 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.
index.convertPluginVite (cyclomatic 18) packages/core/src/plugin/js/index.ts:160— index.convertPluginVite 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.
prepare-sdk-types.prepareSdkTypes (cyclomatic 18) packages/core/scripts/prepare-sdk-types.mjs:41— prepare-sdk-types.prepareSdkTypes has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (visit). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
search-query.resultsFrom (cyclomatic 18) packages/docs-theme-default/src/search-query.ts:13— search-query.resultsFrom has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 21, 50). 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.
dev-client.mount (cyclomatic 18) packages/docs/src/dev-client.tsx:19— dev-client.mount has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 43, 65). 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.
module-helper.interopRequireWildcard (cyclomatic 18) packages/runtime/src/modules/module-helper.ts:81— module-helper.interopRequireWildcard 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.
FarmPluginRuntime::generate_resources (cyclomatic 17) crates/plugin_runtime/src/lib.rs:352— FarmPluginRuntime::generate_resources 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.
farmfe_ecosystem_tailwindcss_node::resolve::resolve_with_extensions (cyclomatic 17) rust-ecosystem/tailwindcss-node/src/resolve.rs:105— farmfe_ecosystem_tailwindcss_node::resolve::resolve_with_extensions 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.
farmfe_plugin_vue::list_blocks::normalize_vue_code (cyclomatic 17) rust-plugins/vue/src/list_blocks.rs:203— farmfe_plugin_vue::list_blocks::normalize_vue_code 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.
utils.getResolvedOptions (cyclomatic 17) js-plugins/dts/src/utils.ts:116— utils.getResolvedOptions 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.
index.farmPostcssPlugin (cyclomatic 17) js-plugins/postcss/src/index.ts:31— index.farmPostcssPlugin has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
farm-to-vite-context.farmContextToViteContext (cyclomatic 17) packages/core/src/plugin/js/farm-to-vite-context.ts:10— farm-to-vite-context.farmContextToViteContext has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 129, a function literal at line 49, a function literal at line 73, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
normalize-output.normalizeTargetEnv (cyclomatic 17) packages/core/src/config/normalize-config/normalize-output.ts:141— normalize-output.normalizeTargetEnv 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.
index.normalizeUserCompilationConfig (cyclomatic 17) packages/core/src/config/normalize-config/index.ts:43— index.normalizeUserCompilationConfig 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.
merge-config.mergeFarmCliConfig (cyclomatic 17) packages/core/src/config/merge-config.ts:48— merge-config.mergeFarmCliConfig has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
code-block.CodeBlock (cyclomatic 17) packages/docs/src/code-block.tsx:12— code-block.CodeBlock has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Compiler::update_with_completion (cyclomatic 16) crates/compiler/src/update/mod.rs:398— Compiler::update_with_completion has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Lexer::next (cyclomatic 16) crates/create-farm-rs/src/utils/lte.rs:116— Lexer::next 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.
farmfe_plugin_partial_bundling::merge_module_pots::handle_enforce_target_min_size (cyclomatic 16) crates/plugin_partial_bundling/src/merge_module_pots.rs:339— farmfe_plugin_partial_bundling::merge_module_pots::handle_enforce_target_min_size 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.
farmfe_plugin_resolve::resolver::exports::walk (cyclomatic 16) crates/plugin_resolve/src/resolver/exports.rs:288— farmfe_plugin_resolve::resolver::exports::walk 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.
FeaturesAnalyzer::analyze (cyclomatic 16) crates/plugin_script_meta/src/plugin_features/features_analyzer.rs:71— FeaturesAnalyzer::analyze 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.
TracedUsedImportStatement::from_import_info_and_used_idents (cyclomatic 16) crates/plugin_tree_shake/src/statement_graph/traced_used_import.rs:60— TracedUsedImportStatement::from_import_info_and_used_idents 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.
RuntimeFeatureGuardRemover::handle_stmt (cyclomatic 16) crates/toolkit/src/runtime.rs:60— RuntimeFeatureGuardRemover::handle_stmt 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.
Root.generate (cyclomatic 16) js-plugins/tailwindcss/src/index.ts:354— Root.generate has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
navigation.NavigationMenu (cyclomatic 16) packages/docs-theme-default/src/navigation.tsx:12— navigation.NavigationMenu has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 21, 15, 14, …). 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.
page-loader-core.createPageLoader.reconcile (cyclomatic 16) packages/docs/src/page-loader-core.ts:42— page-loader-core.createPageLoader.reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
preview.startDocsPreview::serve (cyclomatic 16) packages/docs/src/preview.ts:293— preview.startDocsPreview::serve 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.
theme.resolveTheme (cyclomatic 16) packages/docs/src/theme.ts:52— theme.resolveTheme 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.
HmrClient.handleControlledFarmUpdate (cyclomatic 16) REDACTED:97— HmrClient.handleControlledFarmUpdate 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.
resolve-binding.resolveNativeBindingPath (cognitive 123) packages/core/binding/resolve-binding.cjs:3— resolve-binding.resolveNativeBindingPath has cognitive complexity 123 (threshold 15). Drivers by points: if/else 35 (69 pts), error handling 14 (44 pts), match/switch 5 (9 pts), boolean chains 1 (nesting depth added 68). Of this number, 118 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
code-block-metadata.rewriteOwnedPreMetadata (cognitive 87) packages/docs/src/code-block-metadata.ts:117— code-block-metadata.rewriteOwnedPreMetadata has cognitive complexity 87 (threshold 15). Drivers by points: if/else 29 (65 pts), boolean chains 13, loops 3 (5 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 39). Of this number, 86 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HmrClient.applyHotUpdates (cognitive 84) REDACTED:231— HmrClient.applyHotUpdates has cognitive complexity 84 (threshold 15). Drivers by points: if/else 15 (44 pts), loops 14 (26 pts), error handling 3 (7 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 49). Of this number, 81 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.proxyContext (cognitive 80) packages/core/src/plugin/index.ts:163— index.proxyContext has cognitive complexity 80 (threshold 15). Drivers by points: if/else 10 (54 pts), ternaries 3 (16 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 58). Most of this is not in the body itself: 14 of the 80 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 211, a function literal at line 249, proxyHookCallback::tryProxyMethod, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
content-tabs.Tabs (cognitive 79) packages/docs/src/content-tabs.tsx:12— content-tabs.Tabs has cognitive complexity 79 (threshold 15). Drivers by points: if/else 29 (35 pts), boolean chains 19, ternaries 13 (16 pts), error handling 4 (8 pts), loops 1 (nesting depth added 13). Of this number, 20 points are the body's own statements and 59 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
farm-to-vite-config.viteConfigToFarmConfig (cognitive 74) packages/core/src/plugin/js/farm-to-vite-config.ts:321— farm-to-vite-config.viteConfigToFarmConfig has cognitive complexity 74 (threshold 15). Drivers by points: if/else 25 (50 pts), loops 3 (14 pts), ternaries 1 (6 pts), boolean chains 4 (nesting depth added 41). 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.
Index::resolve_inner (cognitive 72) rust-ecosystem/docs-plan/src/links.rs:201— Index::resolve_inner has cognitive complexity 72 (threshold 15). Drivers by points: if/else 32 (54 pts), boolean chains 15, loops 1 (3 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.
workflow.run (cognitive 71) packages/docs/src/workflow.ts:251— workflow.run has cognitive complexity 71 (threshold 15). Drivers by points: if/else 27 (41 pts), boolean chains 12, loops 6 (8 pts), ternaries 7 (8 pts), error handling 1 (2 pts) (nesting depth added 18). Most of this is not in the body itself: 8 of the 71 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 330, 362, 558, …). 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.
code-block-metadata.tagAt (cognitive 63) packages/docs/src/code-block-metadata.ts:42— code-block-metadata.tagAt has cognitive complexity 63 (threshold 15). Drivers by points: if/else 15 (37 pts), loops 8 (19 pts), boolean chains 7 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HmrEngine.drainWatchUpdates (cognitive 61) packages/core/src/server/hmr-engine.ts:204— HmrEngine.drainWatchUpdates has cognitive complexity 61 (threshold 15). Drivers by points: loops 10 (29 pts), if/else 8 (18 pts), error handling 4 (11 pts), ternaries 1 (3 pts) (nesting depth added 38). 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.
Inspector::visit_jsx_element (cognitive 59) rust-plugins/docs-snippets/src/inventory.rs:140— Inspector::visit_jsx_element has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (32 pts), match/switch 4 (20 pts), loops 2 (7 pts) (nesting depth added 43). 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.
normalize-persistent-cache.normalizePersistentCache (cognitive 59) packages/core/src/config/normalize-config/normalize-persistent-cache.ts:21— normalize-persistent-cache.normalizePersistentCache has cognitive complexity 59 (threshold 15). Drivers by points: if/else 22 (37 pts), loops 4 (10 pts), boolean chains 6, error handling 1 (4 pts), ternaries 1 (2 pts) (nesting depth added 25). Of this number, 58 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeShakeModule::used_exports_idents_to_statement_idents (cognitive 55) crates/plugin_tree_shake/src/module.rs:335— TreeShakeModule::used_exports_idents_to_statement_idents has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (40 pts), loops 3 (9 pts), match/switch 2 (6 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TokenColors::apply (cognitive 55) rust-ecosystem/syntax-highlight/src/theme_config.rs:62— TokenColors::apply has cognitive complexity 55 (threshold 15). Drivers by points: if/else 34 (52 pts), loops 2 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_modular_import::transform::rewrite_imports (cognitive 52) rust-plugins/modular-import/src/transform.rs:43— farmfe_plugin_modular_import::transform::rewrite_imports has cognitive complexity 52 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 4 (13 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ssg-pool.renderPages (cognitive 49) packages/docs/src/ssg-pool.ts:31— ssg-pool.renderPages has cognitive complexity 49 (threshold 15). Drivers by points: if/else 24 (25 pts), ternaries 7 (10 pts), boolean chains 8, loops 3 (4 pts), error handling 2 (nesting depth added 5). Of this number, 17 points are the body's own statements and 32 belong to 8 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.farmPlugin (cognitive 48) js-plugins/copy/src/index.ts:116— index.farmPlugin has cognitive complexity 48 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 3 (8 pts), boolean chains 5, ternaries 1 (5 pts) (nesting depth added 25). None of this is in the body itself: all 48 points belong to 2 function literals inside it that branch (lines 133, 217). 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.
ExportsVisitor::visit_module_decl (cognitive 47) rust-plugins/auto-import/src/parser/parse.rs:170— ExportsVisitor::visit_module_decl has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (29 pts), match/switch 7 (16 pts), loops 1 (2 pts) (nesting depth added 25). 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.
search.AlgoliaSearch (cognitive 47) packages/docs-theme-default/src/search.tsx:9— search.AlgoliaSearch has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 8 (19 pts), if/else 12 (15 pts), boolean chains 13 (nesting depth added 14). Of this number, 16 points are the body's own statements and 31 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeFeatureGuardRemover::handle_stmt (cognitive 46) crates/toolkit/src/runtime.rs:60— RuntimeFeatureGuardRemover::handle_stmt has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (37 pts), match/switch 2 (7 pts), boolean chains 2 (nesting depth added 29). 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.
output-transaction.recover (cognitive 45) packages/docs/src/output-transaction.ts:181— output-transaction.recover has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 13, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FeaturesAnalyzer::analyze (cognitive 41) crates/plugin_script_meta/src/plugin_features/features_analyzer.rs:71— FeaturesAnalyzer::analyze has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (34 pts), loops 3 (7 pts) (nesting depth added 25). 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.
index.farmPlugin (cognitive 40) REDACTED:102— index.farmPlugin has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 15, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ImportMetaURLVisitor::transform_url (cognitive 38) crates/plugin_script/src/transform_import_meta_url/mod.rs:95— ImportMetaURLVisitor::transform_url has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 2 (8 pts), boolean chains 2, match/switch 1 (2 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.
prepare.preparePlatformPackages (cognitive 38) packages/plugin-tools/src/prepare.ts:5— prepare.preparePlatformPackages has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (27 pts), loops 3 (6 pts), boolean chains 4, error handling 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.
create_farm::run_cli (cognitive 37) crates/create-farm-rs/src/lib.rs:29— create_farm::run_cli has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (26 pts), match/switch 4 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 13). Of this number, 27 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalize-output.normalizeTargetEnv (cognitive 37) packages/core/src/config/normalize-config/normalize-output.ts:141— normalize-output.normalizeTargetEnv has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (36 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
module-system.farmRequire (cognitive 35) packages/runtime/src/module-system.ts:153— module-system.farmRequire has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (30 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
machine-readable.validateMachineReadableResources (cognitive 34) packages/docs/src/machine-readable.ts:111— machine-readable.validateMachineReadableResources has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 10, loops 2 (3 pts), error handling 2 (nesting depth added 7). Of this number, 26 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
output-transaction.withOutputTransaction (cognitive 32) packages/docs/src/output-transaction.ts:305— output-transaction.withOutputTransaction has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 8 (10 pts), error handling 3 (4 pts), boolean chains 3, loops 2 (nesting depth added 10). Of this number, 30 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.tailwindcss (cognitive 31) js-plugins/tailwindcss/src/index.ts:35— index.tailwindcss has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, loops 6, ternaries 3 (4 pts), error handling 1 (3 pts) (nesting depth added 6). Of this number, 27 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HmrAcceptedVisitor::visit_mut_expr (cognitive 30) crates/plugin_runtime/src/import_meta_visitor.rs:71— HmrAcceptedVisitor::visit_mut_expr has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 1 (5 pts), boolean chains 2 (nesting depth added 18). 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.
WsServer.createWebSocketServer (cognitive 30) packages/core/src/server/ws.ts:177— WsServer.createWebSocketServer has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 11, ternaries 2, error handling 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 14 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Server.#createWatcher (cognitive 30) packages/core/src/server/index.ts:330— Server.#createWatcher has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 3 (6 pts), error handling 4 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 344, a function literal at line 367, a function literal at line 385, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
normalize-resolvers.normalizeResolverDeclarations::visit (cognitive 30) js-plugins/vuetify/src/normalize-resolvers.ts:16— normalize-resolvers.normalizeResolverDeclarations::visit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6, loops 3 (6 pts), ternaries 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UtilityRegistry::generate_with_variants (cognitive 29) rust-ecosystem/tailwindcss/src/utilities.rs:499— UtilityRegistry::generate_with_variants has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, match/switch 3 (5 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.
index.checkCompilationInputValue (cognitive 29) packages/core/src/config/normalize-config/index.ts:180— index.checkCompilationInputValue has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2 (7 pts), loops 1 (3 pts), ternaries 1 (3 pts), boolean chains 2 (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.
FarmPluginScriptMetaExports::is_import_ident_changed (cognitive 28) crates/plugin_script_meta/src/plugin_exports.rs:78— FarmPluginScriptMetaExports::is_import_ident_changed has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 2 (4 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_dts::emit_type_dependencies (cognitive 28) rust-plugins/dts/src/lib.rs:139— farmfe_plugin_dts::emit_type_dependencies has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
diagram-viewer.DiagramViewer (cognitive 28) packages/docs-theme-default/src/diagram-viewer.tsx:4— diagram-viewer.DiagramViewer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11, ternaries 9 (10 pts), boolean chains 7 (nesting depth added 1). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 15, 48, 57, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HmrClient.handleControlledFarmUpdate (cognitive 28) REDACTED:97— HmrClient.handleControlledFarmUpdate has cognitive complexity 28 (threshold 15). Drivers by points: error handling 5 (11 pts), loops 6 (10 pts), if/else 3 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginCssResolve::resolve (cognitive 27) crates/plugin_css/src/lib.rs:83— FarmPluginCssResolve::resolve has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InsertImportModifier::visit_mut_module_items (cognitive 27) rust-plugins/react-components/src/insert_import.rs:104— InsertImportModifier::visit_mut_module_items has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 5 (12 pts), loops 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.farmPostcssPlugin (cognitive 27) js-plugins/postcss/src/index.ts:31— index.farmPostcssPlugin has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (4 pts), ternaries 1 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 11). Of this number, 17 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceObservationLedger::verify_snapshot (cognitive 26) crates/core/src/context/source_observation.rs:428— SourceObservationLedger::verify_snapshot has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (8 pts), boolean chains 7, 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.
Anchors::visit_jsx_opening_element (cognitive 26) rust-ecosystem/docs-plan/src/script_pages.rs:85— Anchors::visit_jsx_opening_element has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 2 (11 pts), loops 1 (2 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ImmutableModulesMemoryStore::write_cache_with_revisions (cognitive 25) crates/core/src/cache/module_cache/immutable_modules.rs:185— ImmutableModulesMemoryStore::write_cache_with_revisions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 5 (7 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lexer::next (cognitive 25) crates/create-farm-rs/src/utils/lte.rs:116— Lexer::next has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2 (5 pts), boolean chains 3 (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.
FarmPluginDefine::transform (cognitive 25) crates/plugin_define/src/lib.rs:103— FarmPluginDefine::transform has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_resolve::resolver::exports::walk (cognitive 25) crates/plugin_resolve/src/resolver/exports.rs:288— farmfe_plugin_resolve::resolver::exports::walk has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_script::transform_import_meta_url::normalized_glob_pattern (cognitive 25) crates/plugin_script/src/transform_import_meta_url/mod.rs:16— farmfe_plugin_script::transform_import_meta_url::normalized_glob_pattern has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.MobileNavigation (cognitive 25) packages/docs-theme-default/src/index.tsx:42— index.MobileNavigation has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), ternaries 2 (3 pts) (nesting depth added 2). None of this is in the body itself: all 25 points belong to 8 function items inside it that branch (a function literal at line 91, a function literal at line 81, a function literal at line 84, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
development.startDocsDevelopment (cognitive 25) packages/docs/src/development.ts:110— development.startDocsDevelopment has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 5, ternaries 4 (5 pts), error handling 3 (nesting depth added 2). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 10 function items inside it that branch (origin, create, a function literal at line 299, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ResourcesInjector::visit_mut_element (cognitive 24) crates/plugin_html/src/resources_injector.rs:212— ResourcesInjector::visit_mut_element has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (6 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.
FarmPluginRuntime::generate_resources (cognitive 24) crates/plugin_runtime/src/lib.rs:352— FarmPluginRuntime::generate_resources has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3 (4 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginStaticAssets::transform (cognitive 24) crates/plugin_static_assets/src/lib.rs:168— FarmPluginStaticAssets::transform has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Registry::resolve (cognitive 24) rust-ecosystem/docs-plan/src/assets.rs:96— Registry::resolve has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, loops 3, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginDocsSnapshot::build_start (cognitive 24) rust-plugins/docs-snapshot/src/lib.rs:336— FarmPluginDocsSnapshot::build_start has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (6 pts), boolean chains 4, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_icons::loader::icon_to_svg::icon_to_svg (cognitive 24) rust-plugins/icons/src/loader/icon_to_svg.rs:38— farmfe_plugin_icons::loader::icon_to_svg::icon_to_svg has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 4 (7 pts) (nesting depth added 7). 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.
merge.merge (cognitive 24) packages/core/src/utils/merge.ts:63— merge.merge has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.normalizeUserCompilationConfig (cognitive 24) packages/core/src/config/normalize-config/index.ts:43— index.normalizeUserCompilationConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PersistentCacheConfig::as_obj (cognitive 23) crates/core/src/config/persistent_cache.rs:67— PersistentCacheConfig::as_obj has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 1 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
farmfe_docs_seo::syndication::atom (cognitive 23) rust-ecosystem/docs-seo/src/syndication.rs:29— farmfe_docs_seo::syndication::atom has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (6 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.
Visitor::visit_mut_jsx_opening_element (cognitive 23) rust-ecosystem/svgr-rs/src/add_jsx_attribute.rs:86— Visitor::visit_mut_jsx_opening_element has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (5 pts), boolean chains 2, 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.
HmrEngine.prepareHmrUpdate (cognitive 23) packages/core/src/server/hmr-engine.ts:291— HmrEngine.prepareHmrUpdate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dev-client.mount (cognitive 23) packages/docs/src/dev-client.tsx:19— dev-client.mount has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (20 pts), error handling 1, loops 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 43, 65). 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.
FarmPluginCss::transform (cognitive 22) crates/plugin_css/src/lib.rs:232— FarmPluginCss::transform has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (7 pts), match/switch 1 (5 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Reader::node (cognitive 22) rust-ecosystem/docs-content/src/metadata.rs:70— Reader::node has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (6 pts), match/switch 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Server.#initializeMiddlewares (cognitive 22) packages/core/src/server/index.ts:925— Server.#initializeMiddlewares has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 2). Of this number, 17 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
proxy.proxyMiddleware::upgrade (cognitive 22) REDACTED:176— proxy.proxyMiddleware::upgrade has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 1, loops 1 (nesting depth added 13). 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.
page-loader-core.createPageLoader.reconcile (cognitive 22) packages/docs/src/page-loader-core.ts:42— page-loader-core.createPageLoader.reconcile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (7 pts), boolean chains 4, ternaries 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
browser-runtime-core.BrowserRuntime::commit (cognitive 22) packages/docs/src/browser-runtime-core.tsx:194— browser-runtime-core.BrowserRuntime::commit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
module-helper.interopRequireWildcard (cognitive 22) packages/runtime/src/modules/module-helper.ts:81— module-helper.interopRequireWildcard has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Compiler::update_with_completion (cognitive 21) crates/compiler/src/update/mod.rs:398— Compiler::update_with_completion has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (11 pts), loops 4 (5 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
farmfe_node::docs_host::compile_owned (cognitive 21) crates/node/src/docs_host.rs:26— farmfe_node::docs_host::compile_owned has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Theme::resolve_key (cognitive 21) rust-ecosystem/tailwindcss/src/theme.rs:612— Theme::resolve_key has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
index.convertPluginVite (cognitive 21) packages/core/src/plugin/js/index.ts:160— index.convertPluginVite has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepare-sdk-types.prepareSdkTypes (cognitive 21) packages/core/scripts/prepare-sdk-types.mjs:41— prepare-sdk-types.prepareSdkTypes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 8). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (visit). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Comments::mask_line (cognitive 20) rust-ecosystem/docs-content/src/comments.rs:13— Comments::mask_line has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Glob::walk (cognitive 20) rust-ecosystem/glob/src/walk.rs:57— Glob::walk has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (6 pts), boolean chains 2, 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.
ExportComponentsFinder::visit_export_decl (cognitive 20) rust-plugins/react-components/src/find_local_components.rs:222— ExportComponentsFinder::visit_export_decl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 2 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
htmlFallback.htmlFallbackMiddleware.htmlFallbackMiddleware (cognitive 20) packages/core/src/server/middlewares/htmlFallback.ts:9— htmlFallback.htmlFallbackMiddleware.htmlFallbackMiddleware has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farm-to-vite-context.farmContextToViteContext (cognitive 20) packages/core/src/plugin/js/farm-to-vite-context.ts:10— farm-to-vite-context.farmContextToViteContext has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 2, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 49, a function literal at line 129, a function literal at line 73, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
search-page.SearchPage (cognitive 20) packages/docs-theme-default/src/search-page.tsx:26— search-page.SearchPage has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (11 pts), boolean chains 6, if/else 3 (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dynamic-import.loadUntracked (cognitive 20) packages/runtime/src/modules/dynamic-import.ts:216— dynamic-import.loadUntracked has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1 (nesting depth added 9). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginDriver::transform (cognitive 19) crates/core/src/plugin/plugin_driver.rs:309— PluginDriver::transform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (18 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.
FarmPluginResolve::resolve (cognitive 19) crates/plugin_resolve/src/lib.rs:45— FarmPluginResolve::resolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
PackageJsonLoader::load (cognitive 19) crates/toolkit/src/resolve/package_json_loader.rs:68— PackageJsonLoader::load has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_worker::resource_patch::patch_inline_worker_resources (cognitive 19) rust-plugins/worker/src/resource_patch.rs:13— farmfe_plugin_worker::resource_patch::patch_inline_worker_resources has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preview.startDocsPreview::serve (cognitive 19) packages/docs/src/preview.ts:293— preview.startDocsPreview::serve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 3, error handling 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
theme.resolveTheme (cognitive 19) packages/docs/src/theme.ts:52— theme.resolveTheme has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 4, if/else 2 (4 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginLazyCompilation::resolve (cognitive 18) crates/plugin_lazy_compilation/src/lib.rs:33— FarmPluginLazyCompilation::resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExistingCommonJsRequireVisitor::visit_mut_call_expr (cognitive 18) crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:279— ExistingCommonJsRequireVisitor::visit_mut_call_expr has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ModuleSystemAnalyzer::visit_member_expr (cognitive 18) crates/toolkit/src/script/module_system.rs:83— ModuleSystemAnalyzer::visit_member_expr has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2 (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.
farmfe_utils::relative (cognitive 18) crates/utils/src/lib.rs:128— farmfe_utils::relative has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FarmPluginVue::load (cognitive 18) rust-plugins/vue/src/lib.rs:456— FarmPluginVue::load has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
utils.queryPublicPath (cognitive 18) js-plugins/dts/src/utils.ts:284— utils.queryPublicPath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.transformAliasImport (cognitive 18) js-plugins/dts/src/utils.ts:393— utils.transformAliasImport has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 5 (8 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 401, 417). 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.
merge-config.mergeFarmCliConfig (cognitive 18) packages/core/src/config/merge-config.ts:48— merge-config.mergeFarmCliConfig has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 3 (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PackageJsonInfo::analyze_parsed_side_effects (cognitive 17) crates/core/src/common/mod.rs:79— PackageJsonInfo::analyze_parsed_side_effects has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UsedIdentsVisitor::visit_decl (cognitive 17) crates/plugin_tree_shake/src/statement_graph/analyze_deps_by_used_idents.rs:179— UsedIdentsVisitor::visit_decl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (2 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.
FarmfePluginIcons::load (cognitive 17) rust-plugins/icons/src/lib.rs:125— FarmfePluginIcons::load has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 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.
index.farmLessPlugin (cognitive 17) js-plugins/less/src/index.ts:29— index.farmLessPlugin has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 1 (2 pts), error handling 1, ternaries 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.
VitePluginAdapter.constructor (cognitive 17) REDACTED:129— VitePluginAdapter.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.resolveDependency (cognitive 17) js-plugins/sass/src/index.ts:189— index.resolveDependency has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, error handling 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sidebar-section.filterSidebarSection (cognitive 17) packages/docs-theme-default/src/sidebar-section.ts:26— sidebar-section.filterSidebarSection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preview.artifacts (cognitive 17) packages/docs/src/preview.ts:102— preview.artifacts has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, loops 4 (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
is_react_refresh_boundary.flushRefresh (cognitive 17) rust-plugins/react/src/is_react_refresh_boundary.ts:182— is_react_refresh_boundary.flushRefresh has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 1 (3 pts), loops 2 (3 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.
DesignSystem::register_theme_block (cognitive 16) rust-ecosystem/tailwindcss/src/design_system.rs:157— DesignSystem::register_theme_block has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AstNode::to_css (cognitive 16) rust-ecosystem/tailwindcss-node/src/compile.rs:112— AstNode::to_css has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (5 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Instrumentation::report (cognitive 16) rust-ecosystem/tailwindcss-node/src/instrumentation.rs:185— Instrumentation::report has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpClient::fetch_data (cognitive 16) rust-plugins/icons/src/cache/mod.rs:73— HttpClient::fetch_data has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PreviewServer.#initializeMiddlewares (cognitive 16) packages/core/src/server/preview.ts:148— PreviewServer.#initializeMiddlewares has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 4 (6 pts), boolean chains 4 (nesting depth added 2). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
lazyCompilation.lazyCompilationMiddleware.handleLazyCompilationMiddleware (cognitive 16) packages/core/src/server/middlewares/lazyCompilation.ts:20— lazyCompilation.lazyCompilationMiddleware.handleLazyCompilationMiddleware has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 3 (6 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
Root.generate (cognitive 16) js-plugins/tailwindcss/src/index.ts:354— Root.generate has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, loops 1 (2 pts), ternaries 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
navigation.NavigationMenu (cognitive 16) packages/docs-theme-default/src/navigation.tsx:12— navigation.NavigationMenu has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 2 (5 pts), boolean chains 4 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 5 function literals inside it that branch (lines 21, 15, 14, …). 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.
index.AlternateNavigation (cognitive 16) packages/docs-theme-default/src/index.tsx:126— index.AlternateNavigation has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 130, 128, 130). 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.
HmrClient.handleMessage (cognitive 16) REDACTED:393— HmrClient.handleMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity· main (cognitive 16) · ×1
main (cognitive 16) .agents/skills/writing-skills/render-graphs.js:84— main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Change-coupling hub: REDACTED → resources_injector.rs, binding.ts, share.ts packages/core/src/config/index.ts— `packages/core/src/config/index.ts` changes together with 3 other files — `crates/plugin_html/src/resources_injector.rs`, `packages/core/src/types/binding.ts`, `packages/core/src/utils/share.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change coupling: index.d.ts ↔ schema.ts packages/core/binding/index.d.ts:1— `packages/core/binding/index.d.ts` and `packages/core/src/config/schema.ts` change together 50% of the time (15 of the 30 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 15 shared commits counted here, the most recent 3 are `91f897b2` chore: optimize js logic (#1334); `492353f8` Fix/lazy compilation (#1253); `5b75ec27` feat: support isolate runtime resource (#1200) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) rust-ecosystem/syntax-highlight/src/lib.rs:178— rust-ecosystem/syntax-highlight/src/lib.rs:178-235 | rust-ecosystem/syntax-highlight/src/lib.rs:244-311 — 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 copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) crates/compiler/src/build/module_cache.rs:241— crates/compiler/src/build/module_cache.rs:241-288 | crates/compiler/src/build/module_cache.rs:294-338 — These two members are one piece of code written twice and then edited apart: 45 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) crates/toolkit/src/css.rs:34— crates/toolkit/src/css.rs:34-81 | crates/toolkit/src/script/mod.rs:53-87 — These two members are one piece of code written twice and then edited apart: 35 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) crates/core/src/plugin/plugin_driver.rs:206— crates/core/src/plugin/plugin_driver.rs:206-247 | crates/core/src/plugin/plugin_driver.rs:881-928 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) crates/compiler/src/build/module_cache.rs:531— crates/compiler/src/build/module_cache.rs:531-562 | crates/compiler/src/build/module_cache.rs:567-598 — 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) rust-plugins/vue-jsx/src/directive.rs:154— rust-plugins/vue-jsx/src/directive.rs:154-176 | rust-plugins/vue-jsx/src/directive.rs:178-200 — 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, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) crates/node/src/lib.rs:194— crates/node/src/lib.rs:194-214 | crates/node/src/lib.rs:217-237 | crates/node/src/lib.rs:241-261 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) crates/swc_transformer_import_glob/src/lib.rs:241— crates/swc_transformer_import_glob/src/lib.rs:241-269 | crates/swc_transformer_import_glob/src/lib.rs:275-299 | crates/swc_transformer_import_glob/src/lib.rs:301-325 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) crates/plugin_html/src/deps_analyzer.rs:111— crates/plugin_html/src/deps_analyzer.rs:111-139 | crates/plugin_html/src/deps_analyzer.rs:167-195 — 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 copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) rust-ecosystem/svgr-rs/src/add_jsx_attribute.rs:173— rust-ecosystem/svgr-rs/src/add_jsx_attribute.rs:173-196 | rust-ecosystem/svgr-rs/src/replace_jsx_attribute.rs:40-61 — 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 copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) rust-ecosystem/tailwindcss/src/utilities.rs:1577— rust-ecosystem/tailwindcss/src/utilities.rs:1577-1590 | rust-ecosystem/tailwindcss/src/utilities.rs:1660-1678 | rust-ecosystem/tailwindcss/src/utilities.rs:1694-1711 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) crates/core/src/module/module_graph.rs:286— crates/core/src/module/module_graph.rs:286-304 | crates/core/src/module/module_graph.rs:424-443 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) rust-ecosystem/tailwindcss/src/candidate.rs:290— rust-ecosystem/tailwindcss/src/candidate.rs:290-305 | rust-ecosystem/tailwindcss/src/candidate.rs:308-322 — 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 copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) crates/core/src/context/source_observation.rs:23— crates/core/src/context/source_observation.rs:23-32 | rust-ecosystem/docs-plan/src/prepare.rs:32-41 | rust-ecosystem/docs-plan/src/shared.rs:77-88 | rust-ecosystem/docs-snapshot/src/source.rs:18-27 | rust-plugins/docs-snapshot/src/lib.rs:153-162 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) crates/core/src/module/module_graph.rs:688— crates/core/src/module/module_graph.rs:688-694 | crates/core/src/module/module_graph.rs:696-702 | crates/core/src/module/module_group.rs:138-144 | crates/core/src/module/module_group.rs:146-152 | crates/core/src/module/module_group.rs:154-160 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) crates/node/src/plugin_adapters/js_plugin_adapter/hooks/plugin_cache_loaded.rs:13— crates/node/src/plugin_adapters/js_plugin_adapter/hooks/plugin_cache_loaded.rs:13-21 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/update_modules.rs:15-25 — 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 copies of one member (6 members, 1+ corresponding lines) · ×1
Edited copies of one member (6 members, 1+ corresponding lines) crates/node/src/plugin_adapters/js_plugin_adapter/hooks/build_end.rs:3— crates/node/src/plugin_adapters/js_plugin_adapter/hooks/build_end.rs:3-3 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/build_start.rs:3-3 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/finish.rs:3-3 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/render_start.rs:13-21 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/update_finished.rs:3-3 | crates/node/src/plugin_adapters/js_plugin_adapter/hooks/write_plugin_cache.rs:13-21 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 1 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 (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) crates/core/src/cache/store/disk.rs:407— crates/core/src/cache/store/disk.rs:407-409 | crates/core/src/cache/store/memory.rs:31-33 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (34 lines × 2) rust-ecosystem/docs-plan/src/brand_home.rs:36— rust-ecosystem/docs-plan/src/brand_home.rs:36-69 | rust-ecosystem/docs-plan/src/brand_home.rs:99-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/docs-plan/src/brand_home.rs:36` 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 (28–30 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:756— rust-plugins/vue-jsx/src/resolve_type.rs:756-785 | rust-plugins/vue-jsx/src/resolve_type.rs:904-931 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:756` 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 (32 lines × 2) rust-ecosystem/syntax-highlight/src/lib.rs:204— rust-ecosystem/syntax-highlight/src/lib.rs:204-235 | rust-ecosystem/syntax-highlight/src/lib.rs:280-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/syntax-highlight/src/lib.rs:204` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–25 lines × 2) crates/toolkit/src/script/module2cjs.rs:959— crates/toolkit/src/script/module2cjs.rs:959-983 | crates/toolkit/src/script/module2cjs.rs:1009-1032 — 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/toolkit/src/script/module2cjs.rs:959` 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 (23–24 lines × 2) rust-ecosystem/tailwindcss/src/utils/is_valid_arbitrary.rs:27— rust-ecosystem/tailwindcss/src/utils/is_valid_arbitrary.rs:27-50 | rust-ecosystem/tailwindcss/src/utils/segment.rs:49-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. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/utils/is_valid_arbitrary.rs:27` 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 (20–22 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:727— rust-plugins/vue-jsx/src/resolve_type.rs:727-748 | rust-plugins/vue-jsx/src/resolve_type.rs:880-899 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:727` 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 (16–21 lines × 2) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:666— crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:666-686 | crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:698-713 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:666` 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 (19–20 lines × 2) crates/plugin_tree_shake/src/tree_shake_modules.rs:473— crates/plugin_tree_shake/src/tree_shake_modules.rs:473-492 | crates/plugin_tree_shake/src/tree_shake_modules.rs:562-580 — 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/plugin_tree_shake/src/tree_shake_modules.rs:473` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:490— rust-plugins/vue-jsx/src/resolve_type.rs:490-509 | rust-plugins/vue-jsx/src/resolve_type.rs:523-542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:490` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) crates/compiler/src/build/module_cache.rs:534— crates/compiler/src/build/module_cache.rs:534-552 | crates/compiler/src/build/module_cache.rs:570-588 — 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/compiler/src/build/module_cache.rs:534` 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–18 lines × 2) crates/plugin_partial_bundling/src/merge_module_pots.rs:283— crates/plugin_partial_bundling/src/merge_module_pots.rs:283-300 | crates/plugin_partial_bundling/src/merge_module_pots.rs:305-321 — 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/plugin_partial_bundling/src/merge_module_pots.rs:283` 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 (18 lines × 2) rust-plugins/vue-jsx/src/directive.rs:118— rust-plugins/vue-jsx/src/directive.rs:118-135 | rust-plugins/vue-jsx/src/directive.rs:260-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/directive.rs:118` 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–15 lines × 2) crates/plugin_css/src/lib.rs:658— crates/plugin_css/src/lib.rs:658-671 | crates/plugin_script/src/lib.rs:741-755 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/plugin_script/src/lib.rs:758` calls `trace_module_sourcemap` and `crates/plugin_css/src/lib.rs:673` 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 (13–14 lines × 2) crates/plugin_resolve/src/resolver/exports.rs:137— crates/plugin_resolve/src/resolver/exports.rs:137-150 | crates/plugin_resolve/src/resolver/exports.rs:183-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin_resolve/src/resolver/exports.rs:137` 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 × 3) rust-ecosystem/glob/src/compile.rs:1174— rust-ecosystem/glob/src/compile.rs:1174-1186 | rust-ecosystem/glob/src/compile.rs:1213-1225 | rust-ecosystem/glob/src/compile.rs:1247-1259 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/glob/src/compile.rs:1174` 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–13 lines × 2) rust-plugins/react-components/src/find_local_components.rs:68— rust-plugins/react-components/src/find_local_components.rs:68-80 | rust-plugins/react-components/src/find_local_components.rs:99-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/react-components/src/find_local_components.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 (11–13 lines × 2) rust-plugins/vue-jsx/src/lib.rs:926— rust-plugins/vue-jsx/src/lib.rs:926-938 | rust-plugins/vue-jsx/src/lib.rs:944-954 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/lib.rs:926` 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 × 2) crates/compiler/src/update/module_cache.rs:44— crates/compiler/src/update/module_cache.rs:44-55 | crates/compiler/src/update/regenerate_resources/mod.rs:180-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–12 lines × 2) crates/core/src/module/module_graph.rs:474— crates/core/src/module/module_graph.rs:474-482 | crates/core/src/module/module_group.rs:117-128 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `from` to `&ModuleId` in one and `&ModuleGroupId` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10–12 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:681— rust-plugins/vue-jsx/src/resolve_type.rs:681-692 | rust-plugins/vue-jsx/src/resolve_type.rs:841-850 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/vue-jsx/src/resolve_type.rs:681` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–10 lines × 4) rust-ecosystem/glob/src/compile.rs:1134— rust-ecosystem/glob/src/compile.rs:1134-1141 | rust-ecosystem/glob/src/compile.rs:1181-1190 | rust-ecosystem/glob/src/compile.rs:1220-1229 | rust-ecosystem/glob/src/compile.rs:1254-1263 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/glob/src/compile.rs:1134` 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 (9–10 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:1024— rust-plugins/vue-jsx/src/resolve_type.rs:1024-1033 | rust-plugins/vue-jsx/src/resolve_type.rs:1064-1072 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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–9 lines × 2) crates/core/src/module/module_graph.rs:520— crates/core/src/module/module_graph.rs:520-526 | crates/core/src/module/module_graph.rs:569-577 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/module/module_graph.rs:520` 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 (8–9 lines × 2) rust-ecosystem/tailwindcss/src/candidate.rs:381— rust-ecosystem/tailwindcss/src/candidate.rs:381-389 | rust-ecosystem/tailwindcss/src/variants.rs:663-670 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rust-ecosystem/tailwindcss/src/candidate.rs:381` 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 (5 lines × 3) rust-plugins/icons/src/lib.rs:139— rust-plugins/icons/src/lib.rs:139-143 | rust-plugins/icons/src/lib.rs:218-222 | rust-plugins/svgr/src/lib.rs:85-89 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `rust-plugins/icons/src/lib.rs:139` 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 × 4) crates/core/src/module/module_graph.rs:287— crates/core/src/module/module_graph.rs:287-294 | crates/core/src/module/module_graph.rs:391-398 | crates/core/src/module/module_graph.rs:425-432 | crates/core/src/module/module_graph.rs:446-453 — 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/core/src/module/module_graph.rs:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) scripts/ci-e2e-shadow-inputs.py:53— scripts/ci-e2e-shadow-inputs.py:53-59 | scripts/ci-unit-shadow-inputs.py:20-24 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 4+ corresponding lines) · ×1
Edited copies of one member (5 members, 4+ corresponding lines) scripts/ci-source-plan.py:10— scripts/ci-source-plan.py:10-13 | scripts/incremental-chain-evidence.py:13-16 | scripts/release-npm-best-effort.py:29-32 | scripts/release-registry-host-tool.py:23-26 | scripts/release-version-history.py:25-28 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 3+ corresponding lines) · ×1
Edited copies of one member (5 members, 3+ corresponding lines) scripts/ci-impact-plan.py:328— scripts/ci-impact-plan.py:328-330 | scripts/ci-provenance-consumer.py:18-20 | scripts/incremental-release-entry.py:18-20 | scripts/incremental-release-publish.py:25-27 | scripts/temporary-new-packages.py:22-24 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 1+ corresponding lines) · ×1
Edited copies of one member (5 members, 1+ corresponding lines) scripts/ci-impact-plan.py:65— scripts/ci-impact-plan.py:65-65 | scripts/ci-native-proof.py:27-27 | scripts/incremental-chain-plan.py:54-54 | scripts/incremental-publication-state.py:16-16 | scripts/release-registry-host-tool.py:68-69 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
End-of-life runtime: Node.js 10 rust-plugins/yaml/npm/win32-x64-msvc/REDACTED:17— rust-plugins/yaml/npm/win32-x64-msvc/REDACTED declares Node.js 10 as this project's engines.node, and Node.js 10, support ended 2021-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
CI formatting step cannot fail REDACTED:23— `cargo fmt` invokes cargo fmt in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Outbound HTTP without resilience rust-plugins/icons/src/cache/mod.rs:92— `reqwest::get(` 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 7 sibling directories (9 clone groups) crates/create-farm-rs/templates/tauri/react/src/App.tsx:7— 9 duplicated blocks under crates/create-farm-rs/templates/ have copies in at least two of the sibling directories electron, preact, react, solid, tauri, tauri2 (+1 more sibling(s) not listed) — 6 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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 6 sibling directories (8 clone groups) crates/create-farm-rs/templates/electron/preact/electron/main.ts:5— 8 of the duplicated blocks reported below have copies in at least two of the sibling directories preact, react, solid, svelte, vanilla, vue under crates/create-farm-rs/templates/electron/. 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.
Duplication concentrated across 7 sibling directories (6 clone groups) js-plugins/less/src/index.ts:39— 6 duplicated blocks under js-plugins/ have copies in at least two of the sibling directories babel, dts, less, postcss, react-compiler, sass (+1 more sibling(s) not listed) — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (5 clone groups) packages/create-farm-plugin/templates/rust/scripts/index.js:69— 5 duplicated blocks under the repository root have copies in at least two of the sibling directories js-plugins, packages, rust-plugins, scripts — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (64 identical lines × 4 files) rust-plugins/dts/scripts/index.js:1— rust-plugins/dts/scripts/index.js:1 · rust-plugins/replace-dirname/scripts/index.js:1 · rust-plugins/svgr/scripts/index.js:1 · rust-plugins/vue-jsx/scripts/index.js:1 — these 4 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (53 lines × 21 locations) packages/create-farm-plugin/templates/rust/scripts/index.js:69— packages/create-farm-plugin/templates/rust/scripts/index.js:69 · rust-plugins/auto-import/scripts/index.js:69 · rust-plugins/compress/scripts/index.js:69 · rust-plugins/dsv/scripts/index.js:69 · +17 more site(s) not listed — the 21 copies are spread across 21 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) packages/docs-theme-default/src/index.tsx:42— packages/docs-theme-default/src/index.tsx:42 · packages/docs-theme-default/src/search.tsx:9 — the two spans are one implementation copied and then locally edited — 517 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 (46 lines × 2 locations) crates/create-farm-rs/templates/tauri/preact/src/App.tsx:7— crates/create-farm-rs/templates/tauri/preact/src/App.tsx:7 · crates/create-farm-rs/templates/tauri/react/src/App.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.
R10 · Code Duplication· Duplicated block with local edits (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) js-plugins/less/src/index.ts:39— js-plugins/less/src/index.ts:39 · js-plugins/sass/src/index.ts:56 — the two spans are one implementation copied and then locally edited — 254 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 (44 matched lines × 2 locations) · ×1
Duplicated block with local edits (44 matched lines × 2 locations) packages/core/src/server/type.ts:9— packages/core/src/server/type.ts:9 · packages/runtime-plugin-hmr/src/types.ts:55 — the two spans are one implementation copied and then locally edited — 168 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 (40 lines × 2 locations) crates/create-farm-rs/templates/tauri/react/src/App.tsx:7— crates/create-farm-rs/templates/tauri/react/src/App.tsx:7 · crates/create-farm-rs/templates/tauri2/react/src/App.tsx:6 — 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 (36 lines × 2 locations) crates/create-farm-rs/templates/tauri/solid/src/App.tsx:7— crates/create-farm-rs/templates/tauri/solid/src/App.tsx:7 · crates/create-farm-rs/templates/tauri2/solid/src/App.tsx:6 — 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 (35 lines × 3 locations) js-plugins/copy/farm.config.ts:4— js-plugins/copy/farm.config.ts:4 · js-plugins/vuetify/farm.config.ts:4 · packages/create-farm-plugin/templates/js/farm.config.ts: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.
Duplicated block (35 lines × 21 locations) packages/create-farm-plugin/templates/rust/scripts/index.js:6— packages/create-farm-plugin/templates/rust/scripts/index.js:6 · rust-plugins/auto-import/scripts/index.js:6 · rust-plugins/compress/scripts/index.js:6 · rust-plugins/dsv/scripts/index.js:6 · +17 more site(s) not listed — the 21 copies are spread across 21 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 21 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 (34 lines × 3 locations) packages/core/src/types/ws.ts:148— packages/core/src/types/ws.ts:148 · packages/core/src/types/ws.ts:184 · packages/core/src/types/ws.ts:219 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 6 locations) crates/create-farm-rs/templates/electron/preact/electron/main.ts:5— crates/create-farm-rs/templates/electron/preact/electron/main.ts:5 · crates/create-farm-rs/templates/electron/react/electron/main.ts:5 · crates/create-farm-rs/templates/electron/solid/electron/main.ts:5 · crates/create-farm-rs/templates/electron/svelte/electron/main.ts:5 · +2 more site(s) not listed — the 6 copies are spread across 6 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 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (33 lines × 2 locations) scripts/build.mjs:323— scripts/build.mjs:323 · scripts/build.mjs:373 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) packages/core/src/server/index.ts:1122— packages/core/src/server/index.ts:1122 · packages/core/src/server/preview.ts:332 — the two spans are one implementation copied and then locally edited — 189 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 (28 lines × 3 locations) crates/create-farm-rs/templates/tauri2/preact/src/App.tsx:17— crates/create-farm-rs/templates/tauri2/preact/src/App.tsx:17 · crates/create-farm-rs/templates/tauri2/react/src/App.tsx:17 · crates/create-farm-rs/templates/tauri2/solid/src/App.tsx:17 — the 3 copies are spread across 3 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported.
Duplicated block (27 lines × 2 locations) packages/create-farm-plugin/templates/js/playground/src/main.tsx:5— packages/create-farm-plugin/templates/js/playground/src/main.tsx:5 · packages/create-farm-plugin/templates/rust/playground/src/main.tsx:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (26 lines × 2 locations) crates/create-farm-rs/templates/electron/react/src/main.tsx:5— crates/create-farm-rs/templates/electron/react/src/main.tsx:5 · crates/create-farm-rs/templates/react/src/main.tsx:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (25 lines × 2 locations) crates/create-farm-rs/templates/electron/preact/src/app.tsx:6— crates/create-farm-rs/templates/electron/preact/src/app.tsx:6 · crates/create-farm-rs/templates/preact/src/app.tsx:6 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) js-plugins/visualizer/src/client/src/components/CodeDiff.vue:25— js-plugins/visualizer/src/client/src/components/CodeDiff.vue:25 · js-plugins/visualizer/src/client/src/components/CodeViewer.vue:24 — 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 (23 lines × 2 locations) REDACTED:521— REDACTED:521 · REDACTED:580 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (23 matched lines × 2 locations) · ×1
Duplicated block with local edits (23 matched lines × 2 locations) packages/runtime-plugin-hmr/src/overlay.ts:703— packages/runtime-plugin-hmr/src/overlay.ts:703 · packages/runtime-plugin-hmr/src/overlay.ts:742 — the two spans are one implementation copied and then locally edited — 145 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) packages/core/src/plugin/js/apply-html-transform.ts:68— packages/core/src/plugin/js/apply-html-transform.ts:68 · packages/core/src/plugin/js/apply-html-transform.ts:104 — the two spans are one implementation copied and then locally edited — 132 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) packages/core/src/server/error.ts:5— packages/core/src/server/error.ts:5 · packages/runtime-plugin-hmr/src/utils.ts:32 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (20 lines × 4 locations) crates/create-farm-rs/templates/tauri2/preact/farm.config.ts:5— crates/create-farm-rs/templates/tauri2/preact/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/solid/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/svelte/farm.config.ts:5 · crates/create-farm-rs/templates/tauri2/vue/farm.config.ts:5 — 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 (19 lines × 2 locations) packages/core/src/types/ws.ts:257— packages/core/src/types/ws.ts:257 · packages/core/src/types/ws.ts:278 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:112— js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:112 · js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue:131 — 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.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 64, cognitive 89) · ×1
Complex function main (cyclomatic 64, cognitive 89) REDACTED:221— main has cyclomatic complexity 64 and cognitive complexity 89; 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 discoverSuiteInventory (cyclomatic 51, cognitive 91) scripts/ci-suite-inventory.mjs:48— discoverSuiteInventory has cyclomatic complexity 51 and cognitive complexity 91; 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 resolveNativeBindingPath (cyclomatic 47, cognitive 118) packages/core/binding/resolve-binding.cjs:3— resolveNativeBindingPath has cyclomatic complexity 47 and cognitive complexity 118; 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.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 45, cognitive 83) · ×1
Complex function main (cyclomatic 45, cognitive 83) scripts/incremental-release-producer.mjs:373— main has cyclomatic complexity 45 and cognitive complexity 83; 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 verifyCandidateSeal (cyclomatic 44, cognitive 80) scripts/verify-v2-candidate-seal.mjs:22— verifyCandidateSeal has cyclomatic complexity 44 and cognitive complexity 80; 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 makePublicationManifest (cyclomatic 43, cognitive 47) scripts/incremental-release-producer.mjs:287— makePublicationManifest has cyclomatic complexity 43 and cognitive complexity 47; 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 validateSummary (cyclomatic 42, cognitive 48) scripts/performance-pr-reporter.mjs:24— validateSummary has cyclomatic complexity 42 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizePersistentCache (cyclomatic 39, cognitive 68) packages/core/src/config/normalize-config/normalize-persistent-cache.ts:21— normalizePersistentCache has cyclomatic complexity 39 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classifyVersionDiff (cyclomatic 39, cognitive 43) scripts/changesets-version-only.mjs:151— classifyVersionDiff has cyclomatic complexity 39 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateReleaseSet (cyclomatic 38, cognitive 43) scripts/farm-docs-registry-consumer.mjs:24— validateReleaseSet has cyclomatic complexity 38 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function viteConfigToFarmConfig (cyclomatic 37, cognitive 83) packages/core/src/plugin/js/farm-to-vite-config.ts:321— viteConfigToFarmConfig has cyclomatic complexity 37 and cognitive complexity 83; 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 runDockerCargoBuild (cyclomatic 37, cognitive 42) scripts/v2-docker-cargo-cache.mjs:79— runDockerCargoBuild has cyclomatic complexity 37 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyHotUpdates (cyclomatic 34, cognitive 81) REDACTED:231— applyHotUpdates has cyclomatic complexity 34 and cognitive complexity 81; 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 signature (cyclomatic 32, cognitive 15) scripts/ci-attempt-producers.mjs:27— signature has cyclomatic complexity 32 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function assertRegistryLock (cyclomatic 31, cognitive 63) scripts/farm-docs-vercel-build.mjs:185— assertRegistryLock has cyclomatic complexity 31 and cognitive complexity 63; 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 readSafeZip (cyclomatic 31, cognitive 32) scripts/performance-cohorts.mjs:76— readSafeZip has cyclomatic complexity 31 and cognitive complexity 32; 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 resolveVersionEvidence (cyclomatic 30, cognitive 33) scripts/changesets-version-runtime.mjs:58— resolveVersionEvidence has cyclomatic complexity 30 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function materializeRegistry (cyclomatic 29, cognitive 47) scripts/sdk-candidate-registry.mjs:42— materializeRegistry has cyclomatic complexity 29 and cognitive complexity 47; 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 docker (cyclomatic 26, cognitive 35) scripts/v2-docker-cargo-cache.test.mjs:16— docker has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function preparePlatformPackages (cyclomatic 25, cognitive 39) packages/plugin-tools/src/prepare.ts:5— preparePlatformPackages has cyclomatic complexity 25 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function captureProducts (cyclomatic 25, cognitive 26) scripts/ci-native-capture.mjs:51— captureProducts has cyclomatic complexity 25 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sameArtifact (cyclomatic 25, cognitive 12) packages/plugin-tools/src/copy-artifacts.ts:4— sameArtifact has cyclomatic complexity 25 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function drainWatchUpdates (cyclomatic 24, cognitive 61) packages/core/src/server/hmr-engine.ts:204— drainWatchUpdates has cyclomatic complexity 24 and cognitive complexity 61; 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 executor (cyclomatic 23, cognitive 48) js-plugins/copy/src/index.ts:133— executor has cyclomatic complexity 23 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildPublishedDocs (cyclomatic 23, cognitive 33) scripts/farm-docs-vercel-build.mjs:260— buildPublishedDocs has cyclomatic complexity 23 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runConsumer (cyclomatic 23, cognitive 24) scripts/farm-docs-registry-consumer.mjs:142— runConsumer has cyclomatic complexity 23 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function report (cyclomatic 22, cognitive 22) scripts/performance-pr-reporter.mjs:118— report has cyclomatic complexity 22 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function deploymentPlan (cyclomatic 21, cognitive 40) scripts/farm-docs-vercel-build.mjs:63— deploymentPlan has cyclomatic complexity 21 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizeTargetEnv (cyclomatic 21, cognitive 39) packages/core/src/config/normalize-config/normalize-output.ts:141— normalizeTargetEnv has cyclomatic complexity 21 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cargoManifest (cyclomatic 21, cognitive 32) scripts/changesets-version-only.mjs:92— cargoManifest has cyclomatic complexity 21 and cognitive complexity 32; 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 collectReleaseDiagnostics (cyclomatic 21, cognitive 31) scripts/v2-release-diagnostics.mjs:45— collectReleaseDiagnostics has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function assertLockResolution (cyclomatic 21, cognitive 30) scripts/farm-docs-vercel-build.mjs:150— assertLockResolution has cyclomatic complexity 21 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizeUserCompilationConfig (cyclomatic 21, cognitive 29) packages/core/src/config/normalize-config/index.ts:43— normalizeUserCompilationConfig has cyclomatic complexity 21 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function changesetsPublication (cyclomatic 21, cognitive 27) scripts/v2-release-inventory.mjs:131— changesetsPublication has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateCollectedSuites (cyclomatic 21, cognitive 26) scripts/ci-suite-execution.mjs:175— validateCollectedSuites has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cleanupStaleE2EProcesses (cyclomatic 21, cognitive 22) e2e/process-cleanup.mjs:278— cleanupStaleE2EProcesses has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizeRuntimeConfig (cyclomatic 21, cognitive 16) packages/core/src/config/normalize-config/normalize-runtime.ts:20— normalizeRuntimeConfig has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function installedPackages (cyclomatic 20, cognitive 55) scripts/farm-docs-registry-consumer.mjs:119— installedPackages has cyclomatic complexity 20 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildExamples (cyclomatic 20, cognitive 39) scripts/build.mjs:82— buildExamples has cyclomatic complexity 20 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateConsumer (cyclomatic 20, cognitive 33) scripts/farm-docs-registry-consumer.mjs:54— validateConsumer has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/core/src/server/index.ts · ×1
packages/core/src/server/index.ts: 1124 lines of code packages/core/src/server/index.ts:1— packages/core/src/server/index.ts has 1124 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 874 lines of code REDACTED:1— REDACTED has 874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime-plugin-hmr/src/overlay.ts · ×1
packages/runtime-plugin-hmr/src/overlay.ts: 697 lines of code packages/runtime-plugin-hmr/src/overlay.ts:1— packages/runtime-plugin-hmr/src/overlay.ts has 697 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/types/ws.ts · ×1
packages/core/src/types/ws.ts: 515 lines of code packages/core/src/types/ws.ts:1— packages/core/src/types/ws.ts has 515 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 514 lines of code REDACTED:1— REDACTED has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/types/binding.ts · ×1
packages/core/src/types/binding.ts: 510 lines of code packages/core/src/types/binding.ts:1— packages/core/src/types/binding.ts has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/plugin/js/js-plugin-schema.ts · ×1
packages/core/src/plugin/js/js-plugin-schema.ts: 498 lines of code packages/core/src/plugin/js/js-plugin-schema.ts:1— packages/core/src/plugin/js/js-plugin-schema.ts has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/config/schema.ts · ×1
packages/core/src/config/schema.ts: 470 lines of code packages/core/src/config/schema.ts:1— packages/core/src/config/schema.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/server/ws.ts · ×1
packages/core/src/server/ws.ts: 458 lines of code packages/core/src/server/ws.ts:1— packages/core/src/server/ws.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/config/types.ts · ×1
packages/core/src/config/types.ts: 444 lines of code packages/core/src/config/types.ts:1— packages/core/src/config/types.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/plugin/js/farm-to-vite-config.ts · ×1
packages/core/src/plugin/js/farm-to-vite-config.ts: 434 lines of code packages/core/src/plugin/js/farm-to-vite-config.ts:1— packages/core/src/plugin/js/farm-to-vite-config.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· js-plugins/tailwindcss/src/index.ts · ×1
js-plugins/tailwindcss/src/index.ts: 418 lines of code js-plugins/tailwindcss/src/index.ts:1— js-plugins/tailwindcss/src/index.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage· No test rig can mount a component in this workspace · ×1
No test rig can mount a component in this workspace vitest.config.ts:1— vitest.config.ts declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 182 unreached component module(s) can be tested as written, however the suite is authored: js-plugins/visualizer/src/client/src/pages/analysis/Compilation.vue, js-plugins/visualizer/src/client/src/pages/analysis/Plugin.vue, examples/rust-plugin-worker/src/index.tsx, examples/react-antd/src/antd-layout.tsx, examples/tailwind-next/src/App.tsx, examples/solid-ssr/src/main.tsx and 176 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each.
Dead file (~214 LoC) examples/arcgis/e2e.mock.mjs— no import path from any entry point (565 application, 396 tooling, 525 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 (~139 LoC) examples/arco-pro/src/components/MessageBox/index.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~114 LoC) examples/arco-pro/src/components/MessageBox/list.tsx— no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (examples/arco-pro/src/components/MessageBox/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 (~110 LoC) examples/commerce-lab/benchmark/hmr-sampler.mjs— no import path from any entry point (565 application, 396 tooling, 525 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 (~103 LoC) examples/commerce-lab/benchmark/build-sampler.mjs— no import path from any entry point (565 application, 396 tooling, 525 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 (~96 LoC) examples/tailwind-next/src/AnimatedComponents.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~85 LoC) packages/core/src/server/error.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~84 LoC) examples/arco-pro/src/components/Chart/area-polar.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~83 LoC) examples/arco-pro/src/components/Chart/overview-area-line.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~81 LoC) examples/arco-pro/src/components/Chart/period-legend-line.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~76 LoC) examples/arco-pro/src/components/Chart/horizontal-interval.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~75 LoC) js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue— no import path from any entry point (565 application, 396 tooling, 525 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 (~73 LoC) examples/commerce-lab/benchmark/graph-snapshot.mjs— no import path from any entry point (565 application, 396 tooling, 525 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 (~67 LoC) examples/arco-pro/src/components/Chart/fact-multi-pie.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~63 LoC) examples/arco-pro/src/components/Chart/multi-area-line.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~57 LoC) examples/arco-pro/src/utils/authentication.ts— no import path from any entry point (565 application, 396 tooling, 525 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 (~48 LoC) js-plugins/visualizer/src/client/src/components/ProcessRecord.vue— no import path from any entry point (565 application, 396 tooling, 525 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 (~44 LoC) examples/arco-pro/src/components/Chart/multi-stack-interval.tsx— no import path from any entry point (565 application, 396 tooling, 525 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 (~42 LoC) examples/arco-pro/src/components/Chart/customer-tooltip.tsx— no import path from any entry point (565 application, 396 tooling, 525 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (examples/arco-pro/src/components/Chart/area-polar.tsx, examples/arco-pro/src/components/Chart/horizontal-interval.tsx, examples/arco-pro/src/components/Chart/multi-area-line.tsx and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~34 LoC) examples/vue-antdv/src/test1.vue— no import path from any entry point (565 application, 396 tooling, 525 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
Unlisted import 'react-router-dom' examples/rust-plugin-auto-import-react/auto_import.d.ts:4— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'preact' rust-plugins/icons/types/preact.d.ts:2— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'solid-js' rust-plugins/icons/types/solid.d.ts:2— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'svelte' rust-plugins/icons/types/svelte3.d.ts:6— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unused dependency '@codspeed/vitest-plugin' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mdast-util-from-markdown' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mdast-util-frontmatter' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mdast-util-gfm' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mdast-util-mdx' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'micromark-extension-frontmatter' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'micromark-extension-gfm' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'micromark-extension-mdxjs' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'node-emoji' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'source-map-support' — Declared in crates/create-farm-rs/templates/nestjs/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tsconfig-paths' — Declared in crates/create-farm-rs/templates/nestjs/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tslib' — Declared in crates/create-farm-rs/templates/svelte/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Documentation: no build, run or usage example packages/core/npm/darwin-arm64/README.md:1— `darwin-arm64` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/darwin-arm64/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 packages/core/npm/darwin-x64/README.md:1— `darwin-x64` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/darwin-x64/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 packages/core/npm/linux-arm64-gnu/README.md:1— `linux-arm64-gnu` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/linux-arm64-gnu/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 packages/core/npm/linux-arm64-musl/README.md:1— `linux-arm64-musl` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/linux-arm64-musl/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 packages/core/npm/linux-x64-gnu/README.md:1— `linux-x64-gnu` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/linux-x64-gnu/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 packages/core/npm/linux-x64-musl/README.md:1— `linux-x64-musl` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/linux-x64-musl/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 packages/core/npm/win32-arm64-msvc/README.md:1— `win32-arm64-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/win32-arm64-msvc/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 packages/core/npm/win32-ia32-msvc/README.md:1— `win32-ia32-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/win32-ia32-msvc/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 packages/core/npm/win32-x64-msvc/README.md:1— `win32-x64-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/core/npm/win32-x64-msvc/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 packages/create-farm/npm/darwin-arm64/README.md:1— `darwin-arm64` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/darwin-arm64/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 packages/create-farm/npm/darwin-x64/README.md:1— `darwin-x64` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/darwin-x64/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 packages/create-farm/npm/linux-arm64-gnu/README.md:1— `linux-arm64-gnu` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/linux-arm64-gnu/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 packages/create-farm/npm/linux-arm64-musl/README.md:1— `linux-arm64-musl` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/linux-arm64-musl/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 packages/create-farm/npm/linux-x64-gnu/README.md:1— `linux-x64-gnu` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/linux-x64-gnu/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 packages/create-farm/npm/linux-x64-musl/README.md:1— `linux-x64-musl` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/linux-x64-musl/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 packages/create-farm/npm/win32-arm64-msvc/README.md:1— `win32-arm64-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/win32-arm64-msvc/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 packages/create-farm/npm/win32-ia32-msvc/README.md:1— `win32-ia32-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/win32-ia32-msvc/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 packages/create-farm/npm/win32-x64-msvc/README.md:1— `win32-x64-msvc` is a published package (`REDACTED` without `"private": true`) and neither `packages/create-farm/npm/win32-x64-msvc/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 packages/runtime/README.md:1— `runtime` is a published package (`REDACTED` without `"private": true`) and neither `packages/runtime/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 packages/runtime-plugin-hmr/README.md:1— `runtime-plugin-hmr` is a published package (`REDACTED` without `"private": true`) and neither `packages/runtime-plugin-hmr/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 packages/runtime-plugin-import-meta/README.md:1— `runtime-plugin-import-meta` is a published package (`REDACTED` without `"private": true`) and neither `packages/runtime-plugin-import-meta/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 packages/utils/README.md:1— `utils` is a published package (`REDACTED` without `"private": true`) and neither `packages/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 rust-plugins/auto-import/npm/darwin-arm64/README.md:1— `darwin-arm64` is a published package (`REDACTED` without `"private": true`) and neither `rust-plugins/auto-import/npm/darwin-arm64/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 rust-plugins/auto-import/npm/darwin-x64/README.md:1— `darwin-x64` is a published package (`REDACTED` without `"private": true`) and neither `rust-plugins/auto-import/npm/darwin-x64/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 rust-plugins/auto-import/npm/linux-arm64-gnu/README.md:1— `linux-arm64-gnu` is a published package (`REDACTED` without `"private": true`) and neither `rust-plugins/auto-import/npm/linux-arm64-gnu/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.
Orphaned file packages/core/src/types/binding.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/svgr-rs/src/hast_to_swc_ast/mappings.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/tailwindcss-node/src/compile.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/create-farm-rs/src/template.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/src/cache/scope.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/tailwindcss/src/design_system.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/create-farm-rs/src/utils/lte.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/tailwindcss/src/candidate.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-plugins/react-components/src/find_local_components.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/tailwindcss/src/parser.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 js-plugins/dts/src/utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file patches/serde/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 rust-plugins/worker/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 rust-ecosystem/svgr-rs/src/svg_dynamic_title.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/create-farm-rs/src/utils/colors.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-plugins/icons/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 rust-ecosystem/tailwindcss-node/src/instrumentation.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/svgr-rs/src/hast_to_swc_ast/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/create-farm-rs/src/utils/theme.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-plugins/svgr/src/svg_builder.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/svgr-rs/src/add_jsx_attribute.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 js-plugins/dts/src/context.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file rust-ecosystem/svgr-rs/src/transform_react_native_svg.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 js-plugins/react-compiler/src/types.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
redundant comment crates/compiler/tests/fixtures/library/cjs/basic/output.js:45— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/export/complex-export-all/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/export/export-all/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/export/named/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/export/namespace/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/import/named/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/import/namespace/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/module_exports/exports_only/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/require/entry/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/require/external/output.cjs.js:49— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/require/external/output.js:31— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/require/multiple_external/output.js:31— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/cjs/require/spread-expr/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/dynamic/lodash_export/output.cjs.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/dynamic/lodash_export/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/dynamic/require/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/external/multiple-export-all/output.browser.js:82— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/external/multiple-export-all/output.browser.js:88— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/external/multiple-export-all/output.browser.js:97— "dynamic module entry and resources map" repeats the code it sits on: 4 of its 5 words (dynamic, module, resources, map) are already in `let dynamicModuleResourcesMap = {};`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/esm_export_cjs/output.cjs.js:47— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/esm_export_cjs/output.js:29— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/hybrid_entry_should_reexport/output.cjs.js:33— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/hybrid_entry_should_reexport/output.esm_cjs.js:33— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/hybrid_entry_should_reexport/output.esm_cjs.js:114— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/compiler/tests/fixtures/library/hybrid/hybrid_entry_should_reexport/output.js:31— "return the exports of the module" repeats the code it sits on: 3 of its 3 words (return, exports, module) are already in `return module.exports;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate REDACTED:277— `!filename || !filename.endsWith('.html')` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. 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 js-plugins/less/src/utils.ts:12— `!implementation || typeof implementation === 'string'` appears character-identically in 2 files — js-plugins/less/src/utils.ts, js-plugins/postcss/src/utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/docs/src/preview.ts:208— `!inside(root, output) || ['.git', 'node_modules', '.farm-docs', '.farm-docs-locks'].includes( path.relative(root, output).split(path.sep)[0]…` appears character-identically in 2 files — packages/docs/src/preview.ts, packages/docs/src/workflow.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate rust-plugins/dts/scripts/index.js:15— `!process.report || typeof process.report.getReport !== "function"` appears character-identically in 4 files — rust-plugins/dts/scripts/index.js, rust-plugins/replace-dirname/scripts/index.js, rust-plugins/svgr/scripts/index.js, rust-plugins/vue-jsx/scripts/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/binding/resolve-binding.cjs:21— `!process.report || typeof process.report.getReport !== 'function'` appears character-identically in 20 files — packages/core/binding/resolve-binding.cjs, packages/create-farm-plugin/templates/rust/scripts/index.js, rust-plugins/auto-import/scripts/index.js, rust-plugins/compress/scripts/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/prepare-cargo-version-proposal.mjs:85— `!relative.startsWith('..') && !path.isAbsolute(relative)` appears character-identically in 3 files — scripts/prepare-cargo-version-proposal.mjs, scripts/v2-normal-pack-contract.mjs, scripts/verify-sdk-consumer.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:154— `MIME_TYPES[ext] || 'application/octet-stream'` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. 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 scripts/check-pr-changesets.mjs:107— `change.id === cargoChangesetId && cargoRecord` appears character-identically in 2 files — scripts/check-pr-changesets.mjs, scripts/prepare-v2-release-intent.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:69— `container && container.dataset.multiselect !== undefined` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/helper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:68— `el.closest('.options') || el.closest('.cards')` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/helper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/docs-theme-default/src/navigation.tsx:26— `event.key === 'ArrowDown' || event.key === 'ArrowUp'` appears character-identically in 2 files — packages/docs-theme-default/src/navigation.tsx, packages/docs-theme-default/src/search.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 REDACTED:8— `file.endsWith('.md') && file !== 'README.md'` appears character-identically in 2 files — REDACTED, scripts/check-pr-changesets.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/src/server/index.ts:952— `isObject(middlewareMode) && 'server' in middlewareMode` appears character-identically in 2 files — packages/core/src/server/index.ts, packages/core/src/server/preview.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/compose-v2-release-seal.mjs:41— `item.name === row.name && item.version === row.version` appears character-identically in 2 files — scripts/compose-v2-release-seal.mjs, scripts/seal-v2-rust-packages.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/incremental-release-producer.mjs:139— `manifest.scripts?.build && !/\bcargo\b|\bnapi\b|farm-plugin-tools build/.test(manifest.scripts.build)` appears character-identically in 2 files — scripts/incremental-release-producer.mjs, scripts/prepare-v2-candidate-js.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/check-pr-changesets.mjs:52— `name.endsWith('.md') && name !== 'README.md'` appears character-identically in 3 files — scripts/check-pr-changesets.mjs, scripts/check-stable-release-state.mjs, scripts/v2-release-preflight.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/seal-v2-platform-packages.mjs:42— `packed.name !== pkg.name || packed.version !== pkg.version` appears character-identically in 2 files — scripts/seal-v2-platform-packages.mjs, scripts/seal-v2-primary-packages.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate js-plugins/less/src/index.ts:73— `param.query.length === 0 && existsSync(param.resolvedPath)` appears character-identically in 2 files — js-plugins/less/src/index.ts, js-plugins/sass/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/release-rust-metadata.mjs:32— `pkg.name === record.name && pkg.version === record.version` appears character-identically in 2 files — scripts/release-rust-metadata.mjs, scripts/v2-auto-release.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/compose-v2-release-seal.mjs:84— `pkg.name === row.name && pkg.version === row.version` appears character-identically in 4 files — scripts/compose-v2-release-seal.mjs, scripts/prepare-cargo-version-proposal.mjs, scripts/prepare-sdk-frozen-lock.mjs, scripts/v2-rust-registry-reuse.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:79— `process.env.BRAINSTORM_DIR || '/tmp/brainstorm'` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:77— `process.env.BRAINSTORM_HOST || '127.0.0.1'` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:76— `process.env.BRAINSTORM_PORT || (49152 + Math.floor(Math.random() * 16383))` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:145— `req.method === 'GET' && req.url.startsWith('/files/')` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/server.cjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:56— `selected[0].querySelector('h3, .content h3, .card-body h3')?.textContent?.trim() || selected[0].dataset.choice` appears character-identically in 2 files — REDACTED, .claude/skills/brainstorming/scripts/helper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
P2 · Observability· Console output used as the logging channel · ×11
Console output used as the logging channel js-plugins/dts/src/options.ts:4— `js-plugins/dts/src/options.ts` reports through `console.*` at line 4 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel js-plugins/dts/src/utils.ts:29— `js-plugins/dts/src/utils.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel js-plugins/dts/src/utils.ts:34— `js-plugins/dts/src/utils.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel js-plugins/dts/src/utils.ts:80— `js-plugins/dts/src/utils.ts` reports through `console.*` at line 80 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel js-plugins/dts/src/utils.ts:366— `js-plugins/dts/src/utils.ts` reports through `console.*` at line 366 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/utils/share.ts:66— `packages/core/src/utils/share.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/utils/share.ts:70— `packages/core/src/utils/share.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/utils/share.ts:105— `packages/core/src/utils/share.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/server/preview.ts:307— `packages/core/src/server/preview.ts` reports through `console.*` at line 307 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/plugin/js/farm-to-vite-context.ts:30— `packages/core/src/plugin/js/farm-to-vite-context.ts` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/plugin/js/utils.ts:314— `packages/core/src/plugin/js/utils.ts` reports through `console.*` at line 314 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
README/code drift js-plugins/less/README.md:155— js-plugins/less/README.md names Less 3, but the manifest declares `less` ^4.1.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
README/code drift js-plugins/postcss/README.md:154— js-plugins/postcss/README.md names Less 3, but the manifest declares `less` ^4.1.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
README/code drift website/docs/features/css.md:213— website/docs/features/css.md names TailwindCSS 3, but the manifest declares `tailwindcss` 4.1.12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
README/code drift website/docs/features/script.md:166— website/docs/features/script.md names Vite 8, but the manifest declares `vite` ^5.2.6. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
Silent fallback default in catch js-plugins/postcss/tests/cache.integration.ts:46— `findManifests` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch js-plugins/postcss/tests/cache.integration.ts:79— `awaitCacheWrite` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/docs/src/machine-readable.ts:72— `resourcePath` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on Err crates/plugin_script/src/lib.rs:402— `handle_persistent_cached_module` turns every `Err` into `Ok(Some(true))` — 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 rust-plugins/url/src/lib.rs:38— `get_file_size` 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.
Subsumed condition operand rust-ecosystem/tailwindcss-node/tests/support/generated/urls.rs:200— `trimmed.starts_with("url(")` can never decide this `||` — every value satisfying `trimmed.starts_with("url(")` also satisfies `trimmed.contains("url(")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand rust-ecosystem/tailwindcss-node/src/urls.rs:204— `trimmed.starts_with("url(")` can never decide this `||` — every value satisfying `trimmed.starts_with("url(")` also satisfies `trimmed.contains("url(")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Mock-dominated test: retains a retired route when its response finishes before the upstream request closes packages/core/tests/runtime-proxy-lifecycle.spec.ts:17— This test sets up 5 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects/test.rs, crates/plugin_css/src/dep_analyzer.rs. Pair on, review, or document these before any departure.
No ADRs found REDACTED:13— 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 `REDACTED` makes this repository a deployable product (line 13).
D21 · Naming Consistency· `doImportCSSReplace` spells `CSS` where 14 names in the project spell it `Css` · ×1
`doImportCSSReplace` spells `CSS` where 14 names in the project spell it `Css` packages/core/src/utils/rebase-url.ts:182— 14 of 15 names in project farm-fe spell the token `Css` (14 of 15; unit: names in project farm-fe containing `Css`). Peers: index.getCss (examples/rust-plugin-auto-import-react/src/apis/css/index.ts:1); js-plugins.sass.src.CompileCssParams (js-plugins/sass/src/index.ts:151); index.isPotentialCssRootFile (js-plugins/tailwindcss/src/index.ts:288); Root.constructor(customCssResolver) (js-plugins/tailwindcss/src/index.ts:337); Root.customCssResolver (js-plugins/tailwindcss/src/index.ts:342). Rename to `doImportCssReplace`. [rule N6]
D21 · Naming Consistency· `moduleID` spells `ID` where 31 names in the project spell it `Id` · ×1
`moduleID` spells `ID` where 31 names in the project spell it `Id` rust-plugins/react/src/is_react_refresh_boundary.ts:199— 31 of 32 names in project farm-fe spell the token `Id` (31 of 32; unit: names in project farm-fe containing `Id`). Peers: comp-ts._withScopeId (crates/compiler/tests/fixtures/tree_shake/compiled-vue-comp/comp-ts.ts:6); LazyCompilationQueueItem.moduleId (crates/plugin_lazy_compilation/src/dynamic_module.ts:14); index.quoteCampaign(tenantId) (examples/commerce-lab/packages/sdk/src/index.ts:5); CampaignProduct.tenantId (examples/commerce-lab/packages/sdk/src/models.ts:3); CampaignQuote.tenantId (examples/commerce-lab/packages/sdk/src/models.ts:9). Rename to `moduleId`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 98 project(s) overshoot their size bounds, lowering Project Cohesion to 9.4/10. The most over is `(repository root)` (21591 LoC, 196 module-visible types across 5 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 94 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/core/src/types/binding.ts, rust-ecosystem/svgr-rs/src/hast_to_swc_ast/mappings.rs, rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs, rust-ecosystem/tailwindcss-node/src/compile.rs, crates/create-farm-rs/src/template.rs, crates/core/src/cache/scope.rs, rust-ecosystem/tailwindcss/src/design_system.rs, crates/create-farm-rs/src/utils/lte.rs (and 86 more) (106 orphaned of 554 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 554 of the 880 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 6/25 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/create-farm-rs`, `crates/create-farm-rs/templates/tauri/preact/src-tauri`, `crates/create-farm-rs/templates/tauri/react/src-tauri`, `crates/create-farm-rs/templates/tauri/solid/src-tauri`, `crates/create-farm-rs/templates/tauri/svelte/src-tauri` and 14 more.
No dependency-update automation REDACTED:34— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No security response headers detected website/vercel.json:1— 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 configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 3/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 144/175 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~1.4 `!` null assertions per 1k TypeScript source lines — 49 assertion(s) across the 33905 source line(s) of the 280 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/core/src/server/index.ts (10), packages/core/src/server/preview.ts (8), rust-plugins/react/src/is_react_refresh_boundary.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default on parse failure scripts/release-registry-selection.py:133— `valid_sha512` returns `False` when `(ValueError, binascii.Error)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/create-farm-rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.11.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.4"` requirement declared in rust-plugins/vue-jsx/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.11.1 but 1.12.1 is the current stable release on crates.io, and it already satisfies the `"1.10.1"` requirement declared in crates/utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: bytes-str — `bytes-str` is locked at 0.2.7 but 0.2.9 is the current stable release on crates.io, and it already satisfies the `"0.2.7"` requirement declared in crates/toolkit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes-str` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.5.8"` requirement declared in crates/create-farm-rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1.0.35"` requirement declared in crates/plugin_file_size/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: glob — `glob` is locked at 0.3.3 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3.1"` requirement declared in crates/macro_testing/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
Outdated: globset — `globset` is locked at 0.4.18 but 0.4.21 is the current stable release on crates.io, and it already satisfies the `"0.4.14"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p globset` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.14.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in rust-ecosystem/grass/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: insta — `insta` is locked at 1.47.2 but 1.49.0 is the current stable release on crates.io, and it already satisfies the `"1.39.0"` requirement declared in crates/testing_helpers/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p insta` 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.4.0"` requirement declared in crates/core/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: napi — `napi` is locked at 3.9.0 but 3.16.2 is the current stable release on crates.io, and it already satisfies the `"3.1.3"` requirement declared in crates/node/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p napi` and commit the updated REDACTED.
Outdated: napi-build — `napi-build` is locked at 2.3.2 but 2.6.0 is the current stable release on crates.io, and it already satisfies the `"2.2.3"` requirement declared in crates/node/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p napi-build` and commit the updated REDACTED.
Outdated: napi-derive — `napi-derive` is locked at 3.5.6 but 3.7.1 is the current stable release on crates.io, and it already satisfies the `"3.1.1"` requirement declared in crates/node/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p napi-derive` and commit the updated REDACTED.
Outdated: proc-macro2 — `proc-macro2` is locked at 1.0.106 but 1.0.107 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/macro_cache_item/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proc-macro2` and commit the updated REDACTED.
Outdated: quote — `quote` is locked at 1.0.45 but 1.0.47 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/macro_cache_item/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p quote` and commit the updated REDACTED.
Outdated: regex — `regex` is locked at 1.12.3 but 1.13.1 is the current stable release on crates.io, and it already satisfies the `"1.7.3"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p regex` and commit the updated REDACTED.
Outdated: relative-path — `relative-path` is locked at 2.0.1 but 2.0.3 is the current stable release on crates.io, and it already satisfies the `"2.0.1"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p relative-path` and commit the updated REDACTED.
Outdated: rkyv — `rkyv` is locked at 0.8.16 but 0.8.18 is the current stable release on crates.io, and it already satisfies the `"0.8.10"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rkyv` and commit the updated REDACTED.
Outdated: rust-embed — `rust-embed` is locked at 8.11.0 but 8.14.0 is the current stable release on crates.io, and it already satisfies the `"8.3"` requirement declared in crates/create-farm-rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rust-embed` and commit the updated REDACTED.
Outdated: rustc-hash — `rustc-hash` is locked at 2.1.2 but 2.1.3 is the current stable release on crates.io, and it already satisfies the `"2.0.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustc-hash` and commit the updated REDACTED.
Outdated: serde_derive — `serde_derive` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in patches/serde/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_derive` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.150 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: serde_regex — `serde_regex` is locked at 1.1.0 but 1.2.0 is the current stable release on crates.io, and it already satisfies the `"1.1.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_regex` and commit the updated REDACTED.
Outdated: swc_sourcemap — `swc_sourcemap` is locked at 10.0.2 but 10.0.3 is the current stable release on crates.io, and it already satisfies the `"10.0.2"` requirement declared in crates/toolkit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p swc_sourcemap` and commit the updated REDACTED.
doc comments repeat the names packages/cli/src/utils.ts:86— 2 of 9 documented parameters and 0 of 1 summaries in `@farmfe/cli` only repeat the member or parameter name (e.g. "config path" for `configPath`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/core/src/config/normalize-config/normalize-output.ts:259— 2 of 33 documented parameters and 8 of 208 summaries in `@farmfe/core` only repeat the member or parameter name (e.g. "logger instance" for `logger`). 5 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names js-plugins/sass/src/utils.ts:26— 0 of 1 documented parameters and 0 of 4 summaries in `@farmfe/js-plugin-sass` only repeat the member or parameter name (e.g. "" for `implementation`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names crates/compiler/tests/fixtures/tree_shake/self-executed/decl/var_side_effect/a.js:94— 0 of 14 documented parameters and 0 of 19 summaries in `farm-fe` only repeat the member or parameter name (e.g. "" for `props`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 23 file(s) — `crates/create-farm-rs/templates/electron/preact/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/react/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/solid/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/svelte/electron/electron-env.d.ts`, `crates/create-farm-rs/templates/electron/vanilla/electron/electron-env.d.ts`, … (+18 more) — 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 01a1db69-7828-7ac7-8e37-db591af24111 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 487 · Warnings: 1432 · Recommendations: 482 · Info: 33 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 18:54 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.