Public report of farm-fe/farm, published 28 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 28 October 2026, 01:43 UTC · Survey ID cd_044cad69f24c45e5a219dda2d37c6f4f
farm-fe/farm
Measured 28 October 2026, 01:26 UTC, at code version 2000ef8
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 2 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: 129,036 lines of product code in 318 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Security and Compliance, 23
Findings by how serious they are
339 critical948 serious150 minor
11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
28 October 2026, 01:26 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
81of 81 dimensions measured by tools.
1376of 1437 findings point to an exact file and line, so you can open each one in the code. The other 61 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 129,036 lines of product code in 318 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 in part because seven of the dependencies have a known vulnerability. It scores 35 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 23, is the weakest lens and counts most in the score. The best first steps are replacing the four exposed passwords or keys and switching the old ones off and fixing the two runtimes or frameworks that no longer get security updates, each worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 45.
142 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. 126 known security holes in the packages the code depends on can be used by attackers, and fourteen 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 eight passwords or keys in the code's history and the four passwords or keys in the code need replacing, with the old ones switched off. The 15 form fields without a label need a label.
The product code is 129,036 lines, about €130,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 Security and Compliance rose from 23 to 70, the lowest score rated Strong, the score would rise from 35 to about 45.
Code composition: what the lines of code are
Product code 87%Tests 13%
New since the last survey: 141 findings
These 141 critical or serious findings weren't in the previous survey, on 14 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Visual & motion safety · Focus outline removed in CSS without a :focus replacement website/src/theme/CodeBlock/index.module.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement website/src/pages/index.module.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement website/src/pages/index.module.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement website/src/components/TeamMembersItem/index.module.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/vite-adapter-vue/src/style.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/react-sass-js/src/components/card/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/react/src/components/card/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/public-path/src/components/card/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/less/src/components/card/index.less
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/vue/src/App.vue
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/vanilla/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/svelte/src/routes/+page.svelte
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/solid/src/App.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/react/src/App.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri2/preact/src/App.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/vue/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/vanilla/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/svelte/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/solid/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/react/src/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/create-farm-rs/templates/tauri/preact/src/styles.css
Visual & motion safety · Animation without a prefers-reduced-motion guard website/src/theme/CodeBlock/index.module.css
Visual & motion safety · Animation without a prefers-reduced-motion guard website/src/theme/CodeBlock/index.module.css
Visual & motion safety · Animation without a prefers-reduced-motion guard website/src/pages/index.module.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 179 findings
These 179 critical or serious findings were in the previous survey, on 14 October 2026, and are gone from this one. The first 100 are listed here.
Test Coverage · No test reaches this file rust-plugins/worker/scripts/index.js
Test Coverage · No test reaches this file rust-plugins/yaml/scripts/index.js
Test Coverage · No test reaches this file rust-plugins/react-components/scripts/index.js
Test Coverage · No test reaches this file rust-plugins/vue/scripts/index.js
Test Coverage · No test reaches this file scripts/test-examples.mjs
Test Coverage · No test reaches this file js-plugins/dts/src/logger.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/lit/src/my-element.ts
Test Coverage · No test reaches this file packages/plugin-tools/src/index.ts
Test Coverage · No test reaches this file rust-plugins/react/src/is_react_refresh_boundary.ts
Test Coverage · No test reaches this file js-plugins/less/src/plugin-resolve.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/client/src/index.ts
Test Coverage · No test reaches this file packages/core/src/server/error.ts
Test Coverage · No test reaches this file js-plugins/dts/src/index.ts
Test Coverage · No test reaches this file scripts/bump-create-farm-version.mjs
Test Coverage · No test reaches this file js-plugins/qiankun/src/qiankun-farm-plugin.ts
Test Coverage · No test reaches this file scripts/ready.mjs
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/preact/electron/main.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/react/electron/main.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/solid/electron/main.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/svelte/electron/main.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/vanilla/electron/main.ts
Test Coverage · No test reaches this file crates/create-farm-rs/templates/electron/vue/electron/main.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/client/src/http.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/index.ts
Test Coverage · No test reaches this file js-plugins/sass/src/utils.ts
Test Coverage · No test reaches this file REDACTED
Test Coverage · No test reaches this file packages/create-farm/create-farm.js
Test Coverage · No test reaches this file crates/create-farm-rs/templates/nestjs/index.plugin.ts
Test Coverage · No test reaches this file js-plugins/svgr/src/index.ts
Test Coverage · No test reaches this file packages/plugin-tools/src/prepublish.ts
Test Coverage · No test reaches this file scripts/logger.mjs
Test Coverage · No test reaches this file js-plugins/babel/src/index.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/node/utils/envinfo.ts
Test Coverage · No test reaches this file packages/create-farm-plugin/templates/js/src/index.ts
Test Coverage · No test reaches this file packages/plugin-tools/src/copy-artifacts.ts
Test Coverage · No test reaches this file rust-plugins/wasm/src/wasm_runtime.js
Test Coverage · No test reaches this file packages/runtime/src/modules/module-system-helper.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/client/src/stores/resourcePot.ts
Test Coverage · No test reaches this file js-plugins/sass/src/options.ts
Test Coverage · No test reaches this file js-plugins/visualizer/src/client/src/router.ts
Test Coverage · No test reaches this file js-plugins/less/src/utils.ts
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€42,000 to €210,000, for 696 to 2,208 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 35. 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: 129,036 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
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 €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 23 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 4 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 6 points for low effort, because it clears the 4 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 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 169,895 lines over the last 90 days, which is about 689,019 lines a year. At that pace, the extra work comes to an estimated 38.3 to 229.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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.
642 modules, with 1198 dependencies between them. 6 loops run through 65 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 602 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.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_plugin_vue_jsx.options uses serde.core.de, so a change to serde.core.de can break farmfe_plugin_vue_jsx.options, while a change to farmfe_plugin_vue_jsx.options can't break serde.core.de.
Position
Below the diagonal: farmfe_plugin_vue_jsx.options uses a module listed above it, which is the healthy direction.
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.config.config_regex uses farmfe_plugin_vue_jsx.options, so a change to farmfe_plugin_vue_jsx.options can break farmfe_core.config.config_regex, while a change to farmfe_core.config.config_regex can't break farmfe_plugin_vue_jsx.options.
Position
Below the diagonal: farmfe_core.config.config_regex 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_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_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_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_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.
21→23 farmfe_core.cache.module_cache uses farmfe_core.cachepart of a loop✕
Connections
1 pair of types, where a type in farmfe_core.cache.module_cache uses a type in farmfe_core.cache.
farmfe_core.cache.module_cache uses farmfe_core.cache, so a change to farmfe_core.cache can break farmfe_core.cache.module_cache, while a change to farmfe_core.cache.module_cache can't break farmfe_core.cache.
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.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.cache uses farmfe_core.cache.module_cache, so a change to farmfe_core.cache.module_cache can break farmfe_core.cache, while a change to farmfe_core.cache can't break farmfe_core.cache.module_cache.
Position
Below the diagonal: farmfe_core.cache uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.handle_entry_resource uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_core.plugin.hooks.handle_entry_resource, while a change to farmfe_core.plugin.hooks.handle_entry_resource can't break farmfe_core.module.
Position
Below the diagonal: farmfe_core.plugin.hooks.handle_entry_resource uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.handle_entry_resource uses farmfe_core.resource, so a change to farmfe_core.resource can break farmfe_core.plugin.hooks.handle_entry_resource, while a change to farmfe_core.plugin.hooks.handle_entry_resource can't break farmfe_core.resource.
Position
Below the diagonal: farmfe_core.plugin.hooks.handle_entry_resource uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.handle_entry_resource uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_core.plugin.hooks.handle_entry_resource, while a change to farmfe_core.plugin.hooks.handle_entry_resource can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_core.plugin.hooks.handle_entry_resource uses a module listed above it, which is the healthy direction.
farmfe_core.plugin.hooks.handle_entry_resource uses farmfe_core.module.module_group, so a change to farmfe_core.module.module_group can break farmfe_core.plugin.hooks.handle_entry_resource, while a change to farmfe_core.plugin.hooks.handle_entry_resource can't break farmfe_core.module.module_group.
Position
Below the diagonal: farmfe_core.plugin.hooks.handle_entry_resource 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.
farmfe_core.plugin uses farmfe_core.plugin.hooks.handle_entry_resource, so a change to farmfe_core.plugin.hooks.handle_entry_resource can break farmfe_core.plugin, while a change to farmfe_core.plugin can't break farmfe_core.plugin.hooks.handle_entry_resource.
Position
Below the diagonal: farmfe_core.plugin uses a module listed above it, which is the healthy direction.
25→26 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.
25→27 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_ecosystem_tailwindcss_node.source_maps, so a change to farmfe_ecosystem_tailwindcss_node.source_maps can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_ecosystem_tailwindcss_node.source_maps.
Position
Below the diagonal: farmfe_core.context 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.cache, so a change to farmfe_core.cache can break farmfe_core.context, while a change to farmfe_core.context can't break farmfe_core.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.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.hooks.handle_entry_resource, so a change to farmfe_core.plugin.hooks.handle_entry_resource 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.handle_entry_resource.
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_auto_import uses farmfe_toolkit.resolve.package_json_loader, so a change to farmfe_toolkit.resolve.package_json_loader can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_toolkit.resolve.package_json_loader.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses serde.core.de, so a change to serde.core.de can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break serde.core.de.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses farmfe_core.config.config_regex, so a change to farmfe_core.config.config_regex can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_core.config.config_regex.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_auto_import uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_auto_import, while a change to farmfe_plugin_auto_import can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_auto_import uses a module listed above it, which is the healthy direction.
farmfe_plugin_css uses farmfe_plugin_vue_jsx.options, so a change to farmfe_plugin_vue_jsx.options can break farmfe_plugin_css, while a change to farmfe_plugin_css can't break farmfe_plugin_vue_jsx.options.
Position
Below the diagonal: farmfe_plugin_css 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_html uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin.hooks.analyze_deps, so a change to farmfe_core.plugin.hooks.analyze_deps can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.hooks.analyze_deps.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin.hooks.handle_entry_resource, so a change to farmfe_core.plugin.hooks.handle_entry_resource can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.hooks.handle_entry_resource.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_html uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_html, while a change to farmfe_plugin_html can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_html uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.resource.resource_pot, so a change to farmfe_core.resource.resource_pot can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.resource.resource_pot.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.module.module_graph, so a change to farmfe_core.module.module_graph can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.module.module_graph.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.stats, so a change to farmfe_core.stats can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.stats.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_progress uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_progress, while a change to farmfe_plugin_progress can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_progress uses a module listed above it, which is the healthy direction.
farmfe_plugin_script uses farmfe_ecosystem_tailwindcss_node.source_maps, so a change to farmfe_ecosystem_tailwindcss_node.source_maps can break farmfe_plugin_script, while a change to farmfe_plugin_script can't break farmfe_ecosystem_tailwindcss_node.source_maps.
Position
Below the diagonal: farmfe_plugin_script 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.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.
farmfe_plugin_virtual uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_virtual uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_virtual uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_virtual uses farmfe_core.plugin.hooks.resolve, so a change to farmfe_core.plugin.hooks.resolve can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.plugin.hooks.resolve.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_virtual uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_virtual uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_virtual, while a change to farmfe_plugin_virtual can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_virtual uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_vue, while a change to farmfe_plugin_vue can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_vue uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue uses farmfe_core.plugin.hooks.load, so a change to farmfe_core.plugin.hooks.load can break farmfe_plugin_vue, while a change to farmfe_plugin_vue can't break farmfe_core.plugin.hooks.load.
Position
Below the diagonal: farmfe_plugin_vue uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_vue, while a change to farmfe_plugin_vue can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_vue uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_vue, while a change to farmfe_plugin_vue can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_vue uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_vue, while a change to farmfe_plugin_vue can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_vue uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_toolkit.resolve.package_json_loader, so a change to farmfe_toolkit.resolve.package_json_loader can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_toolkit.resolve.package_json_loader.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_core.module, so a change to farmfe_core.module can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_core.module.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_vue_jsx uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_vue_jsx, while a change to farmfe_plugin_vue_jsx can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_vue_jsx uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_toolkit.resolve.package_json_loader, so a change to farmfe_toolkit.resolve.package_json_loader can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_toolkit.resolve.package_json_loader.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses serde.core.de, so a change to serde.core.de can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break serde.core.de.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_core.config.config_regex, so a change to farmfe_core.config.config_regex can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_core.config.config_regex.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_core.config, so a change to farmfe_core.config can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_core.config.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_core.plugin.hooks.transform, so a change to farmfe_core.plugin.hooks.transform can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_core.plugin.hooks.transform.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_core.plugin, so a change to farmfe_core.plugin can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_core.plugin.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_core.context, so a change to farmfe_core.context can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_core.context.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
farmfe_plugin_react_components uses farmfe_plugin_auto_import, so a change to farmfe_plugin_auto_import can break farmfe_plugin_react_components, while a change to farmfe_plugin_react_components can't break farmfe_plugin_auto_import.
Position
Below the diagonal: farmfe_plugin_react_components uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64% · 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
A03:2025 — Software Supply Chain Failures
267
High / Critical
A05:2025 — Injection
200
High / Critical
A07:2025 — Authentication Failures
13
High / Critical
Roadmap
Immediately address the four leaked secrets in configuration files and the seven historical secret findings to eliminate credential exposure risks. Concurrently, remediate the two end-of-life runtime dependencies and the 106 high-severity dependency vulnerabilities to secure the platform's foundation. Finally, enforce supply-chain integrity by resolving the four workflow permission gaps and updating the dependency lock files to ensure provenance and signing compliance.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Per-file score 0–10 — a quality signature. Of 239 files carrying findings, judged against the Production bar: 5% slop · 58% mixed · 37% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
0.5
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
0.9
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
1.1
Slop
Static Analysis (SAST): High: 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.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
3.6
Slop
Static Analysis (SAST): High: 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
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
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 — 339
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 — 948
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 — 150
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 81 of 81 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 81 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, 1376 of 1437 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (throw new Error(), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 62 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 110 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (throw new Error(), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in crates/create-farm-rs/templates/nestjs/ was NOT MEASURED: the dependency install for crates/create-farm-rs/templates/nestjs/ failed in the analyzer sandbox (throw new Error(), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/nestjs/ was NOT MEASURED: the dependency install for examples/nestjs/ failed in the analyzer sandbox (throw new Error(), 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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`, … (+7 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.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 110 further occurrence(s) are not listed individually; the score already reflects all 150.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
76 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Parser::parse at 57. 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.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 76 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Parser::parse (cyclomatic 57), VueJsxTransformVisitor::transform_attrs (cyclomatic 53), VueJsxTransformVisitor::resolve_indexed_access (cyclomatic 46). — 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 76 together lifts Cyclomatic Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
179 method(s) exceeded the cognitive complexity threshold of 15; the worst was farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements at 161.
+ 88 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 120 down to 120 or less in Cognitive Complexity — start with farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements (cognitive 161), farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl (cognitive 131), VueJsxTransformVisitor::resolve_indexed_access (cognitive 122). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 2.8 to about 3.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.4 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 22 FunctionTooLong finding(s) in God Classes — start with variables.rs, expand_exports.rs, tree_shake_modules.rs. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 14 MethodTooLong finding(s) in God Classes — start with lib.rs (5), resolve_type.rs (4), utilities.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 12 FileTooLong finding(s) in God Classes — start with lib.rs (3), utilities.rs, resolve_type.rs. — One of this dimension's main actionable groups (12 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
103 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. Measured on part of this repository only: .ts (21% 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.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with svg_builder.rs (4), module_graph.rs (2), lib.rs (2). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with lib.rs (3), mod.rs, deps_analyzer.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with module_cache.rs, thread_safe_js_plugin_hook.rs, variables.rs. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.6 / 10Stronggated by 14 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
318 production modules (Cargo+npm), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 73 of the 318 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @farmfe/runtime-plugin-hmr · ×11
Unstable project farmfe_compiler
Unstable project farmfe_plugin_file_size
Unstable project farmfe_plugin_script
What to do
Resolve the 11 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Unstable project farmfe_compiler finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project farmfe_plugin_file_size finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 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).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
879 test methods: 324 unit, 553 integration, 0 BDD, 2 e2e. The JavaScript/TypeScript suite contributes 62 `it`/`test` case(s) across 22 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 817 `#[test]` function(s) across 151 file(s) declaring at least one; its unit/integration split is Cargo's own — 72 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 62 tests. Measured on the JavaScript/TypeScript suite only — at least 110 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: Binding - should parse config to rust correctlypackages/core/tests/binding.spec.ts:13
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with binding.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
28 outdated, 0 yanked direct Cargo dependencies. 111 of 119 direct crates were graded against crates.io (0 not published there, 8 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 · ×28
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: 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 943 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 9 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 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with statement_info.rs, render_resource_pots.rs, mangle_exports.rs. — One of this dimension's main actionable groups (5 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.
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs. Counted over 343 of the 615 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
76 deducted task-comment markers across 129036 LoC (0.1/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 73 TodoComment finding(s) in Explicit Debt — start with mod.rs (13), lib.rs (7), REDACTED (7). — One of this dimension's main actionable groups (73 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).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 366 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
200 finding(s): 0 critical, 172 high, 28 medium, 0 low. 142 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 37 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), … (+32 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 5 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
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
No action in Static Analysis (SAST) — all 142 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (142 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 106 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (105), REDACTED. — One of this dimension's main actionable groups (106 issue-level).
Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 7 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 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.
22 of 343 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/core/src/types/binding.ts. Counted over 343 of the 615 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 64 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 2 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels5.3 / 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
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.
`.copy-button` 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/theme/CodeBlock/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. — website/src/pages/index.module.css:53
`.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:121
`.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, …
`.copy-button svg` moves (`animation: popIn 0.3s ease forwards`) 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/theme/CodeBlock/index.module.css:67
`.copy-icon` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/theme/CodeBlock/index.module.css:75
`.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:85
`.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:153
`#__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
`.card` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/components/HomepageFeatures/styles.module.css:30
`.card-container:hover::before` moves (`animation: glowing 16s 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/components/HomepageFeatures/styles.module.css:68
`.card-container:after` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/components/HomepageFeatures/styles.module.css:88
`.card-container-content` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/components/HomepageFeatures/styles.module.css:97
`.logo` moves (`animation: logo-spin infinite 20s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/vite-adapter-solid/src/App.module.css:6
`.card:hover:before` moves (`animation: glowing 20s 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. (×4) — examples/react-sass-js/src/components/card/index.css:27, examples/react/src/components/card/index.css:27, examples/public-path/src/components/card/index.css:27, …
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 95 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · 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 repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
494 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 115 of 438 project(s) that lack one — worth up to 0.5 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
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 4, but the manifest declares `tailwindcss` ^3.3.2. 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
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 4, but the manifest declares `tailwindcss` ^3.3.2.
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:14
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 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 5/23 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 13 more.
`js-plugins/dts/src/logger.ts` reports through `console.*` at line 75 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/logger.ts:75
`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/logger.ts` reports through `console.*` at line 144 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/logger.ts:144
`packages/core/src/utils/logger.ts` reports through `console.*` at line 275 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/logger.ts:275
`packages/core/src/utils/logger.ts` reports through `console.*` at line 280 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/logger.ts:280
`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 248 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:248
`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
`packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 3 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/runtime-plugin-hmr/src/logger.ts:3
`packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 6 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/runtime-plugin-hmr/src/logger.ts:6
`packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 9 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/runtime-plugin-hmr/src/logger.ts:9
`packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 12 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/runtime-plugin-hmr/src/logger.ts:12
`packages/runtime-plugin-hmr/src/overlay.ts` reports through `console.*` at line 676 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/runtime-plugin-hmr/src/overlay.ts:676
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.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether 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 the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`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 `hmrUpdate` 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:141
`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:172
`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:26
`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:57
`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:70
`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:77, scripts/build.mjs:86
`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:81
`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:102, scripts/build.mjs:121
`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:107
`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. (×2) — scripts/build.mjs:168, scripts/build.mjs:192
`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:197
`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:269
`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. (×2) — scripts/build.mjs:271, scripts/build.mjs:320
`existsSync` 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. — scripts/build.mjs:289
`fs.readdirSync` in `buildRustPlugins` 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:319
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.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
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
5 duplicated blocks under js-plugins/ have copies in at least two of the sibling directories babel, dts, less, postcss, react-compiler, sass — 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. — js-plugins/less/src/index.ts:39
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
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 — 163 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
packages/core/src/server/index.ts:727 · packages/core/src/server/preview.ts:273 — the two spans are one implementation copied and then locally edited — 197 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:727
scripts/build.mjs:282 · scripts/build.mjs:332 — 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:282
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:160 · packages/core/binding/resolve-binding.cjs:191 — 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:160
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
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:322 · packages/core/src/watcher/index.ts:266 — 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:322
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
crates/create-farm-rs/templates/electron/preact/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/preact/farm.config.ts:3
packages/core/src/plugin/index.ts:209 · packages/core/src/plugin/index.ts:247 — the two spans are one implementation copied and then locally edited — 73 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/index.ts:209
packages/core/src/plugin/js/index.ts:182 · packages/core/src/plugin/js/index.ts:201 — 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/plugin/js/index.ts:182
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/less/src/utils.ts:7 reaches into another package with a relative path (../../REDACTED) — import the package by name instead. — js-plugins/less/src/utils.ts:7
js-plugins/postcss/src/utils.ts:6 reaches into another package with a relative path (../../REDACTED) — import the package by name instead. — js-plugins/postcss/src/utils.ts:6
js-plugins/sass/src/options.ts:7 reaches into another package with a relative path (../../REDACTED) — import the package by name instead. — js-plugins/sass/src/options.ts:7
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/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.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:23 reaches into another package with a relative path (../e2e/utils.mjs) — import the package by name instead. — scripts/test-e2e.mjs:23
scripts/test-e2e.mjs:23 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:23
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 (13 rows); move the shared test helper into a source directory production code may depend on (6 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.
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
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
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
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
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
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
applyHotUpdates has cyclomatic complexity 19 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. — REDACTED:93
farmRequire has cyclomatic complexity 19 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. — packages/runtime/src/module-system.ts:149
config has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — crates/create-farm-rs/templates/nestjs/index.plugin.ts:6
interopRequireWildcard has cyclomatic complexity 18 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. — packages/runtime/src/modules/module-helper.ts:107
convertPluginVite has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/plugin/js/index.ts:160
#resolveOptions has cyclomatic complexity 18 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. — packages/core/src/server/preview.ts:159
getResolvedOptions has cyclomatic complexity 17 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — js-plugins/dts/src/utils.ts:116
mergeFarmCliConfig has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/config/merge-config.ts:48
farmUserConfigToViteConfig has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/plugin/js/farm-to-vite-config.ts:14
htmlFallbackMiddleware has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/server/middlewares/htmlFallback.ts:9
handleResolveOptions has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — js-plugins/dts/src/context.ts:40
checkCompilationInputValue has cyclomatic complexity 15 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. — packages/core/src/config/normalize-config/index.ts:180
parseArgs has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/test-e2e.mjs:37
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.8 / 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.
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/server/index.ts has 692 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
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
packages/core/src/types/binding.ts has 503 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 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/config/schema.ts:1
packages/core/src/config/types.ts has 436 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
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage2.9 / 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 57 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, js-plugins/visualizer/src/client/src/pages/analysis/Bundle.vue, js-plugins/visualizer/src/client/src/components/NavBar.vue, js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue, js-plugins/visualizer/src/client/src/components/ResourcePots.vue and 51 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/dts/src/utils.ts:1, scripts/build.mjs: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 Code8.0 / 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.
Unreachable from the 191 application, 163 tooling and 230 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 (191 application, 163 tooling, 230 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 (×19) — packages/core/binding/resolve-binding.cjs, packages/core/src/server/error.ts, js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue, …
no import path from any entry point (191 application, 163 tooling, 230 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
This script imports the product ('../Card'), so it is an authored benchmark, not measurement input — but nothing invokes it: no REDACTED script, no CI workflow or build recipe, no Dockerfile, no other file under website/src/components/Benchmark/, and no in-repo reference to its name at all. It runs only if someone remembers to type `node website/src/components/Benchmark/index.tsx`, and it silently rots against the API it measures. Wire it into a script or workflow the way its wired siblings are, or delete it. — website/src/components/Benchmark/index.tsx
Nothing imports this binding — it is safe to review for removal. (×18) — js-plugins/dts/src/utils.ts:28, js-plugins/dts/src/utils.ts:33, js-plugins/dts/src/utils.ts:37, …
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. (×5) — crates/create-farm-rs/templates/electron/solid/svelte.config.js:1, crates/create-farm-rs/templates/electron/vanilla/svelte.config.js:1, rust-plugins/auto-import/tests/test.ts:3, …
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. (×6) — rust-plugins/auto-import/playground-vue/src/types/auto_import.d.ts:4, rust-plugins/icons/types/preact.d.ts:2, rust-plugins/icons/types/react.d.ts:2, …
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
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.
Every import is type-only — move it to devDependencies. — js-plugins/visualizer/src/dev.ts:2
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 · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`deleteUndefinedPropertyDeeply` is exported and takes `obj: any` from its caller, and it calls itself at line 217 (`deleteUndefinedPropertyDeeply`) with a piece of `obj` — and nowhere in `deleteUndefinedPropertyDeeply` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deleteUndefinedPropertyDeeply` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/core/src/plugin/js/utils.ts:217
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`starMaterial` is a `THREE.PointsMaterial`, which declares a disposal member, and it is created here (line 24). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using starMaterial = …;`), which releases it at the end of the scope on every path including a throw, or call `starMaterial.dispose()` in a `finally`. — website/src/components/StarrySky/index.js:24
`particleGeometry` is a `THREE.BufferGeometry`, which declares a disposal member, and it is created here (line 30). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using particleGeometry = …;`), which releases it at the end of the scope on every path including a throw, or call `particleGeometry.dispose()` in a `finally`. — website/src/components/StarrySky/index.js:30
`particleMaterial` is a `THREE.PointsMaterial`, which declares a disposal member, and it is created here (line 31). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using particleMaterial = …;`), which releases it at the end of the scope on every path including a throw, or call `particleMaterial.dispose()` in a `finally`. — website/src/components/StarrySky/index.js:31
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
`readConfigFile` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `FARM_PROFILE` environment variable (set at line 222, put back at line 229) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between — or by a promise that rejects at an `await`, and while this function is suspended at one every other callback the event loop runs sees the moved value too: the process then keeps the overwritten value for the rest of its life, and every later relative path, child-process launch or config read in ANY module resolves against it. That failure is silent and remote from its cause — the function that breaks is not the function that moved the directory. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — the `cwd` and `env` options of `child_process.spawn`/`exec`/`execSync` (or `Deno.Command`) scope both to the CHILD — or build absolute paths with `path.resolve`. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — packages/core/src/config/load-config-file.ts:156
What to do
Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a working directory or an environment variable passed to the operation that needs it (the `cwd` and `env` options of `child_process`, or of `Deno.Command`) is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, a `try`/`finally` is the least that makes the restore unconditional.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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
`ping` 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 })`. — REDACTED:310
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.8 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`Logo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — crates/create-farm-rs/templates/electron/vanilla/src/main.ts:9, crates/create-farm-rs/templates/vanilla/src/main.ts:9
`typescriptLogo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — crates/create-farm-rs/templates/electron/vanilla/src/main.ts:12, crates/create-farm-rs/templates/vanilla/src/main.ts:12
`message` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/runtime-plugin-hmr/src/overlay.ts:553
`description` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/runtime-plugin-hmr/src/overlay.ts:554
`description.replace(/\n/g,'<br>')` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/runtime-plugin-hmr/src/overlay.ts:565
`highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — packages/runtime-plugin-hmr/src/overlay.ts:646, packages/runtime-plugin-hmr/src/overlay.ts:707, packages/runtime-plugin-hmr/src/overlay.ts:746, …
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×14) — scripts/build.mjs:378, REDACTED:324, packages/runtime/src/module-system.ts:187, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/core/src/config/load-config-file.ts:261
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
136/167 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.6 `!` null assertions per 1k TypeScript source lines — 41 assertion(s) across the 26436 source line(s) of the 233 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 (9), packages/core/src/server/preview.ts (8), packages/core/src/server/ws.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
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 — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 23 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 47 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 — Not applicable: 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, 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.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
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) — 12 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (21 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — No web surface: 479 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. 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.
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.
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.
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.
Unlisted import 'react' rust-plugins/auto-import/tests/test.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'vue' rust-plugins/auto-import/tests/test.ts:1— 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:157— // 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:175— // 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:20— // 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:311— // 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 REDACTED:66— // 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:89— // 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:289— // 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.
TodoComment REDACTED:488— // TODO support relative and absolute external — 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:626— // TODO support meta and sideEffects — 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/config/schema.ts:210— // TODO add customResolver schema — 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/config/normalize-config/normalize-persistent-cache.ts:114— // TODO find latest lock file starting from root — 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 js-plugins/sass/src/index.ts:51— // @ts-ignore TODO fix it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment js-plugins/less/src/index.ts:38— // @ts-ignore TODO fix it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment js-plugins/electron/src/index.ts:4— // TODO: submit a PR to farm(export default 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 js-plugins/electron/src/index.ts:88— // TODO: .mjs file ext — 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.
+ 48 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×59
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:141— `fse.existsSync` in `hmrUpdate` 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:172— `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:26— `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:57— `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/dts/src/utils.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 scripts/build.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 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 js-plugins/tailwindcss/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 scripts/test-e2e.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/runtime/src/modules/dynamic-import.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/dts/src/context.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/react-compiler/src/types.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/cli/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/binding/resolve-binding.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 packages/runtime/src/module-system.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 scripts/test-e2e-worker.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/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 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/postcss/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/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 packages/runtime/src/modules/module-helper.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/cli/src/utils.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 rust-plugins/tailwindcss/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 rust-plugins/svgr/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.
+ 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×23
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:relative-cross-package] js-plugins/less/src/utils.ts:7— js-plugins/less/src/utils.ts:7 reaches into another package with a relative path (../../REDACTED) — import the package by name instead.
Boundary violation [package:relative-cross-package] js-plugins/postcss/src/utils.ts:6— js-plugins/postcss/src/utils.ts:6 reaches into another package with a relative path (../../REDACTED) — import the package by name instead.
Boundary violation [package:relative-cross-package] js-plugins/sass/src/options.ts:7— js-plugins/sass/src/options.ts:7 reaches into another package with a relative path (../../REDACTED) — 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/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.mjs:21— scripts/test-e2e.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.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.
Boundary violation [package:relative-cross-package] scripts/test-e2e.mjs:22— scripts/test-e2e.mjs:22 reaches into another package with a relative path (../e2e/process-cleanup.mjs) — import the package by name instead.
Boundary violation [package:test-suite-dependency] 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.
Boundary violation [package:relative-cross-package] scripts/test-e2e.mjs:23— scripts/test-e2e.mjs:23 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.mjs:23— scripts/test-e2e.mjs:23 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.
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:162— FunctionTooLong — farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_plugin_tree_shake::tree_shake_modules::trace_and_mark_write_imported_idents_statements crates/plugin_tree_shake/src/tree_shake_modules.rs:309— 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: farmfe_plugin_css::transform_css_to_script::transform_css_to_script_modules crates/plugin_css/src/transform_css_to_script.rs:38— FunctionTooLong — farmfe_plugin_css::transform_css_to_script::transform_css_to_script_modules 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: farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps crates/compiler/src/update/diff_and_patch_module_graph.rs:265— FunctionTooLong — farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps runs 146 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 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: 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 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.
FunctionTooLong: farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info crates/toolkit/src/script/analyze_statement/statement_info.rs:32— FunctionTooLong — farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info 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.
FunctionTooLong: roadmap.TimelineCpm website/src/pages/roadmap.tsx:29— 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: farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl crates/plugin_mangle_exports/src/mangle_exports.rs:251— FunctionTooLong — farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl 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.
FunctionTooLong: farmfe_toolkit::script::concatenate_modules::strip_modules_asts crates/toolkit/src/script/concatenate_modules/mod.rs:237— FunctionTooLong — farmfe_toolkit::script::concatenate_modules::strip_modules_asts 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.
FunctionTooLong: animated-beam.AnimatedBeam website/src/components/MagicUi/animated-beam.tsx:28— FunctionTooLong — AnimatedBeam runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_compiler::update::handle_update_modules::handle_update_modules crates/compiler/src/update/handle_update_modules.rs:12— FunctionTooLong — farmfe_compiler::update::handle_update_modules::handle_update_modules runs 123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_ecosystem_tailwindcss::candidate::parse_candidate rust-ecosystem/tailwindcss/src/candidate.rs:32— FunctionTooLong — farmfe_ecosystem_tailwindcss::candidate::parse_candidate 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.
FunctionTooLong: farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements crates/toolkit/src/script/concatenate_modules/strip_module_decl.rs:255— FunctionTooLong — farmfe_toolkit::script::concatenate_modules::strip_module_decl::strip_export_statements runs 119 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 19 over it, 1.19× 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_tailwindcss::attribute_selector_parser::parse rust-ecosystem/tailwindcss/src/attribute_selector_parser.rs:97— FunctionTooLong — farmfe_ecosystem_tailwindcss::attribute_selector_parser::parse runs 116 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 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.farmPlugin REDACTED:100— FunctionTooLong — farmPlugin runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: farmfe_ecosystem_tailwindcss::selector_parser::parse rust-ecosystem/tailwindcss/src/selector_parser.rs:90— FunctionTooLong — farmfe_ecosystem_tailwindcss::selector_parser::parse runs 107 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 7 over it, 1.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.
FunctionTooLong: farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators rust-ecosystem/tailwindcss/src/utils/math_operators.rs:41— FunctionTooLong — farmfe_ecosystem_tailwindcss::utils::math_operators::add_whitespace_around_math_operators runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:603— FunctionTooLong — farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_toolkit::script::module2cjs::transform_export_named crates/toolkit/src/script/module2cjs.rs:570— FunctionTooLong — farmfe_toolkit::script::module2cjs::transform_export_named runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: normalize-persistent-cache.normalizePersistentCache packages/core/src/config/normalize-config/normalize-persistent-cache.ts:21— FunctionTooLong — normalizePersistentCache runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: farmfe_plugin_auto_import::parser::scan_exports::scan_exports rust-plugins/auto-import/src/parser/scan_exports.rs:79— FunctionTooLong — farmfe_plugin_auto_import::parser::scan_exports::scan_exports runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×21
Focus outline removed in CSS without a :focus replacement website/src/theme/CodeBlock/index.module.css:55— `.copy-button` 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:53— `.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:121— `.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.
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::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:124— 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:309— 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::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:482— 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::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::ast::stringify (cognitive 20) rust-ecosystem/tailwindcss/src/ast.rs:55— farmfe_ecosystem_tailwindcss::ast::stringify has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (12 pts), if/else 5 (7 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_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:658— 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:455— 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::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 vulnerability · ×18
Swallowed exception (empty catch) scripts/build.mjs:378— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:324— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/src/module-system.ts:187— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/index.ts:113— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/utils/share.ts:188— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:85— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/server/middlewares/static.ts:73— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/config/load-config-file.ts:38— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/config/load-config-file.ts:245— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/config/load-config-file.ts:261— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/core/src/config/resolve-server.ts:20— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/src/config/normalize-config/normalize-external.ts:55— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) js-plugins/tailwindcss/src/index.ts:353— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) js-plugins/sass/src/index.ts:235— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) js-plugins/postcss/src/index.ts:97— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×14
Animation without a prefers-reduced-motion guard website/src/theme/CodeBlock/index.module.css:67— `.copy-button svg` moves (`animation: popIn 0.3s ease forwards`) 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/theme/CodeBlock/index.module.css:75— `.copy-icon` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/src/pages/index.module.css:85— `.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:153— `.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.
Animation without a prefers-reduced-motion guard website/src/components/HomepageFeatures/styles.module.css:30— `.card` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/src/components/HomepageFeatures/styles.module.css:68— `.card-container:hover::before` moves (`animation: glowing 16s 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/components/HomepageFeatures/styles.module.css:88— `.card-container:after` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/src/components/HomepageFeatures/styles.module.css:97— `.card-container-content` moves (`transition: background-position 350ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/vite-adapter-solid/src/App.module.css:6— `.logo` moves (`animation: logo-spin infinite 20s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/react-sass-js/src/components/card/index.css:27— `.card:hover:before` moves (`animation: glowing 20s 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 examples/react/src/components/card/index.css:27— `.card:hover:before` moves (`animation: glowing 20s 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 examples/public-path/src/components/card/index.css:27— `.card:hover:before` moves (`animation: glowing 20s 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 examples/less/src/components/card/index.less:27— `.card:hover:before` moves (`animation: glowing 20s 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.
MethodTooLong: VueJsxTransformVisitor.resolve_indexed_access rust-plugins/vue-jsx/src/resolve_type.rs:628— MethodTooLong — resolve_indexed_access runs 274 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 174 over it, 2.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UtilityRegistry.builtin rust-ecosystem/tailwindcss/src/utilities.rs:27— MethodTooLong — builtin runs 273 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 173 over it, 2.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: VueJsxTransformVisitor.transform_attrs rust-plugins/vue-jsx/src/lib.rs:517— MethodTooLong — transform_attrs runs 257 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 157 over it, 2.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExportsVisitor.visit_module_decl rust-plugins/auto-import/src/parser/parse.rs:169— 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:362— MethodTooLong — resolve_type_elements 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.
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: VueJsxTransformVisitor.transform_children rust-plugins/vue-jsx/src/lib.rs:895— 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: Compiler.update crates/compiler/src/update/mod.rs:145— MethodTooLong — update runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SideEffectsAnalyzer.visit_expr crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:302— MethodTooLong — visit_expr 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:124— MethodTooLong — load 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: VueJsxTransformVisitor.infer_runtime_type rust-plugins/vue-jsx/src/resolve_type.rs:978— 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: VueJsxTransformVisitor.extract_props_type rust-plugins/vue-jsx/src/resolve_type.rs:25— MethodTooLong — extract_props_type runs 111 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 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FarmfePluginCompress.finalize_resources rust-plugins/compress/src/lib.rs:88— MethodTooLong — finalize_resources runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
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 71) crates/toolkit/src/script/analyze_statement/statement_info.rs:32— farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info has cognitive complexity 71 (threshold 15). Drivers by points: match/switch 12 (38 pts), if/else 7 (23 pts), loops 3 (10 pts) (nesting depth added 49). 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::strip_module_decl::strip_import_statements (cognitive 46) 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 46 (threshold 15). Drivers by points: if/else 10 (35 pts), loops 3 (7 pts), match/switch 1 (4 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_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all (cognitive 43) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:603— 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::transform_to_esm::update_module_graph_edges_of_cjs_modules (cognitive 37) 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 37 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 4 (8 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.
farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_external_import (cognitive 32) 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 32 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (5 pts), match/switch 1 (5 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.
farmfe_toolkit::script::concatenate_modules::strip_modules_asts (cognitive 28) crates/toolkit/src/script/concatenate_modules/mod.rs:237— farmfe_toolkit::script::concatenate_modules::strip_modules_asts has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 5 (6 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_toolkit::sourcemap::collapse_sourcemap_chain (cognitive 28) crates/toolkit/src/sourcemap.rs:271— 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::module2cjs::transform_export_named (cognitive 25) crates/toolkit/src/script/module2cjs.rs:570— farmfe_toolkit::script::module2cjs::transform_export_named has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_toolkit::sourcemap::trace_module_sourcemap (cognitive 20) crates/toolkit/src/sourcemap.rs:82— 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:420— 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×13
farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps (cognitive 79) crates/compiler/src/update/diff_and_patch_module_graph.rs:265— 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:288— 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 34) crates/compiler/src/update/handle_update_modules.rs:12— farmfe_compiler::update::handle_update_modules::handle_update_modules has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 4 (9 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_compiler::update::patch_module_group_graph::patch_existing_added_non_dynamic_children (cognitive 34) crates/compiler/src/update/patch_module_group_graph.rs:402— 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::patch_module_group_graph::patch_any_module_group_for_toposort_modules (cognitive 31) crates/compiler/src/update/patch_module_group_graph.rs:598— farmfe_compiler::update::patch_module_group_graph::patch_any_module_group_for_toposort_modules has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (21 pts), loops 3 (8 pts), boolean chains 2 (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_compiler::update::patch_module_group_graph::patch_module_group_graph (cognitive 29) crates/compiler/src/update/patch_module_group_graph.rs:16— farmfe_compiler::update::patch_module_group_graph::patch_module_group_graph has cognitive complexity 29 (threshold 15). Drivers by points: loops 9 (18 pts), if/else 3 (10 pts), boolean chains 1 (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_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:149— 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 25) 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 25 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 7 (9 pts), match/switch 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::diff_and_patch_resource_pot_map (cognitive 22) crates/compiler/src/update/regenerate_resources/generate_and_diff_resource_pots.rs:303— farmfe_compiler::update::regenerate_resources::generate_and_diff_resource_pots::diff_and_patch_resource_pot_map has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 4 (10 pts), boolean chains 1 (nesting depth added 12). 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::build::resolve_module (cognitive 17) crates/compiler/src/build/mod.rs:655— 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:203— 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.
FileTooLong: src/lib.rs rust-plugins/vue-jsx/src/lib.rs— FileTooLong — 1162 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, 39-1489). The bar is 500 significant lines; this is 662 over it, 2.32× 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 — 956 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 108 free functions. The bar is 500 significant lines; this is 456 over it, 1.91× 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 — 941 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-1226). The bar is 500 significant lines; this is 441 over it, 1.88× 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: script/module2cjs.rs crates/toolkit/src/script/module2cjs.rs— FileTooLong — 757 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 257 over it, 1.51× 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: 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/lib.rs crates/swc_transformer_import_glob/src/lib.rs— FileTooLong — 602 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 102 over it, 1.20× 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: concatenate_modules/handle_external_modules.rs crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs— FileTooLong — 592 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 92 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/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: 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/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-736). 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: update/mod.rs crates/compiler/src/update/mod.rs— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: Compiler (78-690). The bar is 500 significant lines; this is 55 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
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::ast::optimize_ast (cyclomatic 17) rust-ecosystem/tailwindcss/src/ast.rs:124— 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::variants::resolve_functional (cyclomatic 17) rust-ecosystem/tailwindcss/src/variants.rs:482— 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::apply::process_nodes (cyclomatic 16) rust-ecosystem/tailwindcss/src/apply.rs:44— farmfe_ecosystem_tailwindcss::apply::process_nodes 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.
farmfe_ecosystem_tailwindcss::utilities::resolve_spacing (cyclomatic 16) rust-ecosystem/tailwindcss/src/utilities.rs:658— 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.
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.
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.
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:218— crates/toolkit/src/script/concatenate_modules/unique_idents.rs:218-223 | crates/toolkit/src/script/concatenate_modules/unique_idents.rs:237-242 — 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) rust-plugins/vue-jsx/src/lib.rs:1048— rust-plugins/vue-jsx/src/lib.rs:1048-1053 | rust-plugins/vue-jsx/src/lib.rs:1120-1125 — 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) 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-ecosystem/tailwindcss/src/utilities.rs:1018— rust-ecosystem/tailwindcss/src/utilities.rs:1018-1023 | rust-ecosystem/tailwindcss/src/utilities.rs:1049-1054 — 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.
Off the main sequence: @farmfe/runtime-plugin-hmr — @farmfe/runtime-plugin-hmr: 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/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: 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_plugin_types — farmfe_toolkit_plugin_types: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and depended on by 19 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 38 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.06, distance 0.88 — zone of pain — concrete and depended on by 46 project(s), so it's rigid to change.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×11
Untrusted text written into markup unescaped crates/create-farm-rs/templates/electron/vanilla/src/main.ts:9— `Logo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped crates/create-farm-rs/templates/electron/vanilla/src/main.ts:12— `typescriptLogo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped crates/create-farm-rs/templates/vanilla/src/main.ts:9— `Logo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped crates/create-farm-rs/templates/vanilla/src/main.ts:12— `typescriptLogo` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:553— `message` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:554— `description` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:565— `description.replace(/\n/g,'<br>')` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:646— `highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:707— `highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:746— `highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/runtime-plugin-hmr/src/overlay.ts:787— `highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
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:309— 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::find_dep_module_read_global_variables_dfs (cognitive 40) crates/plugin_tree_shake/src/tree_shake_modules.rs:608— 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:206— 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::remove_export_idents (cognitive 32) crates/plugin_tree_shake/src/tree_shake_modules/remove_export_idents.rs:112— farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::remove_export_idents has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 5 (10 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::is_module_contains_reexport_ident (cognitive 27) crates/plugin_tree_shake/src/tree_shake_modules/remove_export_idents.rs:58— farmfe_plugin_tree_shake::tree_shake_modules::remove_export_idents::is_module_contains_reexport_ident has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 1 (4 pts), loops 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.
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:18— 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::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.
VueJsxTransformVisitor::resolve_indexed_access (cognitive 122) rust-plugins/vue-jsx/src/resolve_type.rs:628— 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:517— 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:362— 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:895— 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:978— 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:187— 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:1140— 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/compiler/src/build/mod.rs:169— crates/compiler/src/build/mod.rs:169-182 | crates/compiler/src/update/mod.rs:229-242 — `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 40 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 (14 lines × 2) crates/plugin_html/src/deps_analyzer.rs:116— crates/plugin_html/src/deps_analyzer.rs:116-129 | crates/plugin_html/src/deps_analyzer.rs:172-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/plugin_library/src/lib.rs:462— crates/plugin_library/src/lib.rs:462-475 | crates/plugin_library/src/lib.rs:494-507 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/swc_transformer_import_glob/src/lib.rs:194— crates/swc_transformer_import_glob/src/lib.rs:194-207 | crates/swc_transformer_import_glob/src/lib.rs:220-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) 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.
Duplicated block (14 lines × 2) rust-plugins/auto-import/src/lib.rs:137— rust-plugins/auto-import/src/lib.rs:137-150 | 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.
Duplicated block (14 lines × 2) rust-plugins/vue-jsx/src/directive.rs:93— rust-plugins/vue-jsx/src/directive.rs:93-106 | rust-plugins/vue-jsx/src/directive.rs:241-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) 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.
VueJsxTransformVisitor::transform_attrs (cyclomatic 53) rust-plugins/vue-jsx/src/lib.rs:517— 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:628— 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:362— 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:978— 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:895— 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:1140— 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.
Duplicated block (12 lines × 2) crates/compiler/src/build/module_cache.rs:343— crates/compiler/src/build/module_cache.rs:343-354 | crates/compiler/src/build/module_cache.rs:379-390 — 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) crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:354— crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:354-365 | crates/node/src/plugin_adapters/js_plugin_adapter/thread_safe_js_plugin_hook.rs:395-406 — 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/svgr-rs/src/transform_svg_component/variables.rs:376— rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:376-387 | rust-ecosystem/svgr-rs/src/transform_svg_component/variables.rs:389-400 — 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/tailwindcss/src/utilities.rs:450— rust-ecosystem/tailwindcss/src/utilities.rs:450-461 | rust-ecosystem/tailwindcss/src/utilities.rs:608-619 — 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-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.
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.
Duplicated block (11 lines × 2) crates/core/src/cache/module_cache/mutable_modules.rs:118— crates/core/src/cache/module_cache/mutable_modules.rs:118-128 | crates/core/src/cache/resource_cache/resource_pot.rs:76-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/plugin_partial_bundling/src/analyze_module_graph.rs:122— crates/plugin_partial_bundling/src/analyze_module_graph.rs:122-132 | crates/plugin_partial_bundling/src/analyze_module_graph.rs:165-175 — 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:1397— rust-ecosystem/tailwindcss/src/utilities.rs:1397-1407 | rust-ecosystem/tailwindcss/src/utilities.rs:1431-1441 — 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/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.
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-ecosystem/tailwindcss/src/utilities.rs:1189— rust-ecosystem/tailwindcss/src/utilities.rs:1189-1199 | rust-ecosystem/tailwindcss/src/utilities.rs:1211-1221 — 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/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/plugin_css/src/lib.rs:660— crates/plugin_css/src/lib.rs:660-669 | crates/plugin_script/src/lib.rs:565-575 — 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 (10 lines × 2) crates/toolkit/src/script/analyze_statement/statement_info.rs:81— crates/toolkit/src/script/analyze_statement/statement_info.rs:81-90 | crates/toolkit/src/script/analyze_statement/statement_info.rs:92-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) rust-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.
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.
Duplicated block (10 lines × 2) rust-plugins/sass/src/rebase_urls.rs:64— rust-plugins/sass/src/rebase_urls.rs:64-73 | rust-plugins/sass/src/rebase_urls.rs:84-94 — 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/compiler/src/update/handle_update_modules.rs:34— crates/compiler/src/update/handle_update_modules.rs:34-43 | crates/compiler/src/update/handle_update_modules.rs:165-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/compiler/src/build/mod.rs:557— crates/compiler/src/build/mod.rs:557-565 | crates/compiler/src/update/mod.rs:486-494 — `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 40 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) 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.
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.
Duplicated block (9 lines × 2) rust-ecosystem/tailwindcss-node/src/compile.rs:111— rust-ecosystem/tailwindcss-node/src/compile.rs:111-119 | rust-ecosystem/tailwindcss-node/src/compile.rs:128-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) rust-plugins/auto-import/src/parser/scan_dirs_exports.rs:39— rust-plugins/auto-import/src/parser/scan_dirs_exports.rs:39-43 | rust-plugins/react-components/src/find_local_components.rs:364-368 — 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 (5 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:365— rust-plugins/vue-jsx/src/resolve_type.rs:365-369 | rust-plugins/vue-jsx/src/resolve_type.rs:404-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) rust-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) crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_importers.rs:19— crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_importers.rs:19-23 | crates/node/src/plugin_adapters/js_plugin_adapter/context_methods/vite_get_modules_by_file.rs:36-40 — 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-ecosystem/tailwindcss/src/utilities.rs:1281— rust-ecosystem/tailwindcss/src/utilities.rs:1281-1285 | rust-ecosystem/tailwindcss/src/utilities.rs:1295-1299 — 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.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) rust-plugins/vue-jsx/src/resolve_type.rs:1144— rust-plugins/vue-jsx/src/resolve_type.rs:1144-1148 | rust-plugins/vue-jsx/src/resolve_type.rs:1150-1154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/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.
Duplicated block (7 lines × 2) crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:130— crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:130-136 | crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:267-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
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:34— crates/plugin_html/src/deps_analyzer.rs:34-40 | 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.
Duplicated block (7 lines × 2) rust-plugins/vue-jsx/src/directive.rs:86— rust-plugins/vue-jsx/src/directive.rs:86-92 | rust-plugins/vue-jsx/src/directive.rs:231-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.
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: 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: FarmPluginScript (LCOM4 7) crates/plugin_script/src/lib.rs:74— FarmPluginScript's methods fall into 7 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 7 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:122— 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:53— 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.
Dead file (~56 LoC) crates/create-farm-rs/templates/electron/preact/electron/main.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/preact/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/react/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/solid/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/svelte/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/vanilla/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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 (~24 LoC) crates/create-farm-rs/templates/electron/vue/electron/preload.ts— no import path from any entry point (191 application, 163 tooling, 230 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
farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info (cyclomatic 37) crates/toolkit/src/script/analyze_statement/statement_info.rs:32— farmfe_toolkit::script::analyze_statement::statement_info::analyze_statement_info has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
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::handle_external_modules::handle_ambiguous_export_all (cyclomatic 20) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:603— 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::concatenate_modules::strip_modules_asts (cyclomatic 19) crates/toolkit/src/script/concatenate_modules/mod.rs:237— farmfe_toolkit::script::concatenate_modules::strip_modules_asts 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_toolkit::script::transform_to_esm::update_module_graph_edges_of_cjs_modules (cyclomatic 16) crates/toolkit/src/script/transform_to_esm/mod.rs:111— farmfe_toolkit::script::transform_to_esm::update_module_graph_edges_of_cjs_modules 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.
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 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 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 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-03-16..2026-06-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-16 08:34:49 +08:00' --until='2026-06-14 08:34:49 +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: crates/compiler/src/generate/render_resource_pots.rs crates/compiler/src/generate/render_resource_pots.rs:22— crates/compiler/src/generate/render_resource_pots.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in farmfe_compiler::generate::render_resource_pots::render_resource_pots_and_generate_resources at line 22. 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-03-16..2026-06-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-16 08:34:49 +08:00' --until='2026-06-14 08:34:49 +08:00' --full-history --no-merges -- crates/compiler/src/generate/render_resource_pots.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_mangle_exports/src/mangle_exports.rs crates/plugin_mangle_exports/src/mangle_exports.rs:251— 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 27 in farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl at line 251. 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-03-16..2026-06-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-16 08:34:49 +08:00' --until='2026-06-14 08:34:49 +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/toolkit/src/script/concatenate_modules/handle_external_modules.rs crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:603— crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in farmfe_toolkit::script::concatenate_modules::handle_external_modules::handle_ambiguous_export_all at line 603. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-03-16..2026-06-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-16 08:34:49 +08:00' --until='2026-06-14 08:34:49 +08:00' --full-history --no-merges -- crates/toolkit/src/script/concatenate_modules/handle_external_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: crates/swc_transformer_import_glob/src/lib.rs crates/swc_transformer_import_glob/src/lib.rs:821— crates/swc_transformer_import_glob/src/lib.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in farmfe_swc_transformer_import_glob::get_object_literal at line 821. 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-03-16..2026-06-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-16 08:34:49 +08:00' --until='2026-06-14 08:34:49 +08:00' --full-history --no-merges -- crates/swc_transformer_import_glob/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.
farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl (cognitive 131) crates/plugin_mangle_exports/src/mangle_exports.rs:251— farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl has cognitive complexity 131 (threshold 15). Drivers by points: match/switch 8 (59 pts), if/else 12 (54 pts), loops 5 (18 pts) (nesting depth added 106). 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_plugin_mangle_exports::mangle_exports::find_imports_to_rename (cognitive 95) crates/plugin_mangle_exports/src/mangle_exports.rs:153— 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:482— 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:26— 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:51— 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.
ClassTooLong: VueJsxTransformVisitor rust-plugins/vue-jsx/src/lib.rs:39— ClassTooLong — 1002 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 39-1489. The bar is 400 significant lines; this is 602 over it, 2.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: 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: 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-736. 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 (8 lines × 2) crates/plugin_partial_bundling/src/analyze_module_graph.rs:44— crates/plugin_partial_bundling/src/analyze_module_graph.rs:44-51 | crates/plugin_partial_bundling/src/analyze_module_graph.rs:67-74 — 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 (8 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:372— rust-plugins/vue-jsx/src/resolve_type.rs:372-379 | rust-plugins/vue-jsx/src/resolve_type.rs:411-418 — 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 (8 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:432— rust-plugins/vue-jsx/src/resolve_type.rs:432-439 | rust-plugins/vue-jsx/src/resolve_type.rs:454-461 — 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 (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-plugins/auto-import/src/parser/scan_exports.rs:179— rust-plugins/auto-import/src/parser/scan_exports.rs:179-186 | rust-plugins/auto-import/src/parser/scan_exports.rs:190-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure· 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>.
farmfe_compiler::update::diff_and_patch_module_graph::diff_module_deps (cyclomatic 34) crates/compiler/src/update/diff_and_patch_module_graph.rs:265— 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 17) crates/compiler/src/update/handle_update_modules.rs:12— farmfe_compiler::update::handle_update_modules::handle_update_modules 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_compiler::update::patch_module_group_graph::patch_removed_dynamic_import_and_dynamic_entry (cyclomatic 16) crates/compiler/src/update/patch_module_group_graph.rs:288— 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.
farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl (cyclomatic 27) crates/plugin_mangle_exports/src/mangle_exports.rs:251— farmfe_plugin_mangle_exports::mangle_exports::update_exports_meta_and_module_decl 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::find_imports_to_rename (cyclomatic 22) crates/plugin_mangle_exports/src/mangle_exports.rs:153— 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:26— 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:482— 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.
ImportGlobVisitor::glob_and_filter_sources (cognitive 43) crates/swc_transformer_import_glob/src/lib.rs:463— ImportGlobVisitor::glob_and_filter_sources has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (33 pts), match/switch 2 (5 pts), loops 3 (4 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.
ImportGlobVisitor::try_alias (cognitive 27) crates/swc_transformer_import_glob/src/lib.rs:315— ImportGlobVisitor::try_alias has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, 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::visit_mut_expr (cognitive 24) crates/swc_transformer_import_glob/src/lib.rs:677— ImportGlobVisitor::visit_mut_expr has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 12). 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::find_rel_source (cognitive 20) crates/swc_transformer_import_glob/src/lib.rs:399— ImportGlobVisitor::find_rel_source 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:241— 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.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×4
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.
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/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 (17 matched lines × 2 locations) packages/core/src/plugin/index.ts:209— packages/core/src/plugin/index.ts:209 · packages/core/src/plugin/index.ts:247 — the two spans are one implementation copied and then locally edited — 73 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.
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:356— // // 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.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs (cognitive 109) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:162— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs has cognitive complexity 109 (threshold 15). Drivers by points: if/else 23 (72 pts), loops 10 (21 pts), match/switch 3 (13 pts), boolean chains 3 (nesting depth added 70). 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:476— 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:97— 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_auto_import::parser::scan_exports::scan_exports (cognitive 47) rust-plugins/auto-import/src/parser/scan_exports.rs:79— farmfe_plugin_auto_import::parser::scan_exports::scan_exports has cognitive complexity 47 (threshold 15). Drivers by points: if/else 7 (26 pts), loops 5 (19 pts), match/switch 1 (2 pts) (nesting depth added 34). To reduce it, split the body into named stages: move each independent 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.
SourceReplacer::visit_mut_url (cognitive 46) crates/plugin_css/src/source_replacer.rs:44— SourceReplacer::visit_mut_url has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (37 pts), loops 1 (4 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SourceReplacer::replace_source_with_id (cognitive 28) crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:124— SourceReplacer::replace_source_with_id has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (28 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:104— 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:336— 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:233— 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:88— 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.
Resolver::try_alias (cognitive 38) crates/plugin_resolve/src/resolver.rs:426— Resolver::try_alias has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (32 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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_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:209— 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.
TooManyMethods: Compiler crates/compiler/src/lib.rs:31— TooManyMethods — 44 methods, declared across 6 files: build/mod.rs (15), update/mod.rs (10), write/mod.rs (9), src/lib.rs (5), +2 more file(s). The bar is 30 methods; this is 14 over it, 1.47× 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: 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:42— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (17 lines × 2) crates/compiler/src/build/mod.rs:681— crates/compiler/src/build/mod.rs:681-697 | crates/compiler/src/update/mod.rs:739-755 — `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 40 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 (17 lines × 2) crates/toolkit/src/css.rs:131— crates/toolkit/src/css.rs:131-147 | crates/toolkit/src/script/merge_swc_globals.rs:72-88 — 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 (17 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:201— rust-plugins/vue-jsx/src/resolve_type.rs:201-217 | rust-plugins/vue-jsx/src/resolve_type.rs:233-249 — 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/compiler/src/build/finalize_module_graph.rs:63— crates/compiler/src/build/finalize_module_graph.rs:63-77 | crates/compiler/src/update/finalize_module_graph.rs:54-68 — 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 (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.
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_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.
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:322— packages/core/src/server/index.ts:322 · packages/core/src/watcher/index.ts:266 — 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.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the function that made it · ×3
Disposable created and abandoned in the function that made it website/src/components/StarrySky/index.js:24— `starMaterial` is a `THREE.PointsMaterial`, which declares a disposal member, and it is created here (line 24). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using starMaterial = …;`), which releases it at the end of the scope on every path including a throw, or call `starMaterial.dispose()` in a `finally`.
Disposable created and abandoned in the function that made it website/src/components/StarrySky/index.js:30— `particleGeometry` is a `THREE.BufferGeometry`, which declares a disposal member, and it is created here (line 30). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using particleGeometry = …;`), which releases it at the end of the scope on every path including a throw, or call `particleGeometry.dispose()` in a `finally`.
Disposable created and abandoned in the function that made it website/src/components/StarrySky/index.js:31— `particleMaterial` is a `THREE.PointsMaterial`, which declares a disposal member, and it is created here (line 31). Every use of it in this block calls or writes a member through it — it is never returned, never stored, never handed to anything else, its members' values are never handed on, it is not captured by a callback, and it is never released — so this block both creates the value and is the last thing that can release it, and does not. The type's own disposal member says it holds something that has to be given back, and nothing here gives it back, once per CALL. Declare it with `using` (`using particleMaterial = …;`), which releases it at the end of the scope on every path including a throw, or call `particleMaterial.dispose()` in a `finally`.
farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs (cyclomatic 40) crates/plugin_script_meta/src/plugin_exports/expand_exports.rs:162— farmfe_plugin_script_meta::plugin_exports::expand_exports::expand_module_exports_dfs has cyclomatic complexity 40 (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:476— 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:309— 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:206— 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.
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.
Parser::parse (cognitive 121) rust-ecosystem/tailwindcss/src/parser.rs:116— Parser::parse has cognitive complexity 121 (threshold 15). Drivers by points: if/else 35 (98 pts), boolean chains 18, match/switch 4, loops 1 (nesting depth added 63). 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.
farmfe_swc_transformer_import_glob::get_object_literal (cognitive 68) crates/swc_transformer_import_glob/src/lib.rs:821— 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 (cognitive 29) crates/swc_transformer_import_glob/src/lib.rs:50— farmfe_swc_transformer_import_glob::transform_import_meta_glob has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
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.
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.
farmfe_plugin_runtime::render_resource_pot::scope_hoisting::build_scope_hoisted_module_groups (cognitive 31) 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 31 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 5 (12 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_html::deps_analyzer::get_script_src_or_code (cognitive 20) crates/plugin_html/src/deps_analyzer.rs:109— 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:168— 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.
farmfe_plugin_library::replace_internal_import_sources_with_placeholders (cognitive 18) crates/plugin_library/src/lib.rs:437— 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.
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.
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.
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.
Duplicated block (18 lines × 2) rust-plugins/auto-import/src/parser/parse.rs:407— rust-plugins/auto-import/src/parser/parse.rs:407-424 | rust-plugins/auto-import/src/parser/parse.rs:477-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:758— rust-plugins/vue-jsx/src/resolve_type.rs:758-775 | rust-plugins/vue-jsx/src/resolve_type.rs:908-925 — 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 (16 lines × 2) rust-ecosystem/tailwindcss/src/design_system.rs:183— rust-ecosystem/tailwindcss/src/design_system.rs:183-198 | rust-ecosystem/tailwindcss/src/design_system.rs:227-242 — 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 (16 lines × 2) rust-plugins/vue-jsx/src/directive.rs:158— rust-plugins/vue-jsx/src/directive.rs:158-173 | rust-plugins/vue-jsx/src/directive.rs:184-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:187— crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:187-194 | crates/plugin_runtime/src/render_resource_pot/source_replacer.rs:268-276 — 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 (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:637-644 — 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.
End-of-life runtime: Node.js 10 rust-plugins/yaml/npm/win32-x64-msvc/REDACTED:16— 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.
End-of-life runtime: Node.js 16 packages/cli/REDACTED:40— packages/cli/REDACTED declares Node.js 16 as this project's engines.node, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 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.
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:160— packages/core/binding/resolve-binding.cjs:160 · packages/core/binding/resolve-binding.cjs:191 — 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×2
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: ping REDACTED:310— `ping` 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 })`.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 95 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Parser::parse (cyclomatic 57) rust-ecosystem/tailwindcss/src/parser.rs:116— Parser::parse has cyclomatic complexity 57 (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 38) REDACTED:100— 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.
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.
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.
ExportsVisitor::visit_module_decl (cyclomatic 31) rust-plugins/auto-import/src/parser/parse.rs:169— 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.
SideEffectsAnalyzer::visit_expr (cyclomatic 30) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:302— SideEffectsAnalyzer::visit_expr 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 27) packages/core/src/server/ws.ts:165— WsServer.createWebSocketServer has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 12 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 245, 188, 285, …). 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.
build.buildExamples (cyclomatic 26) scripts/build.mjs:69— build.buildExamples has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (resolveRustPluginsForExample, hasPrebuiltRustPluginArtifact, a function literal at line 133, …). 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.
proxy.proxyMiddleware (cyclomatic 25) REDACTED:22— proxy.proxyMiddleware has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 96, 126, 44, …). 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.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.
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.
farmfe_swc_transformer_import_glob::get_object_literal (cyclomatic 23) crates/swc_transformer_import_glob/src/lib.rs:821— farmfe_swc_transformer_import_glob::get_object_literal has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
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 210, a function literal at line 248, 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.Tabs (cyclomatic 21) website/src/theme/ManagerTabs/index.tsx:57— index.Tabs has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 97, 114, 127, …). 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.
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.
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.
HmrClient.applyHotUpdates (cyclomatic 20) REDACTED:93— HmrClient.applyHotUpdates 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.
module-system.farmRequire (cyclomatic 20) packages/runtime/src/module-system.ts:149— 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.
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.
farmfe_plugin_auto_import::parser::scan_exports::scan_exports (cyclomatic 18) rust-plugins/auto-import/src/parser/scan_exports.rs:79— farmfe_plugin_auto_import::parser::scan_exports::scan_exports 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.
module-helper.interopRequireWildcard (cyclomatic 18) packages/runtime/src/modules/module-helper.ts:107— 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.
index.CodeBlockWrapper (cyclomatic 18) REDACTED:11— index.CodeBlockWrapper has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 4 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.
farmfe_plugin_resolve::resolver::exports::walk (cyclomatic 17) crates/plugin_resolve/src/resolver/exports.rs:288— farmfe_plugin_resolve::resolver::exports::walk 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.
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.
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.
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.
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.
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:336— 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.
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.
ImportGlobVisitor::try_alias (cyclomatic 16) crates/swc_transformer_import_glob/src/lib.rs:315— ImportGlobVisitor::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.
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:256— 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.
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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
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 210, a function literal at line 248, 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.
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.
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.
proxy.proxyMiddleware (cognitive 52) REDACTED:22— proxy.proxyMiddleware has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (47 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 28). Most of this is not in the body itself: 1 of the 52 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 96, 126, 44, …). 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.applyHotUpdates (cognitive 49) REDACTED:93— HmrClient.applyHotUpdates has cognitive complexity 49 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 8 (17 pts), ternaries 2 (9 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 30). Of this number, 43 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.
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:169— 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.
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.
build.buildExamples (cognitive 44) scripts/build.mjs:69— build.buildExamples has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (29 pts), ternaries 3 (6 pts), loops 4 (5 pts), boolean chains 3, error handling 1 (nesting depth added 19). Of this number, 23 points are the body's own statements and 21 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SideEffectsAnalyzer::visit_expr (cognitive 43) crates/plugin_tree_shake/src/statement_graph/analyze_statement_side_effects.rs:302— 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.
index.farmPlugin (cognitive 40) REDACTED:100— 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.
farmfe_plugin_resolve::resolver::exports::walk (cognitive 38) crates/plugin_resolve/src/resolver/exports.rs:288— farmfe_plugin_resolve::resolver::exports::walk has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (34 pts), boolean chains 2, loops 1 (2 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.
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.
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:149— 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.
FeaturesAnalyzer::analyze (cognitive 31) crates/plugin_script_meta/src/plugin_features/features_analyzer.rs:21— FeaturesAnalyzer::analyze has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 3 (7 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.
index.farmPostcssPlugin (cognitive 31) js-plugins/postcss/src/index.ts:31— index.farmPostcssPlugin has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (6 pts), ternaries 1 (5 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 15). Of this number, 21 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
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.
WsServer.createWebSocketServer (cognitive 28) packages/core/src/server/ws.ts:165— WsServer.createWebSocketServer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 10, error handling 1, ternaries 1 (nesting depth added 3). Of this number, 15 points are the body's own statements and 13 belong to 5 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.
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.
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:68— 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.
FarmPluginScript::process_resource_pots (cognitive 25) crates/plugin_script/src/lib.rs:308— FarmPluginScript::process_resource_pots has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 3 (8 pts), boolean chains 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_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.Tabs (cognitive 25) website/src/theme/ManagerTabs/index.tsx:57— index.Tabs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 5). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 97, 114, 127, …). 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.
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.
FarmPluginStaticAssets::transform (cognitive 24) crates/plugin_static_assets/src/lib.rs:169— 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.
RequireEsmReplacer::visit_mut_expr (cognitive 24) crates/toolkit/src/script/transform_to_esm/transform_cjs.rs:316— RequireEsmReplacer::visit_mut_expr has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (23 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_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.
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.
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.
module-helper.interopRequireWildcard (cognitive 22) packages/runtime/src/modules/module-helper.ts:107— 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.
Theme::resolve_key (cognitive 21) rust-ecosystem/tailwindcss/src/theme.rs:426— 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.
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.
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.
dynamic-import.load (cognitive 20) packages/runtime/src/modules/dynamic-import.ts:109— dynamic-import.load 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:44— 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.
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.
ModuleSystemAnalyzer::visit_member_expr (cognitive 18) crates/toolkit/src/script/module_system.rs:67— 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.
FarmPluginVue::load (cognitive 18) rust-plugins/vue/src/lib.rs:427— 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.
HmrEngine.hmrUpdate (cognitive 18) packages/core/src/server/hmr-engine.ts:129— HmrEngine.hmrUpdate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, error handling 1 (2 pts), loops 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
ImmutableModulesMemoryStore::write_cache (cognitive 17) crates/core/src/cache/module_cache/immutable_modules.rs:150— ImmutableModulesMemoryStore::write_cache has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (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.
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.
farmfe_utils::relative (cognitive 17) crates/utils/src/lib.rs:102— farmfe_utils::relative has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 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.
FarmfePluginIcons::load (cognitive 17) rust-plugins/icons/src/lib.rs:124— 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.
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.
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.
DesignSystem::register_theme_block (cognitive 16) rust-ecosystem/tailwindcss/src/design_system.rs:146— 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:108— 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.
Root.generate (cognitive 16) js-plugins/tailwindcss/src/index.ts:256— 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.
bump-create-farm-version.updatePackageJsonDependencies (cognitive 16) scripts/bump-create-farm-version.mjs:18— bump-create-farm-version.updatePackageJsonDependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 16 points belong to 5 function literals inside it that branch (lines 46, 26, 34, …). 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.
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 (16 corresponding lines) · ×1
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.
Duplicated block (24–25 lines × 2) crates/toolkit/src/script/module2cjs.rs:942— crates/toolkit/src/script/module2cjs.rs:942-966 | crates/toolkit/src/script/module2cjs.rs:992-1015 — 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–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.
Duplicated block (16–21 lines × 2) crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:673— crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:673-693 | crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs:705-720 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19–20 lines × 2) crates/plugin_tree_shake/src/tree_shake_modules.rs:468— crates/plugin_tree_shake/src/tree_shake_modules.rs:468-487 | crates/plugin_tree_shake/src/tree_shake_modules.rs:557-575 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:479— rust-plugins/vue-jsx/src/resolve_type.rs:479-497 | rust-plugins/vue-jsx/src/resolve_type.rs:511-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 2) crates/plugin_partial_bundling/src/merge_module_pots.rs:280— crates/plugin_partial_bundling/src/merge_module_pots.rs:280-297 | crates/plugin_partial_bundling/src/merge_module_pots.rs:302-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.
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.
Duplicated block (13–15 lines × 2) crates/plugin_runtime/src/render_resource_pot/external.rs:83— crates/plugin_runtime/src/render_resource_pot/external.rs:83-97 | crates/plugin_runtime/src/render_resource_pot/external.rs:129-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (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.
Duplicated block (12 lines × 3) rust-plugins/auto-import/src/parser/parse.rs:402— rust-plugins/auto-import/src/parser/parse.rs:402-413 | rust-plugins/auto-import/src/parser/parse.rs:437-448 | rust-plugins/auto-import/src/parser/parse.rs:472-483 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (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.
Duplicated block (11 lines × 3) rust-plugins/auto-import/src/parser/parse.rs:411— rust-plugins/auto-import/src/parser/parse.rs:411-421 | rust-plugins/auto-import/src/parser/parse.rs:481-491 | rust-plugins/react-components/src/find_local_components.rs:321-331 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7–10 lines × 2) crates/core/src/module/watch_graph.rs:128— crates/core/src/module/watch_graph.rs:128-134 | crates/core/src/module/watch_graph.rs:149-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) crates/plugin_css/src/lib.rs:669— crates/plugin_css/src/lib.rs:669-678 | crates/plugin_script/src/lib.rs:580-587 — 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–10 lines × 2) rust-plugins/vue-jsx/src/resolve_type.rs:1008— rust-plugins/vue-jsx/src/resolve_type.rs:1008-1017 | rust-plugins/vue-jsx/src/resolve_type.rs:1048-1056 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–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.
Duplicated block (6 lines × 3) rust-plugins/dsv/src/lib.rs:69— rust-plugins/dsv/src/lib.rs:69-74 | 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 all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) rust-plugins/icons/src/lib.rs:138— rust-plugins/icons/src/lib.rs:138-142 | rust-plugins/icons/src/lib.rs:212-216 | 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.
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.
CI formatting step cannot fail REDACTED:14— `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.
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 6 sibling directories (5 clone groups) js-plugins/less/src/index.ts:39— 5 duplicated blocks under js-plugins/ have copies in at least two of the sibling directories babel, dts, less, postcss, react-compiler, sass — 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.
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 (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 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 — 163 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.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) packages/core/src/server/index.ts:727— packages/core/src/server/index.ts:727 · packages/core/src/server/preview.ts:273 — the two spans are one implementation copied and then locally edited — 197 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (33 lines × 2 locations) scripts/build.mjs:282— scripts/build.mjs:282 · scripts/build.mjs:332 — 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 (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 (16 lines × 2 locations) packages/core/src/plugin/js/index.ts:182— packages/core/src/plugin/js/index.ts:182 · packages/core/src/plugin/js/index.ts:201 — 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.
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 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 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 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 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 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 applyHotUpdates (cyclomatic 19, cognitive 43) REDACTED:93— applyHotUpdates has cyclomatic complexity 19 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 farmRequire (cyclomatic 19, cognitive 35) packages/runtime/src/module-system.ts:149— farmRequire has cyclomatic complexity 19 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 config (cyclomatic 19, cognitive 17) crates/create-farm-rs/templates/nestjs/index.plugin.ts:6— config has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 interopRequireWildcard (cyclomatic 18, cognitive 22) packages/runtime/src/modules/module-helper.ts:107— interopRequireWildcard has cyclomatic complexity 18 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 convertPluginVite (cyclomatic 18, cognitive 21) packages/core/src/plugin/js/index.ts:160— convertPluginVite has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function #resolveOptions (cyclomatic 18, cognitive 15) packages/core/src/server/preview.ts:159— #resolveOptions has cyclomatic complexity 18 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 getResolvedOptions (cyclomatic 17, cognitive 25) js-plugins/dts/src/utils.ts:116— getResolvedOptions has cyclomatic complexity 17 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function mergeFarmCliConfig (cyclomatic 16, cognitive 17) packages/core/src/config/merge-config.ts:48— mergeFarmCliConfig has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function farmUserConfigToViteConfig (cyclomatic 16, cognitive 15) packages/core/src/plugin/js/farm-to-vite-config.ts:14— farmUserConfigToViteConfig has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function htmlFallbackMiddleware (cyclomatic 16, cognitive 15) packages/core/src/server/middlewares/htmlFallback.ts:9— htmlFallbackMiddleware has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleResolveOptions (cyclomatic 16, cognitive 14) js-plugins/dts/src/context.ts:40— handleResolveOptions has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkCompilationInputValue (cyclomatic 15, cognitive 32) packages/core/src/config/normalize-config/index.ts:180— checkCompilationInputValue has cyclomatic complexity 15 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 parseArgs (cyclomatic 15, cognitive 23) scripts/test-e2e.mjs:37— parseArgs has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
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/server/index.ts · ×1
packages/core/src/server/index.ts: 692 lines of code packages/core/src/server/index.ts:1— packages/core/src/server/index.ts has 692 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.
R3 · Large Files· packages/core/src/types/binding.ts · ×1
packages/core/src/types/binding.ts: 503 lines of code packages/core/src/types/binding.ts:1— packages/core/src/types/binding.ts has 503 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: 458 lines of code packages/core/src/config/schema.ts:1— packages/core/src/config/schema.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: 436 lines of code packages/core/src/config/types.ts:1— packages/core/src/config/types.ts has 436 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.
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 57 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, js-plugins/visualizer/src/client/src/pages/analysis/Bundle.vue, js-plugins/visualizer/src/client/src/components/NavBar.vue, js-plugins/visualizer/src/client/src/components/AnalyzeDepsRecord.vue, js-plugins/visualizer/src/client/src/components/ResourcePots.vue and 51 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 (~258 LoC) packages/core/binding/resolve-binding.cjs— no import path from any entry point (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (191 application, 163 tooling, 230 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 (~48 LoC) js-plugins/visualizer/src/client/src/components/ProcessRecord.vue— no import path from any entry point (191 application, 163 tooling, 230 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 (~32 LoC) scripts/github-matrix.mjs— no import path from any entry point (191 application, 163 tooling, 230 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 (~26 LoC) js-plugins/visualizer/src/client/src/pages/analysis/Module.vue— no import path from any entry point (191 application, 163 tooling, 230 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 (~20 LoC) scripts/clear-cache.mjs— no import path from any entry point (191 application, 163 tooling, 230 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
Benchmark script nothing runs (~223 LoC) website/src/components/Benchmark/index.tsx— This script imports the product ('../Card'), so it is an authored benchmark, not measurement input — but nothing invokes it: no REDACTED script, no CI workflow or build recipe, no Dockerfile, no other file under website/src/components/Benchmark/, and no in-repo reference to its name at all. It runs only if someone remembers to type `node website/src/components/Benchmark/index.tsx`, and it silently rots against the API it measures. Wire it into a script or workflow the way its wired siblings are, or delete it.
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.
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 'react' rust-plugins/icons/types/react.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.
Unlisted import 'vue' rust-plugins/icons/types/vue3.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.
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 '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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap packages/core/src/plugin/js/utils.ts:217— `deleteUndefinedPropertyDeeply` is exported and takes `obj: any` from its caller, and it calls itself at line 217 (`deleteUndefinedPropertyDeeply`) with a piece of `obj` — and nowhere in `deleteUndefinedPropertyDeeply` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deleteUndefinedPropertyDeeply` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X19 · Unrestored process-global state· Process-global state is restored only on the happy path · ×1
Process-global state is restored only on the happy path packages/core/src/config/load-config-file.ts:156— `readConfigFile` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `FARM_PROFILE` environment variable (set at line 222, put back at line 229) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between — or by a promise that rejects at an `await`, and while this function is suspended at one every other callback the event loop runs sees the moved value too: the process then keeps the overwritten value for the rest of its life, and every later relative path, child-process launch or config read in ANY module resolves against it. That failure is silent and remote from its cause — the function that breaks is not the function that moved the directory. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — the `cwd` and `env` options of `child_process.spawn`/`exec`/`execSync` (or `Deno.Command`) scope both to the CHILD — or build absolute paths with `path.resolve`. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
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 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:12— `!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 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 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/core/src/server/index.ts:581— `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 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 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.
Duplicated predicate REDACTED:51— `target.closest('.options') || target.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 REDACTED:109— `trimmed.startsWith('<!doctype') || trimmed.startsWith('<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 crates/plugin_resolve/src/resolver.rs:457— `!alias.ends_with('$') && source.starts_with(alias)` appears character-identically in 2 files — crates/plugin_resolve/src/resolver.rs, crates/swc_transformer_import_glob/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_tree_shake/src/init_tree_shake_module_map.rs:20— `!module.module_type.is_script() || module.external` appears character-identically in 2 files — crates/plugin_tree_shake/src/init_tree_shake_module_map.rs, crates/plugin_tree_shake/src/remove_hot_update.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_resolve/src/resolver.rs:455— `alias.ends_with('$') && source == alias.trim_end_matches('$')` appears character-identically in 2 files — crates/plugin_resolve/src/resolver.rs, crates/swc_transformer_import_glob/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_mangle_exports/src/utils.rs:75— `dep_module.external || !dep_module.module_type.is_script()` appears character-identically in 3 files — crates/plugin_mangle_exports/src/utils.rs, crates/toolkit/src/script/concatenate_modules/dynamic_import.rs, crates/toolkit/src/script/transform_to_esm/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_runtime/src/handle_runtime_modules.rs:308— `matches!(context.config.mode, Mode::Development) && context.config.output.target_env != TargetEnv::Library` appears character-identically in 2 files — crates/plugin_runtime/src/handle_runtime_modules.rs, crates/toolkit/src/runtime.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_mangle_exports/src/utils.rs:54— `module.external || !module.module_type.is_script()` appears character-identically in 2 files — crates/plugin_mangle_exports/src/utils.rs, crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/plugin_mangle_exports/src/mangle_exports.rs:173— `source_module.external || !source_module.module_type.is_script()` appears character-identically in 3 files — crates/plugin_mangle_exports/src/mangle_exports.rs, crates/toolkit/src/script/concatenate_modules/handle_external_modules.rs, crates/toolkit/src/script/concatenate_modules/strip_module_decl.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
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 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/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 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 crates/core/src/cache/store/disk.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 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 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 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 crates/create-farm-rs/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/plugin_script/src/transform_import_meta_url/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 js-plugins/electron/src/index.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 crates/macro_testing/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/core/src/cache/store/namespace.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/logger.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core/src/utils/file.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 crates/core/src/cache/store/memory.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/module_cache/module_metadata.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/node/src/plugin_adapters/js_plugin_adapter/context_methods/cache.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/src/is_react_refresh_boundary.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 crates/create-farm-rs/src/package_manager.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/config/external.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.
P2 · Observability· Console output used as the logging channel · ×20
Console output used as the logging channel js-plugins/dts/src/logger.ts:75— `js-plugins/dts/src/logger.ts` reports through `console.*` at line 75 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/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/logger.ts:144— `packages/core/src/utils/logger.ts` reports through `console.*` at line 144 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/logger.ts:275— `packages/core/src/utils/logger.ts` reports through `console.*` at line 275 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/logger.ts:280— `packages/core/src/utils/logger.ts` reports through `console.*` at line 280 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:248— `packages/core/src/server/preview.ts` reports through `console.*` at line 248 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.
Console output used as the logging channel packages/runtime-plugin-hmr/src/logger.ts:3— `packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 3 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/runtime-plugin-hmr/src/logger.ts:6— `packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 6 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/runtime-plugin-hmr/src/logger.ts:9— `packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 9 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/runtime-plugin-hmr/src/logger.ts:12— `packages/runtime-plugin-hmr/src/logger.ts` reports through `console.*` at line 12 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/runtime-plugin-hmr/src/overlay.ts:676— `packages/runtime-plugin-hmr/src/overlay.ts` reports through `console.*` at line 676 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 4, but the manifest declares `tailwindcss` ^3.3.2. 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.
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.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 81 project(s) overshoot their size bounds, lowering Project Cohesion to 9.5/10. The most over is `packages/core` (12927 LoC, 180 module-visible types across 14 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· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 22 of 343 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 343 of the 615 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/core/src/types/binding.ts, crates/create-farm-rs/src/template.rs, crates/create-farm-rs/src/utils/lte.rs, js-plugins/dts/src/utils.ts, crates/core/src/cache/store/disk.rs, crates/core/src/cache/scope.rs, crates/create-farm-rs/src/utils/colors.rs, crates/create-farm-rs/src/utils/theme.rs (and 14 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 5/23 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 13 more.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Unused export 'tryRead' js-plugins/dts/src/utils.ts:272— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'cleanScssBugUrl' · ×1
Unused export 'cleanScssBugUrl' js-plugins/sass/src/options.ts:23— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'createModuleGraph' · ×1
Unused export 'createModuleGraph' packages/core/src/plugin/js/vite-server-adapter.ts:94— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'ERR_SYMLINK_IN_RECURSIVE_READDIR' · ×1
Unused export 'ERR_SYMLINK_IN_RECURSIVE_READDIR' REDACTED:4— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'initPublicFiles' · ×1
Unused export 'initPublicFiles' REDACTED:9— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getPublicFiles' · ×1
Unused export 'getPublicFiles' REDACTED:30— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'HMRBroadcasterClient' · ×1
Unused export 'HMRBroadcasterClient' packages/core/src/server/type.ts:90— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'loopbackHosts' · ×1
Unused export 'loopbackHosts' packages/core/src/utils/http.ts:28— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'handleErrorSync' · ×1
Unused export 'handleErrorSync' packages/runtime-plugin-hmr/src/utils.ts:1— Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene· Type-only dependency 'connect' in production deps · ×1
Type-only dependency 'connect' in production deps js-plugins/visualizer/src/dev.ts:2— Every import is type-only — move it to devDependencies.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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 — 136/167 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~1.6 `!` null assertions per 1k TypeScript source lines — 41 assertion(s) across the 26436 source line(s) of the 233 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 (9), packages/core/src/server/preview.ts (8), packages/core/src/server/ws.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
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.
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.10 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.1"` requirement declared in rust-plugins/vue-jsx/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.15.0 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.6.13 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.13.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: thiserror — `thiserror` is locked at 2.0.18 but 2.0.21 is the current stable release on crates.io, and it already satisfies the `"2.0.12"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thiserror` and commit the updated REDACTED.
+ 3 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 12 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`, … (+7 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 01a1801d-e888-780c-b90f-2526b368baf6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 339 · Warnings: 948 · Recommendations: 122 · Info: 28 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 28-10-2026 @ 01:26 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.