Public report of vitejs/vite, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 09:40 UTC · Survey ID cd_a1161928c754489dbaf2acab6f1a194e
vitejs/vite
Measured 14 November 2026, 09:39 UTC, at code version f898888
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 64,280 lines of product code in 229 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Architecture, 35
Findings by how serious they are
69 critical794 serious475 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 09:39 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
76of 76 dimensions measured by tools.
1315of 1338 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 64,280 lines of product code in 229 projects.
vitejs/vite falls short of our standard for production, in part because it has pieces of product code that depend on test code. It scores 45 out of 100 and is rated Weak, and 18 of its 69 critical findings are security problems.
Architecture, at 35, is the weakest lens and counts most in the score. The best first steps are removing the test references and respecting the front end's boundaries, each worth about 6 points. Raising Architecture to 70 would lift the score to about 53.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and twenty-three images have no description for people who can't see them. Pinning each tool to an exact version, updating the vulnerable packages and describing the images would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the place where the code runs text as code or as a command needs a direct call instead. The nine pages that don't say their language need their language set.
The product code is 64,280 lines, about €89,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 Architecture rose from 35 to 70, the lowest score rated Strong, the score would rise from 45 to about 53.
Code composition: what the lines of code are
Product code 64%Tests 36%
New since the last survey: 176 findings
These 176 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 261 findings
These 261 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.
€29,000 to €150,000, for 491 to 1,559 hours of work, about 0.6 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 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 64,280 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Raises the score by about 6 points · Medium effort · Test isolation
2
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 (126 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (13 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (7 rows).
Raises the score by about 6 points · Medium effort · Import Boundaries
3
Break each cycle by extracting the shared piece into a module both sides can import.
Raises the score by about 5 points · Medium effort · Circular Imports
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €89,000 to build again, about 0.6 person-years of work. Its weakest lens is Architecture, at 35 (Weak). Architecture is about whether the structure holds up as the product grows, and when the structure is weak, a change in one place ripples into many others. Because the weakest lens counts most in the score, work on Architecture also moves the score most.
Based on: the rebuild estimate · the Architecture grade · how much each lens counts
What to do: Start with the Architecture actions in Top priorities.
If you do one thing first · First action
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 62,551 lines over the last 90 days, which is about 253,679 lines a year. At that pace, the extra work comes to an estimated 39.2 to 235 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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.
248 modules, with 191 dependencies between them. One loop runs through 14 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 208 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
packages.vite.src.module-runner.types uses packages.vite.src.module-runner.evaluatedModules, so a change to packages.vite.src.module-runner.evaluatedModules can break packages.vite.src.module-runner.types, while a change to packages.vite.src.module-runner.types can't break packages.vite.src.module-runner.evaluatedModules.
Position
Below the diagonal: packages.vite.src.module-runner.types uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.types uses packages.vite.src.shared.moduleRunnerTransport, so a change to packages.vite.src.shared.moduleRunnerTransport can break packages.vite.src.module-runner.types, while a change to packages.vite.src.module-runner.types can't break packages.vite.src.shared.moduleRunnerTransport.
Position
Below the diagonal: packages.vite.src.module-runner.types uses a module listed above it, which is the healthy direction.
10→26 packages.vite.src.node.plugins.html uses packages.vite.src.node.serverpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.plugins.html uses a type in packages.vite.src.node.server.
packages.vite.src.node.plugins.html uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.plugins.html, while a change to packages.vite.src.node.plugins.html can't break packages.vite.src.node.server.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.server.mixedModuleGraph uses packages.vite.src.node.server.moduleGraph, so a change to packages.vite.src.node.server.moduleGraph can break packages.vite.src.node.server.mixedModuleGraph, while a change to packages.vite.src.node.server.mixedModuleGraph can't break packages.vite.src.node.server.moduleGraph.
Position
Below the diagonal: packages.vite.src.node.server.mixedModuleGraph uses a module listed above it, which is the healthy direction.
packages.vite.src.shared uses packages.vite.src.shared.moduleRunnerTransport, so a change to packages.vite.src.shared.moduleRunnerTransport can break packages.vite.src.shared, while a change to packages.vite.src.shared can't break packages.vite.src.shared.moduleRunnerTransport.
Position
Below the diagonal: packages.vite.src.shared uses a module listed above it, which is the healthy direction.
packages.vite.src.shared.bundledDevHmr uses packages.vite.src.shared.moduleRunnerTransport, so a change to packages.vite.src.shared.moduleRunnerTransport can break packages.vite.src.shared.bundledDevHmr, while a change to packages.vite.src.shared.bundledDevHmr can't break packages.vite.src.shared.moduleRunnerTransport.
Position
Below the diagonal: packages.vite.src.shared.bundledDevHmr uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.runner uses packages.vite.src.module-runner.evaluatedModules, so a change to packages.vite.src.module-runner.evaluatedModules can break packages.vite.src.module-runner.runner, while a change to packages.vite.src.module-runner.runner can't break packages.vite.src.module-runner.evaluatedModules.
Position
Below the diagonal: packages.vite.src.module-runner.runner uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.runner uses packages.vite.src.shared.moduleRunnerTransport, so a change to packages.vite.src.shared.moduleRunnerTransport can break packages.vite.src.module-runner.runner, while a change to packages.vite.src.module-runner.runner can't break packages.vite.src.shared.moduleRunnerTransport.
Position
Below the diagonal: packages.vite.src.module-runner.runner uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.runner uses packages.vite.src.module-runner.types, so a change to packages.vite.src.module-runner.types can break packages.vite.src.module-runner.runner, while a change to packages.vite.src.module-runner.runner can't break packages.vite.src.module-runner.types.
Position
Below the diagonal: packages.vite.src.module-runner.runner uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.runner uses packages.vite.src.shared.bundledDevHmr, so a change to packages.vite.src.shared.bundledDevHmr can break packages.vite.src.module-runner.runner, while a change to packages.vite.src.module-runner.runner can't break packages.vite.src.shared.bundledDevHmr.
Position
Below the diagonal: packages.vite.src.module-runner.runner uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugin uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.plugin, while a change to packages.vite.src.node.plugin can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.plugin uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugin uses packages.vite.src.node.plugins.html, so a change to packages.vite.src.node.plugins.html can break packages.vite.src.node.plugin, while a change to packages.vite.src.node.plugin can't break packages.vite.src.node.plugins.html.
Position
Below the diagonal: packages.vite.src.node.plugin uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.hmr uses packages.vite.src.node.server.moduleGraph, so a change to packages.vite.src.node.server.moduleGraph can break packages.vite.src.node.server.hmr, while a change to packages.vite.src.node.server.hmr can't break packages.vite.src.node.server.moduleGraph.
Position
Below the diagonal: packages.vite.src.node.server.hmr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.hmr uses packages.vite.src.node.server.mixedModuleGraph, so a change to packages.vite.src.node.server.mixedModuleGraph can break packages.vite.src.node.server.hmr, while a change to packages.vite.src.node.server.hmr can't break packages.vite.src.node.server.mixedModuleGraph.
Position
Below the diagonal: packages.vite.src.node.server.hmr uses a module listed above it, which is the healthy direction.
16→26 packages.vite.src.node.server.hmr uses packages.vite.src.node.serverpart of a loop✕
Connections
4 pairs of types, where a type in packages.vite.src.node.server.hmr uses a type in packages.vite.src.node.server.
packages.vite.src.node.server.hmr uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.server.hmr, while a change to packages.vite.src.node.server.hmr can't break packages.vite.src.node.server.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.ssr.runtime.serverModuleRunner uses packages.vite.src.module-runner.types, so a change to packages.vite.src.module-runner.types can break packages.vite.src.node.ssr.runtime.serverModuleRunner, while a change to packages.vite.src.node.ssr.runtime.serverModuleRunner can't break packages.vite.src.module-runner.types.
Position
Below the diagonal: packages.vite.src.node.ssr.runtime.serverModuleRunner uses a module listed above it, which is the healthy direction.
packages.vite uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite, while a change to packages.vite can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite uses a module listed above it, which is the healthy direction.
packages.vite.src.module-runner.sourcemap uses packages.vite.src.module-runner.runner, so a change to packages.vite.src.module-runner.runner can break packages.vite.src.module-runner.sourcemap, while a change to packages.vite.src.module-runner.sourcemap can't break packages.vite.src.module-runner.runner.
Position
Below the diagonal: packages.vite.src.module-runner.sourcemap uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.bundledDev uses packages.vite.src.node.server.hmr, so a change to packages.vite.src.node.server.hmr can break packages.vite.src.node.server.bundledDev, while a change to packages.vite.src.node.server.bundledDev can't break packages.vite.src.node.server.hmr.
Position
Below the diagonal: packages.vite.src.node.server.bundledDev uses a module listed above it, which is the healthy direction.
20→25 packages.vite.src.node.server.bundledDev uses packages.vite.src.node.server.environmentpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.server.bundledDev uses a type in packages.vite.src.node.server.environment.
packages.vite.src.node.server.bundledDev uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.server.bundledDev, while a change to packages.vite.src.node.server.bundledDev can't break packages.vite.src.node.server.environment.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.server.pluginContainer uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.server.pluginContainer, while a change to packages.vite.src.node.server.pluginContainer can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.server.pluginContainer uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.pluginContainer uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.server.pluginContainer, while a change to packages.vite.src.node.server.pluginContainer can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.server.pluginContainer uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.pluginContainer uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite.src.node.server.pluginContainer, while a change to packages.vite.src.node.server.pluginContainer can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite.src.node.server.pluginContainer uses a module listed above it, which is the healthy direction.
packages.vite.src.node.optimizer.scan uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node.optimizer.scan, while a change to packages.vite.src.node.optimizer.scan can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node.optimizer.scan uses a module listed above it, which is the healthy direction.
22→31 packages.vite.src.node.optimizer.scan uses packages.vite.src.node.baseEnvironmentpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.optimizer.scan uses a type in packages.vite.src.node.baseEnvironment.
packages.vite.src.node.optimizer.scan uses packages.vite.src.node.baseEnvironment, so a change to packages.vite.src.node.baseEnvironment can break packages.vite.src.node.optimizer.scan, while a change to packages.vite.src.node.optimizer.scan can't break packages.vite.src.node.baseEnvironment.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.plugins.worker uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.plugins.worker, while a change to packages.vite.src.node.plugins.worker can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.plugins.worker uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins.worker uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.plugins.worker, while a change to packages.vite.src.node.plugins.worker can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.plugins.worker uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins.worker uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node.plugins.worker, while a change to packages.vite.src.node.plugins.worker can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node.plugins.worker uses a module listed above it, which is the healthy direction.
packages.vite.src.node.optimizer uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.optimizer, while a change to packages.vite.src.node.optimizer can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.optimizer uses a module listed above it, which is the healthy direction.
packages.vite.src.node.optimizer uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite.src.node.optimizer, while a change to packages.vite.src.node.optimizer can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite.src.node.optimizer uses a module listed above it, which is the healthy direction.
packages.vite.src.node.optimizer uses packages.vite.src.node.optimizer.scan, so a change to packages.vite.src.node.optimizer.scan can break packages.vite.src.node.optimizer, while a change to packages.vite.src.node.optimizer can't break packages.vite.src.node.optimizer.scan.
Position
Below the diagonal: packages.vite.src.node.optimizer uses a module listed above it, which is the healthy direction.
24→25 packages.vite.src.node.optimizer uses packages.vite.src.node.server.environmentpart of a loop✕
Connections
2 pairs of types, where a type in packages.vite.src.node.optimizer uses a type in packages.vite.src.node.server.environment.
packages.vite.src.node.optimizer uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.optimizer, while a change to packages.vite.src.node.optimizer can't break packages.vite.src.node.server.environment.
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.
24→30 packages.vite.src.node.optimizer uses packages.vite.src.node.configpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.optimizer uses a type in packages.vite.src.node.config.
packages.vite.src.node.optimizer uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.optimizer, while a change to packages.vite.src.node.optimizer can't break packages.vite.src.node.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.server.environment uses packages.vite.src.node.server.moduleGraph, so a change to packages.vite.src.node.server.moduleGraph can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.server.moduleGraph.
Position
Below the diagonal: packages.vite.src.node.server.environment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environment uses packages.vite.src.node.server.hmr, so a change to packages.vite.src.node.server.hmr can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.server.hmr.
Position
Below the diagonal: packages.vite.src.node.server.environment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environment uses packages.vite.src.node.server.bundledDev, so a change to packages.vite.src.node.server.bundledDev can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.server.bundledDev.
Position
Below the diagonal: packages.vite.src.node.server.environment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environment uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node.server.environment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environment uses packages.vite.src.node.optimizer, so a change to packages.vite.src.node.optimizer can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.optimizer.
Position
Below the diagonal: packages.vite.src.node.server.environment uses a module listed above it, which is the healthy direction.
25→26 packages.vite.src.node.server.environment uses packages.vite.src.node.serverpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.server.environment uses a type in packages.vite.src.node.server.
packages.vite.src.node.server.environment uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.server.
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→30 packages.vite.src.node.server.environment uses packages.vite.src.node.configpart of a loop✕
Connections
2 pairs of types, where a type in packages.vite.src.node.server.environment uses a type in packages.vite.src.node.config.
packages.vite.src.node.server.environment uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.config.
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→31 packages.vite.src.node.server.environment uses packages.vite.src.node.baseEnvironmentpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.server.environment uses a type in packages.vite.src.node.baseEnvironment.
packages.vite.src.node.server.environment uses packages.vite.src.node.baseEnvironment, so a change to packages.vite.src.node.baseEnvironment can break packages.vite.src.node.server.environment, while a change to packages.vite.src.node.server.environment can't break packages.vite.src.node.baseEnvironment.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.server uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.moduleGraph, so a change to packages.vite.src.node.server.moduleGraph can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.moduleGraph.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.transformRequest, so a change to packages.vite.src.node.server.transformRequest can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.transformRequest.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.plugins.html, so a change to packages.vite.src.node.plugins.html can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.plugins.html.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.mixedModuleGraph, so a change to packages.vite.src.node.server.mixedModuleGraph can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.mixedModuleGraph.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.module-runner.runner, so a change to packages.vite.src.module-runner.runner can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.module-runner.runner.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.hmr, so a change to packages.vite.src.node.server.hmr can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.hmr.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.server uses a module listed above it, which is the healthy direction.
26→30 packages.vite.src.node.server uses packages.vite.src.node.configpart of a loop✕
Connections
2 pairs of types, where a type in packages.vite.src.node.server uses a type in packages.vite.src.node.config.
packages.vite.src.node.server uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server, while a change to packages.vite.src.node.server can't break packages.vite.src.node.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.ssr.runtime uses packages.vite.src.shared.moduleRunnerTransport, so a change to packages.vite.src.shared.moduleRunnerTransport can break packages.vite.src.node.ssr.runtime, while a change to packages.vite.src.node.ssr.runtime can't break packages.vite.src.shared.moduleRunnerTransport.
Position
Below the diagonal: packages.vite.src.node.ssr.runtime uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr.runtime uses packages.vite.src.module-runner.runner, so a change to packages.vite.src.module-runner.runner can break packages.vite.src.node.ssr.runtime, while a change to packages.vite.src.node.ssr.runtime can't break packages.vite.src.module-runner.runner.
Position
Below the diagonal: packages.vite.src.node.ssr.runtime uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr.runtime uses packages.vite.src.node.ssr.runtime.serverModuleRunner, so a change to packages.vite.src.node.ssr.runtime.serverModuleRunner can break packages.vite.src.node.ssr.runtime, while a change to packages.vite.src.node.ssr.runtime can't break packages.vite.src.node.ssr.runtime.serverModuleRunner.
Position
Below the diagonal: packages.vite.src.node.ssr.runtime uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr.runtime uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.ssr.runtime, while a change to packages.vite.src.node.ssr.runtime can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.ssr.runtime uses a module listed above it, which is the healthy direction.
packages.vite.src.node.preview uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.preview, while a change to packages.vite.src.node.preview can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node.preview uses a module listed above it, which is the healthy direction.
28→30 packages.vite.src.node.preview uses packages.vite.src.node.configpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.preview uses a type in packages.vite.src.node.config.
packages.vite.src.node.preview uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.preview, while a change to packages.vite.src.node.preview can't break packages.vite.src.node.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.ssr uses packages.vite.src.node.server.moduleGraph, so a change to packages.vite.src.node.server.moduleGraph can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.server.moduleGraph.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.node.server.transformRequest, so a change to packages.vite.src.node.server.transformRequest can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.server.transformRequest.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.module-runner.runner, so a change to packages.vite.src.module-runner.runner can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.module-runner.runner.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.node.server.bundledDev, so a change to packages.vite.src.node.server.bundledDev can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.server.bundledDev.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
packages.vite.src.node.ssr uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node.ssr uses a module listed above it, which is the healthy direction.
29→30 packages.vite.src.node.ssr uses packages.vite.src.node.configpart of a loop✕
Connections
1 pair of types, where a type in packages.vite.src.node.ssr uses a type in packages.vite.src.node.config.
packages.vite.src.node.ssr uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.ssr, while a change to packages.vite.src.node.ssr can't break packages.vite.src.node.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.config uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.config uses a module listed above it, which is the healthy direction.
packages.vite.src.node.config uses packages.vite.src.node.plugins.resolve, so a change to packages.vite.src.node.plugins.resolve can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.plugins.resolve.
Position
Below the diagonal: packages.vite.src.node.config uses a module listed above it, which is the healthy direction.
packages.vite.src.node.config uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node.config uses a module listed above it, which is the healthy direction.
packages.vite.src.node.config uses packages.vite.src.node.preview, so a change to packages.vite.src.node.preview can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.preview.
Position
Below the diagonal: packages.vite.src.node.config uses a module listed above it, which is the healthy direction.
packages.vite.src.node.config uses packages.vite.src.node.ssr, so a change to packages.vite.src.node.ssr can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.ssr.
Position
Below the diagonal: packages.vite.src.node.config uses a module listed above it, which is the healthy direction.
30→36 packages.vite.src.node.config uses packages.vite.src.node.buildpart of a loop✕
Connections
2 pairs of types, where a type in packages.vite.src.node.config uses a type in packages.vite.src.node.build.
packages.vite.src.node.config uses packages.vite.src.node.build, so a change to packages.vite.src.node.build can break packages.vite.src.node.config, while a change to packages.vite.src.node.config can't break packages.vite.src.node.build.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vite.src.node.baseEnvironment uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.baseEnvironment, while a change to packages.vite.src.node.baseEnvironment can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.baseEnvironment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.baseEnvironment uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.baseEnvironment, while a change to packages.vite.src.node.baseEnvironment can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.baseEnvironment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.vite.src.node.server.environments.fetchableEnvironments uses a type in packages.vite.src.node.server.environment.
packages.vite.src.node.server.environments.fetchableEnvironments uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.server.environments.fetchableEnvironments, while a change to packages.vite.src.node.server.environments.fetchableEnvironments can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.server.environments.fetchableEnvironments uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environments.fetchableEnvironments uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server.environments.fetchableEnvironments, while a change to packages.vite.src.node.server.environments.fetchableEnvironments can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.server.environments.fetchableEnvironments uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environments.runnableEnvironment uses packages.vite.src.module-runner.runner, so a change to packages.vite.src.module-runner.runner can break packages.vite.src.node.server.environments.runnableEnvironment, while a change to packages.vite.src.node.server.environments.runnableEnvironment can't break packages.vite.src.module-runner.runner.
Position
Below the diagonal: packages.vite.src.node.server.environments.runnableEnvironment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.vite.src.node.server.environments.runnableEnvironment uses a type in packages.vite.src.node.ssr.runtime.serverModuleRunner.
packages.vite.src.node.server.environments.runnableEnvironment uses packages.vite.src.node.ssr.runtime.serverModuleRunner, so a change to packages.vite.src.node.ssr.runtime.serverModuleRunner can break packages.vite.src.node.server.environments.runnableEnvironment, while a change to packages.vite.src.node.server.environments.runnableEnvironment can't break packages.vite.src.node.ssr.runtime.serverModuleRunner.
Position
Below the diagonal: packages.vite.src.node.server.environments.runnableEnvironment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.vite.src.node.server.environments.runnableEnvironment uses a type in packages.vite.src.node.server.environment.
packages.vite.src.node.server.environments.runnableEnvironment uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.server.environments.runnableEnvironment, while a change to packages.vite.src.node.server.environments.runnableEnvironment can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.server.environments.runnableEnvironment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environments.runnableEnvironment uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server.environments.runnableEnvironment, while a change to packages.vite.src.node.server.environments.runnableEnvironment can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.server.environments.runnableEnvironment uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.middlewares uses packages.plugin-legacy.src.types, so a change to packages.plugin-legacy.src.types can break packages.vite.src.node.server.middlewares, while a change to packages.vite.src.node.server.middlewares can't break packages.plugin-legacy.src.types.
Position
Below the diagonal: packages.vite.src.node.server.middlewares uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.middlewares uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.server.middlewares, while a change to packages.vite.src.node.server.middlewares can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.server.middlewares uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.middlewares uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.server.middlewares, while a change to packages.vite.src.node.server.middlewares can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node.server.middlewares uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.middlewares uses packages.vite.src.node.preview, so a change to packages.vite.src.node.preview can break packages.vite.src.node.server.middlewares, while a change to packages.vite.src.node.server.middlewares can't break packages.vite.src.node.preview.
Position
Below the diagonal: packages.vite.src.node.server.middlewares uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.middlewares uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server.middlewares, while a change to packages.vite.src.node.server.middlewares can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.server.middlewares uses a module listed above it, which is the healthy direction.
playground uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break playground, while a change to playground can't break packages.vite.src.node.logger.
Position
Below the diagonal: playground uses a module listed above it, which is the healthy direction.
playground uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break playground, while a change to playground can't break packages.vite.src.node.plugin.
Position
Below the diagonal: playground uses a module listed above it, which is the healthy direction.
playground uses packages.vite.src.node.optimizer, so a change to packages.vite.src.node.optimizer can break playground, while a change to playground can't break packages.vite.src.node.optimizer.
Position
Below the diagonal: playground uses a module listed above it, which is the healthy direction.
playground uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break playground, while a change to playground can't break packages.vite.src.node.config.
Position
Below the diagonal: playground uses a module listed above it, which is the healthy direction.
packages.vite.src.node.build uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.build, while a change to packages.vite.src.node.build can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.build uses a module listed above it, which is the healthy direction.
packages.vite.src.node.build uses packages.vite.src.node.baseEnvironment, so a change to packages.vite.src.node.baseEnvironment can break packages.vite.src.node.build, while a change to packages.vite.src.node.build can't break packages.vite.src.node.baseEnvironment.
Position
Below the diagonal: packages.vite.src.node.build uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environments uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.server.environments, while a change to packages.vite.src.node.server.environments can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.server.environments uses a module listed above it, which is the healthy direction.
packages.vite.src.node.server.environments uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.server.environments, while a change to packages.vite.src.node.server.environments can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.server.environments uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.vite.src.node.server.environments uses a type in packages.vite.src.node.server.environments.fetchableEnvironments.
packages.vite.src.node.server.environments uses packages.vite.src.node.server.environments.fetchableEnvironments, so a change to packages.vite.src.node.server.environments.fetchableEnvironments can break packages.vite.src.node.server.environments, while a change to packages.vite.src.node.server.environments can't break packages.vite.src.node.server.environments.fetchableEnvironments.
Position
Below the diagonal: packages.vite.src.node.server.environments uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.vite.src.node.server.environments uses a type in packages.vite.src.node.server.environments.runnableEnvironment.
packages.vite.src.node.server.environments uses packages.vite.src.node.server.environments.runnableEnvironment, so a change to packages.vite.src.node.server.environments.runnableEnvironment can break packages.vite.src.node.server.environments, while a change to packages.vite.src.node.server.environments can't break packages.vite.src.node.server.environments.runnableEnvironment.
Position
Below the diagonal: packages.vite.src.node.server.environments uses a module listed above it, which is the healthy direction.
packages.plugin-legacy uses packages.plugin-legacy.src.types, so a change to packages.plugin-legacy.src.types can break packages.plugin-legacy, while a change to packages.plugin-legacy can't break packages.plugin-legacy.src.types.
Position
Below the diagonal: packages.plugin-legacy uses a module listed above it, which is the healthy direction.
packages.plugin-legacy uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.plugin-legacy, while a change to packages.plugin-legacy can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.plugin-legacy uses a module listed above it, which is the healthy direction.
packages.plugin-legacy uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.plugin-legacy, while a change to packages.plugin-legacy can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.plugin-legacy uses a module listed above it, which is the healthy direction.
packages.plugin-legacy uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.plugin-legacy, while a change to packages.plugin-legacy can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.plugin-legacy uses a module listed above it, which is the healthy direction.
packages.plugin-legacy uses packages.vite.src.node.build, so a change to packages.vite.src.node.build can break packages.plugin-legacy, while a change to packages.plugin-legacy can't break packages.vite.src.node.build.
Position
Below the diagonal: packages.plugin-legacy uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.plugin-legacy.src.types, so a change to packages.plugin-legacy.src.types can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.plugin-legacy.src.types.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.plugins.resolve, so a change to packages.vite.src.node.plugins.resolve can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.plugins.resolve.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.server.transformRequest, so a change to packages.vite.src.node.server.transformRequest can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.server.transformRequest.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.preview, so a change to packages.vite.src.node.preview can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.preview.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.baseEnvironment, so a change to packages.vite.src.node.baseEnvironment can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.baseEnvironment.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node uses packages.vite.src.node.build, so a change to packages.vite.src.node.build can break packages.vite.src.node, while a change to packages.vite.src.node can't break packages.vite.src.node.build.
Position
Below the diagonal: packages.vite.src.node uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.environment, so a change to packages.vite.src.node.environment can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.environment.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.logger, so a change to packages.vite.src.node.logger can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.logger.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.plugins.resolve, so a change to packages.vite.src.node.plugins.resolve can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.plugins.resolve.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.plugins.html, so a change to packages.vite.src.node.plugins.html can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.plugins.html.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.plugin, so a change to packages.vite.src.node.plugin can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.plugin.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.server.bundledDev, so a change to packages.vite.src.node.server.bundledDev can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.server.bundledDev.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.server.pluginContainer, so a change to packages.vite.src.node.server.pluginContainer can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.server.pluginContainer.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.plugins.worker, so a change to packages.vite.src.node.plugins.worker can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.plugins.worker.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.optimizer, so a change to packages.vite.src.node.optimizer can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.optimizer.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.server.environment, so a change to packages.vite.src.node.server.environment can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.server.environment.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.server, so a change to packages.vite.src.node.server can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.server.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.config, so a change to packages.vite.src.node.config can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.config.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.baseEnvironment, so a change to packages.vite.src.node.baseEnvironment can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.baseEnvironment.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
packages.vite.src.node.plugins uses packages.vite.src.node.build, so a change to packages.vite.src.node.build can break packages.vite.src.node.plugins, while a change to packages.vite.src.node.plugins can't break packages.vite.src.node.build.
Position
Below the diagonal: packages.vite.src.node.plugins uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 43% · Weak · gated by D2, R3, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
59
High / Critical
A03:2025 — Software Supply Chain Failures
10
High / Critical
Roadmap
Top priorities: Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse; 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 (126 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (13 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (7 rows); Break each cycle by extracting the shared piece into a module both sides can import.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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 (126 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (13 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (7 rows).
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 `?`).
Bring the 4 bodies over 120 down to 120 or less in Cognitive Complexity — start with importAnalysisBuild.buildImportAnalysisPlugin (cognitive 246), css.cssPostPlugin (cognitive 138), ssrTransform.ssrTransformScript (cognitive 136).
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 — 69
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 — 794
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 — 475
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 76 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, 1315 of 1338 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `playground/json/json-bom/has-bom.json`, `playground/resolve/utf8-bom-package/package.json`, `playground/tsconfig-json-load-error/has-error/tsconfig.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `docs/.vitepress/config.ts`, `packages/create-vite/src/index.ts`, `packages/plugin-legacy/src/index.ts`, `REDACTED`, `packages/vite/rolldown.dts.config.ts`, … (+30 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.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 145 further occurrence(s) are not listed individually; the score already reflects all 185.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/vite/src/node/server/pluginContainer.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm -r --parallel --filter='./packages/*' run dev / sh: 1: pnpm: not found" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm -r --parallel --filter='./packages/*' run dev / sh: 1: pnpm: not found" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
R11 Import Boundaries — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 106 further occurrence(s) are not listed individually; the score already reflects all 146.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 109 further occurrence(s) are not listed individually; the score already reflects all 149.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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.
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.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 89 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with importAnalysis.importAnalysisPlugin.transform (cyclomatic 131), index.viteLegacyPlugin (cyclomatic 103), config.resolveConfig (cyclomatic 103). — 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 7 together lifts Cyclomatic Complexity from 4.6 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 128 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 importAnalysisBuild.buildImportAnalysisPlugin (cognitive 246), css.cssPostPlugin (cognitive 138), ssrTransform.ssrTransformScript (cognitive 136). — 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.0 to about 3.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 32 FunctionTooLong finding(s) in God Classes — start with index.ts (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 18 FileTooLong finding(s) in God Classes — start with index.ts (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with bundledDev.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
190 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 14 of the 190 (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: dep-ts-enum · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 73 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
183 skipped (178 with a documented reason), 237 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2149 tests (8 harness-style project(s) excluded from the assertion penalty).
No assertions: loads relative module scripts from the trailing slash directory · ×67playground/ssr-html/__tests__/ssr-html.spec.ts:61
Test project verifies nothing: playground/base-conflictplayground/base-conflict/__tests__/base-conflict.spec.ts:4
No direct assertions: named · ×170playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:19
Mock-dominated test: binding custom shortcuts with the %s · ×2packages/vite/src/node/__tests__/shortcuts.spec.ts:8
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 67 No assertions finding(s) in Test Quality — start with hmr-full-bundle-mode.spec.ts (11), legacy.spec.ts (8), hmr-ssr.spec.ts (8). — One of this dimension's main actionable groups (67 warning-level).
Resolve the 5 Skipped test finding(s) in Test Quality — start with worker-relative-base.spec.ts, ssr-deps.spec.ts, hmr-full-bundle-mode.spec.ts. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with base-conflict.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
11 outdated direct production npm dependency(ies) of 38 graded, 0 pinning defect(s), across 105 package.json (20 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 451 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 451 package(s) this repository's committed lockfile installs for a consumer — its 40 production, optional and peer dependency(ies), across 20 product package.json manifest(s), and everything those install in turn. Its 246 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: packages/create-vite/src/index.ts (29×59=1711); REDACTED (15×103=1545); REDACTED (22×68=1496) Repeated repair below the complexity floor: playground/optimize-deps/index.html (5 of 7 changes were fixes); playground/resolve/index.html (4 of 5 changes were fixes); playground/assets/index.html (3 of 4 changes were fixes)
Resolve the 29 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.ts (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.html (4). — One of this dimension's main actionable groups (4 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 Factor9.4 / 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.
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/vite/src/node/nativeConfigCompat.ts. Counted over 120 of the 207 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
35 deducted task-comment markers across 52817 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 32 TodoComment finding(s) in Explicit Debt — start with REDACTED (4), index.ts (3), REDACTED (3). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with pluginContainer.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 57 document(s) read across 260 unit(s).
Documentation: no build, run or usage examplepackages/vite/README.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 5 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
25 % of calls cross a namespace and 10 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 14 high, 42 medium, 3 low. semgrep hit a parse error in 47 file(s) — `docs/.vitepress/config.ts` (line 12), `packages/create-vite/src/index.ts` (line 10), `packages/plugin-legacy/src/index.ts` (line 9, line 1189), `REDACTED` (line 7), `packages/vite/rolldown.dts.config.ts` (line 15), … (+42 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-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.
19 of 120 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/create-vite/template-lit/src/my-element.js. Counted over 120 of the 207 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with App.tsx (2), App.jsx (2), app.tsx (2). — One of this dimension's main actionable groups (19 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.0 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×23) — packages/create-vite/template-vanilla-ts/src/main.ts:10, packages/create-vite/template-vanilla/src/main.js:10, playground/assets/index.html:203, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels7.4 / 10Strong✓ 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) — packages/create-vite/template-vanilla-ts/src/main.ts:18, packages/create-vite/template-vanilla/src/main.js:18
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — playground/client-reload/index.html:3
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.
Do you agree with this assessment?
AC3 · Page structure4.6 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×9) — packages/create-vite/template-lit-ts/index.html:2, packages/create-vite/template-lit/index.html:2, playground/assets-sanitize/index.html:1, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. (×11) — packages/create-vite/template-preact-ts/index.html:2, packages/create-vite/template-preact/index.html:2, packages/create-vite/template-qwik-ts/index.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×4) — packages/create-vite/template-react-ts/index.html:2, packages/create-vite/template-react/index.html:2, packages/create-vite/template-solid-ts/index.html:2, …
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×9) — playground/alias/index.html:1, playground/assets-sanitize/index.html:1, playground/assets/index.html:1, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×7) — playground/alias/index.html:1, playground/assets-sanitize/index.html:1, playground/assets/index.html:1, …
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 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.
`.treeshake-scoped-order` sets color: red on background-color: red — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — playground/css/treeshake-scoped/order/a-scoped.css:1
`.treeshake-scoped-order` sets color: red on background-color: blue — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — playground/css/treeshake-scoped/order/after.css:1
`.event-card:hover` moves (`animation: event-card-hover 10s ease-in-out 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. — docs/.vitepress/theme/live/Events.vue:76
`.testimonial-card::before` moves (`animation: move-background 16s ease-in-out 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. — docs/.vitepress/theme/landing/Community.vue:180
`.viteconf img` moves (`transition: transform 0.5s`) 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. — docs/.vitepress/theme/components/AsideSponsors.vue:62
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether 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.
`ViteDevServer` declares 17 required operations: `transformRequest`, `warmupRequest`, `transformIndexHtml`, `ssrTransform`, `ssrLoadModule`, `ssrRewriteStacktrace`, `ssrFixStacktrace`, `reloadModule`, `listen`, `close`, `printUrls`, `bindCLIShortcuts`, `restart`, `openBrowser`, `waitForRequestsIdle`, `_setInternalServer`, `_closeServer`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/vite/src/node/server/index.ts:329
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation0.0 / 10Critical✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`@vitejs/test-forward-console` (production) references the test project `@vitejs/test-forward-console-throw-dep`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/forward-console/package.json:13
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-a`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:13
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-b`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:14
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-c`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:15
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-d`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:16
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-e`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:17
`@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-f`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — playground/nested-deps/package.json:18
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — REDACTED:388
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/vite/src/node/build.ts:1790
`applyUpdate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/vite/src/shared/bundledDevHmr.ts:444
`resolveSpecifier` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — playground/dynamic-import/nested/index.js:208
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — playground/environment-react-ssr/src/entry-client.tsx:5
`message` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — playground/lib/src/main-multiple-output.js:4, playground/lib/src/sub-multiple-output.js:4
A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition. — playground/optimize-deps/dep-linked-include/index.mjs:15
`render` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — playground/ssr-conditions/src/app.js:4, playground/ssr-noexternal/src/entry-server.js:3
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×5) — packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:188, playground/css-codesplit-cjs/__tests__/css-codesplit-cjs.spec.ts:4, playground/hmr-full-bundle-mode/__tests__/hmr-full-bundle-mode.spec.ts:545, …
`default` has an empty body — confirm it's an intentional no-op and not an unfinished method. — playground/dynamic-import/files/mxd.js:1
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×5) — playground/tsconfig-json-load-error/src/main.ts:1, playground/tsconfig-json/nested-with-extends/main.ts:1, playground/tsconfig-json/nested/main.ts:1, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.6 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `playground`, `playground/css-lightningcss-proxy`, `playground/js-sourcemap`, `playground/optimize-missing-deps`, `playground/ssr` and 8 more.
`packages/vite/rollupLicensePlugin.ts` reports through `console.*` at line 111 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/vite/rollupLicensePlugin.ts:111
`packages/vite/src/node/env.ts` reports through `console.*` at line 120 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/vite/src/node/env.ts:120
`packages/vite/src/node/plugins/esbuild.ts` reports through `console.*` at line 89 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/vite/src/node/plugins/esbuild.ts:89
`packages/vite/src/node/plugins/oxc.ts` reports through `console.*` at line 185 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/vite/src/node/plugins/oxc.ts:185
`REDACTED` reports through `console.*` at line 305 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:305
`packages/vite/src/module-runner/hmrLogger.ts` reports through `console.*` at line 11 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/vite/src/module-runner/hmrLogger.ts:11
`packages/vite/src/module-runner/hmrLogger.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/vite/src/module-runner/hmrLogger.ts:12
`packages/vite/src/client/bundledDevClient.ts` reports through `console.*` at line 59 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/vite/src/client/bundledDevClient.ts:59
`packages/vite/src/client/bundledDevClient.ts` reports through `console.*` at line 60 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/vite/src/client/bundledDevClient.ts:60
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`semgrep.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:44
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.readdirSync` in `scanCommandLocks` 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/vite/src/node/commandLock.ts:100
`fs.readFileSync` in `scanCommandLocks` 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/vite/src/node/commandLock.ts:110
`fs.existsSync` in `resolveConfig` 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. — REDACTED:1901
`fs.existsSync` in `getTime` 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. — REDACTED:2468
`fs.writeFileSync` in `commit` 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/vite/src/node/optimizer/index.ts:589
`fs.existsSync` in `commit` 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/vite/src/node/optimizer/index.ts:603
`fs.renameSync` in `commit` 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/vite/src/node/optimizer/index.ts:616, packages/vite/src/node/optimizer/index.ts:621
`fs.readFileSync` in `extractExportsData` 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/vite/src/node/optimizer/index.ts:1153
`fs.existsSync` in `cleanupDepsCacheStaleDirs` 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/vite/src/node/optimizer/index.ts:1450
`fs.existsSync` in `callback to entries.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. — packages/vite/src/node/optimizer/scan.ts:255
`fs.readFileSync` in `getHmrImplementation` 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/vite/src/node/plugins/clientInjections.ts:160
`globSync` in `runPostCSS` 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. — REDACTED:1879
`fs.readFileSync` in `read` 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. — REDACTED:3418
`fs.readFileSync` in `compileLightningCSS` 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. — REDACTED:3512
`globSync` in `compileLightningCSS` 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) — REDACTED:3542, REDACTED:3545
`fs.existsSync` in `resolveId` 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/vite/src/node/plugins/preAlias.ts:67
`fs.existsSync` in `preview` 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/vite/src/node/preview.ts:149
`execSync` in `resolveServerOptions` 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/vite/src/node/server/index.ts:1316, packages/vite/src/node/server/index.ts:1322
`fs.readFileSync` in `resolveServerOptions` 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/vite/src/node/server/index.ts:1352
`fs.existsSync` in `viteIndexHtmlMiddleware` 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. — REDACTED:517
`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. — REDACTED:695
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 — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
packages/create-vite/template-react-ts/src/App.tsx:1 · packages/create-vite/template-react/src/App.jsx:1 — these 2 files are line-for-line copies of one another — 94 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. — packages/create-vite/template-react-ts/src/App.tsx:1
packages/create-vite/template-preact-ts/src/app.tsx:1 · packages/create-vite/template-preact/src/app.jsx:1 · packages/create-vite/template-qwik-ts/src/app.tsx:1 · packages/create-vite/template-qwik/src/app.jsx:1 · +2 more site(s) not listed — these 6 files are line-for-line copies of one another — 74 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. — packages/create-vite/template-preact-ts/src/app.tsx:1
playground/hmr-ssr/hmr.ts:16 · playground/hmr/hmr.ts:18 — the two spans are one implementation copied and then locally edited — 541 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. — playground/hmr-ssr/hmr.ts:16
playground/ssr-bundled-dev/src/app.js:3 · playground/ssr/src/app.js:3 — 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. — playground/ssr-bundled-dev/src/app.js:3
playground/hmr-ssr/vite.config.ts:18 · playground/hmr/vite.config.ts:74 — the two spans are one implementation copied and then locally edited — 271 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. — playground/hmr-ssr/vite.config.ts:18
packages/plugin-legacy/src/index.ts:62 · packages/vite/src/node/build.ts:1712 — 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/plugin-legacy/src/index.ts:62
playground/tailwind-v3/vite.config.ts:4 · playground/tailwind/vite.config.ts:5 — 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. — playground/tailwind-v3/vite.config.ts:4
REDACTED:6 · REDACTED: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. — REDACTED:6
packages/vite/src/node/server/hmr.ts:910 · packages/vite/src/shared/bundledDevHmr.ts:235 — the two spans are one implementation copied and then locally edited — 143 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/vite/src/node/server/hmr.ts:910
packages/vite/src/node/plugins/importAnalysisBuild.ts:567 · packages/vite/src/node/plugins/importAnalysisBuild.ts:651 — the two spans are one implementation copied and then locally edited — 215 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/vite/src/node/plugins/importAnalysisBuild.ts:567
REDACTED:8 · REDACTED: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. — REDACTED:8
packages/vite/src/node/server/pluginContainer.ts:481 · packages/vite/src/node/server/pluginContainer.ts:548 — the two spans are one implementation copied and then locally edited — 104 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/vite/src/node/server/pluginContainer.ts:481
REDACTED:3 · REDACTED:1 — the two spans are one implementation copied and then locally edited — 135 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. — REDACTED:3
packages/vite/src/node/plugins/html.ts:1587 · packages/vite/src/node/plugins/html.ts:1623 — 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/vite/src/node/plugins/html.ts:1587
REDACTED:16 · REDACTED:17 — 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. — REDACTED:16
playground/fs-serve/root/vite.config-base.js:16 · playground/fs-serve/root/vite.config.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — playground/fs-serve/root/vite.config-base.js:16
playground/multiple-entrypoints/entrypoints/a0.js:26 · playground/multiple-entrypoints/entrypoints/a1.js:27 · playground/multiple-entrypoints/entrypoints/a10.js:18 · playground/multiple-entrypoints/entrypoints/a2.js:26 · +7 more site(s) not listed — the 11 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 11 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. — playground/multiple-entrypoints/entrypoints/a0.js:26
playground/worker/vite.config-es.js:32 · playground/worker/vite.config-relative-base.js:31 — 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. — playground/worker/vite.config-es.js:32
REDACTED:61 · REDACTED:99 — 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. — REDACTED:61
packages/vite/src/node/build.ts:1413 · packages/vite/src/node/build.ts:1436 — 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/vite/src/node/build.ts:1413
packages/vite/src/node/optimizer/index.ts:279 · packages/vite/src/node/optimizer/index.ts:318 — the two spans are one implementation copied and then locally edited — 68 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/vite/src/node/optimizer/index.ts:279
playground/optimize-deps/dep-lodash-clonedeep/index.js:4 · playground/optimize-deps/dep-lodash/cloneDeep.js:4 — 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. — playground/optimize-deps/dep-lodash-clonedeep/index.js:4
REDACTED:155 · REDACTED:226 — the two spans are one implementation copied and then locally edited — 95 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. — REDACTED:155
packages/vite/rolldown.dts.config.ts:220 · packages/vite/rolldown.dts.config.ts:250 — 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/vite/rolldown.dts.config.ts:220
packages/vite/src/node/cli.ts:384 · packages/vite/src/node/cli.ts:478 — 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/vite/src/node/cli.ts:384
packages/vite/src/node/plugins/index.ts:199 · packages/vite/src/node/server/hmr.ts:383 — 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/vite/src/node/plugins/index.ts:199
REDACTED:792 · packages/vite/src/node/plugins/workerImportMetaUrl.ts:285 — 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. — REDACTED:792
packages/vite/src/node/server/hmr.ts:561 · packages/vite/src/node/server/hmr.ts: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. — packages/vite/src/node/server/hmr.ts:561
REDACTED:427 · REDACTED:458 — the two spans are one implementation copied and then locally edited — 77 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. — REDACTED:427
packages/vite/src/shared/bundledDevHmr.ts:335 · packages/vite/src/shared/bundledDevHmr.ts:380 — the two spans are one implementation copied and then locally edited — 84 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/vite/src/shared/bundledDevHmr.ts:335
playground/hmr/intermediate-file-delete/index.js:3 · playground/hmr/orphan-no-boundary/index.js:3 — 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. — playground/hmr/intermediate-file-delete/index.js:3
playground/optimize-deps/dep-lodash-clonedeep/index.js:4 · playground/optimize-deps/dep-lodash/cloneDeep.js:4 · playground/optimize-deps/dep-lodash/index.js:12 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — playground/optimize-deps/dep-lodash-clonedeep/index.js:4
REDACTED:44 · REDACTED:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:44
playground/worker/deeply-nested-second-worker.js:3 · playground/worker/deeply-nested-worker.js:3 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — playground/worker/deeply-nested-second-worker.js:3
packages/vite/src/node/idResolver.ts:48 · packages/vite/src/node/idResolver.ts:88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/vite/src/node/idResolver.ts:48
REDACTED:162 · REDACTED:210 — the two spans are one implementation copied and then locally edited — 102 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. — REDACTED:162
packages/vite/src/node/ssr/fetchModule.ts:169 · packages/vite/src/node/ssr/fetchModule.ts:257 — 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/vite/src/node/ssr/fetchModule.ts:169
playground/optimize-deps/cjs.js:41 · playground/optimize-deps/dedupe.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — playground/optimize-deps/cjs.js:41
packages/vite/src/node/nativeConfigCompat.ts:61 · packages/vite/src/node/nativeConfigCompat.ts:79 — 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/vite/src/node/nativeConfigCompat.ts:61
REDACTED:2463 · packages/vite/src/node/plugins/esbuild.ts:402 — the two spans are one implementation copied and then locally edited — 50 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. — REDACTED:2463
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/vite/src/node/__tests__/assetSource.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../assetSource) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/assetSource.spec.ts:3
packages/vite/src/node/__tests__/build.spec.ts:26 reaches past another workspace package's public entry into its internals with a relative path (../build) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/build.spec.ts:26
packages/vite/src/node/__tests__/build.spec.ts:36 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/build.spec.ts:36
packages/vite/src/node/__tests__/build.spec.ts:37 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/build.spec.ts:37
packages/vite/src/node/__tests__/commandLock.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../commandLock) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/commandLock.spec.ts:5
packages/vite/src/node/__tests__/commandLock.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/commandLock.spec.ts:6
packages/vite/src/node/__tests__/commandLock.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../processStartTime) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/commandLock.spec.ts:8
packages/vite/src/node/__tests__/commandLock.spec.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/commandLock.spec.ts:9
packages/vite/src/node/__tests__/config.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../shared/utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:8
packages/vite/src/node/__tests__/config.spec.ts:10 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:10
packages/vite/src/node/__tests__/config.spec.ts:16 reaches past another workspace package's public entry into its internals with a relative path (../env) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:16
packages/vite/src/node/__tests__/config.spec.ts:17 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:17
packages/vite/src/node/__tests__/config.spec.ts:19 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:19
packages/vite/src/node/__tests__/config.spec.ts:20 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/config.spec.ts:20
packages/vite/src/node/__tests__/constants.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../constants) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/constants.spec.ts:2
REDACTED:5 reaches past another workspace package's public entry into its internals with a relative path (../../shared/utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:5
REDACTED:6 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:6
REDACTED:7 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:7
REDACTED:8 reaches past another workspace package's public entry into its internals with a relative path (../server/environment) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:8
REDACTED:9 reaches past another workspace package's public entry into its internals with a relative path (../server/middlewares/static) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:9
REDACTED:13 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:13
packages/vite/src/node/__tests__/env.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../env) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/env.spec.ts:3
packages/vite/src/node/__tests__/environment.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../build) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/environment.spec.ts:4
packages/vite/src/node/__tests__/environment.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/environment.spec.ts:6
packages/vite/src/node/__tests__/environment.spec.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../ssr/runtime/serverModuleRunner) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/environment.spec.ts:7
packages/vite/src/node/__tests__/external.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../baseEnvironment) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/external.spec.ts:3
packages/vite/src/node/__tests__/external.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/external.spec.ts:4
packages/vite/src/node/__tests__/external.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../external) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/external.spec.ts:5
packages/vite/src/node/__tests__/filterRegex.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../plugins/assetImportMetaUrl) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/filterRegex.spec.ts:2
packages/vite/src/node/__tests__/filterRegex.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../plugins/workerImportMetaUrl) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/filterRegex.spec.ts:3
REDACTED:4 reaches past another workspace package's public entry into its internals with a relative path (../baseEnvironment) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:4
REDACTED:5 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:5
REDACTED:6 reaches past another workspace package's public entry into its internals with a relative path (../plugins/html) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:6
REDACTED:7 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — REDACTED:7
packages/vite/src/node/__tests__/http.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../constants) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/http.spec.ts:5
packages/vite/src/node/__tests__/logger.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/logger.spec.ts:3
packages/vite/src/node/__tests__/optimizer/cacheDir.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../../optimizer) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/optimizer/cacheDir.spec.ts:4
packages/vite/src/node/__tests__/optimizer/cacheDir.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/optimizer/cacheDir.spec.ts:8
packages/vite/src/node/__tests__/optimizer/discoverBeforeListen.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../..) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/optimizer/discoverBeforeListen.spec.ts:4
packages/vite/src/node/__tests__/optimizer/discoverBeforeListen.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../../shared/utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/vite/src/node/__tests__/optimizer/discoverBeforeListen.spec.ts:5
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 (126 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (13 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (7 rows).
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.
resolveConfig has cyclomatic complexity 104 and cognitive complexity 115; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1480
generateBundle has cyclomatic complexity 63 and cognitive complexity 222; 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/vite/src/node/plugins/importAnalysisBuild.ts:536
(anonymous) has cyclomatic complexity 54 and cognitive complexity 110; 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:511
init has cyclomatic complexity 54 and cognitive complexity 96; 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/create-vite/src/index.ts:468
loadAndTransform has cyclomatic complexity 47 and cognitive complexity 79; 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/vite/src/node/server/transformRequest.ts:237
mergeConfigRecursively has cyclomatic complexity 43 and cognitive complexity 58; 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:1448
tryNodeResolve has cyclomatic complexity 43 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:722
ssrTransformScript has cyclomatic complexity 42 and cognitive complexity 105; 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/vite/src/node/ssr/ssrTransform.ts:59
transform has cyclomatic complexity 42 and cognitive complexity 60; 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:224
renderChunk has cyclomatic complexity 39 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:721
viteTransformMiddleware has cyclomatic complexity 38 and cognitive complexity 76; 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/vite/src/node/server/middlewares/transform.ts:140
(anonymous) has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/optimizer/scan.ts:456
_createServer has cyclomatic complexity 33 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/server/index.ts:512
transformWithEsbuild has cyclomatic complexity 32 and cognitive complexity 64; 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/vite/src/node/plugins/esbuild.ts:97
handleHMRUpdate has cyclomatic complexity 31 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/server/hmr.ts:411
(anonymous) has cyclomatic complexity 31 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/plugins/html.ts:562
(anonymous) has cyclomatic complexity 31 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 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/vite/src/node/build.ts:713
enter has cyclomatic complexity 30 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/vite/src/node/ssr/ssrTransform.ts:530
parseGlobOptions has cyclomatic complexity 28 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/plugins/importMetaGlob.ts:153
isRefIdentifier has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vite/src/node/ssr/ssrTransform.ts:630
generateBundle has cyclomatic complexity 26 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1058
compileLightningCSS has cyclomatic complexity 26 and cognitive complexity 41; 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:3380
resolveId has cyclomatic complexity 26 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/server/pluginContainer.ts:351
resolveRolldownOptions has cyclomatic complexity 26 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/vite/src/node/build.ts:600
tryCleanFsResolve has cyclomatic complexity 25 and cognitive complexity 57; 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:613
handleMessage has cyclomatic complexity 25 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. — REDACTED:201
resolveDepOptimizationOptions has cyclomatic complexity 25 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. — REDACTED:1286
generateBundle has cyclomatic complexity 24 and cognitive complexity 66; 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/vite/src/node/plugins/manifest.ts:121
CallSiteToString has cyclomatic complexity 24 and cognitive complexity 41; 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/vite/src/module-runner/sourcemap/interceptor.ts:276
resolveId has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/optimizer/scan.ts:599
lexAcceptedHmrDeps has cyclomatic complexity 23 and cognitive complexity 57; 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/vite/src/node/server/hmr.ts:1009
viteIndexHtmlMiddleware has cyclomatic complexity 23 and cognitive complexity 50; 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:438
resolveId has cyclomatic complexity 22 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/plugins/preAlias.ts:34
handler has cyclomatic complexity 21 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/plugins/assetImportMetaUrl.ts:64
generateBundle 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/vite/src/node/plugins/asset.ts:371
handler 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. — REDACTED:604
resolveBuildEnvironmentOptions has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/build.ts:432
(anonymous) has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/optimizer/pluginConverter.ts:202
isCommandLockRecord has cyclomatic complexity 21 and cognitive complexity 13; 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/vite/src/node/commandLock.ts:40
generateBundle has cyclomatic complexity 20 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vite/src/node/plugins/html.ts:847
Do you agree with this assessment?
R3 · Large Files2.6 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 3467 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
REDACTED has 2755 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/vite/src/node/build.ts has 1859 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/vite/src/node/build.ts:1
REDACTED has 1786 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/vite/src/node/plugins/html.ts has 1612 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/vite/src/node/plugins/html.ts:1
packages/vite/src/node/server/index.ts has 1396 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/vite/src/node/server/index.ts:1
packages/vite/src/node/optimizer/index.ts has 1383 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/vite/src/node/optimizer/index.ts:1
packages/vite/src/node/server/pluginContainer.ts has 1220 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/vite/src/node/server/pluginContainer.ts:1
packages/create-vite/src/index.ts has 1194 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/create-vite/src/index.ts:1
REDACTED has 1126 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/vite/src/node/server/hmr.ts has 1107 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/vite/src/node/server/hmr.ts:1
REDACTED has 1099 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/plugin-legacy/src/index.ts has 1090 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/plugin-legacy/src/index.ts:1
REDACTED has 904 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/vite/src/node/plugins/importAnalysisBuild.ts has 855 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/vite/src/node/plugins/importAnalysisBuild.ts:1
packages/vite/src/node/plugins/asset.ts has 762 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/vite/src/node/plugins/asset.ts:1
packages/vite/src/node/optimizer/scan.ts has 734 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/vite/src/node/optimizer/scan.ts:1
packages/vite/src/node/ssr/ssrTransform.ts has 728 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/vite/src/node/ssr/ssrTransform.ts:1
packages/vite/src/node/optimizer/optimizer.ts has 705 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/vite/src/node/optimizer/optimizer.ts:1
packages/vite/src/node/server/mixedModuleGraph.ts has 694 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/vite/src/node/server/mixedModuleGraph.ts:1
packages/vite/src/node/plugins/importMetaGlob.ts has 643 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/vite/src/node/plugins/importMetaGlob.ts:1
packages/vite/src/node/server/bundledDev.ts has 631 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/vite/src/node/server/bundledDev.ts:1
REDACTED has 584 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
REDACTED has 555 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/vite/src/shared/bundledDevHmr.ts has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/vite/src/shared/bundledDevHmr.ts:1
REDACTED has 522 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/vite/src/node/server/transformRequest.ts has 506 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/vite/src/node/server/transformRequest.ts:1
packages/vite/src/node/cli.ts has 467 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/vite/src/node/cli.ts:1
packages/vite/src/node/plugins/esbuild.ts has 459 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/vite/src/node/plugins/esbuild.ts:1
packages/vite/src/node/server/environment.ts has 453 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/vite/src/node/server/environment.ts:1
packages/vite/src/node/plugins/wasm.ts has 447 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/vite/src/node/plugins/wasm.ts:1
packages/vite/src/node/plugin.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/vite/src/node/plugin.ts:1
packages/vite/src/node/server/moduleGraph.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/vite/src/node/server/moduleGraph.ts:1
REDACTED has 440 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
REDACTED has 433 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
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.
packages/vite/src/node/__tests__/plugins/license.spec.ts:8 imports './fixtures/license', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/vite/src/node/__tests__/plugins/license.spec.ts:8
packages/vite/src/node/server/__tests__/watcher.spec.ts:10 imports './fixtures/watcher/nested-root', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/vite/src/node/server/__tests__/watcher.spec.ts:10
packages/vite/src/node/ssr/__tests__/fixtures/modules/has-invalid-import.js:1 imports './non-existent.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/vite/src/node/ssr/__tests__/fixtures/modules/has-invalid-import.js:1
packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:10 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:10
packages/vite/src/node/ssr/__tests__/ssrStacktrace.spec.ts:5 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/vite/src/node/ssr/__tests__/ssrStacktrace.spec.ts:5
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. (×35) — packages/create-vite/src/index.ts:1, packages/create-vite/template-lit/src/my-element.js:1, packages/create-vite/template-lit-ts/src/my-element.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but packages/vite/src/node/__tests__/plugins/license.spec.ts and 4 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/vite/src/node/__tests__/plugins/license.spec.ts:8
Do you agree with this assessment?
R7 · Dead Code8.2 / 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.
8 file(s) (~1245 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/vite/src/types
3 file(s) (~86 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/client-reload
2 file(s) (~21 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×2) — playground/env-nested, playground/extensions
1 file(s) (~10 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/import-attribute
1 file(s) (~77 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/json
2 file(s) (~41 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×2) — playground/nested-deps, playground/optimize-deps-no-discovery
3 file(s) (~7 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — playground/optimize-deps/dep-not-js
2 file(s) (~76 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/proxy-bypass
3 file(s) (~67 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/proxy-hmr
1 file(s) (~9 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/proxy-hmr/other-app
3 file(s) (~30 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — playground/tailwind-sourcemap
Unreachable from the 792 application, 209 tooling and 615 test entry point(s) detected in this repo. Gate removals on `pnpm run typecheck` — an undetected custom entry would make these reachable.
no import path from any entry point (792 application, 209 tooling, 615 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 (×10) — packages/vite/bin/openChrome.js, playground/hmr-ssr/counter/index.ts, playground/css/postcss-caching/serve.ts, …
no import path from any entry point (792 application, 209 tooling, 615 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (playground/hmr-ssr/counter/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — playground/hmr-ssr/counter/dep.ts
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/vite/src/client/bundledDevClient.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/vite/src/client/bundledDevClient.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — REDACTED:564, REDACTED:597, REDACTED:614, …
No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. — packages/vite/src/node/baseEnvironment.ts:136
Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-module/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-module/index.js in the same commit, or the barrel will import a name that no longer exists. — playground/css/treeshake-module/b.js:3
Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-scoped/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-scoped/index.js in the same commit, or the barrel will import a name that no longer exists. (×3) — playground/css/treeshake-scoped/b.js:3, playground/css/treeshake-scoped/c.js:3, playground/css/treeshake-scoped/d.js:3
Nothing imports this binding — it is safe to review for removal. (×6) — playground/hmr-ssr/accept-exports/main-non-accepted/default.ts:1, playground/hmr-ssr/accept-exports/main-non-accepted/named.ts:5, playground/hmr-ssr/accept-exports/side-effects/side-effects.ts:1, …
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.
Only test files import it (first: playground/js-sourcemap/__tests__/js-sourcemap.spec.ts:5) — move it to devDependencies. — playground/js-sourcemap/package.json:13
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
packages/vite/src/node/build.ts → REDACTED → packages/vite/src/node/build.ts (one verified cycle inside a mutually-dependent group of 49 files) — packages/vite/src/node/build.ts:40
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
`wsHttpServer.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:411
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) (×10) — REDACTED:81, REDACTED:67, REDACTED:75, …
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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.
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`compileFromUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/vite/src/node/plugins/wasm.ts:78
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether 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 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.
`debug` at line 277 is called with an argument built by `importChain.join(' -> ')` (line 278), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/vite/src/shared/bundledDevHmr.ts:277
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.2 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`heroImg` 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) — packages/create-vite/template-vanilla-ts/src/main.ts:10, packages/create-vite/template-vanilla/src/main.js:10
`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) — packages/create-vite/template-vanilla-ts/src/main.ts:11, packages/create-vite/template-vanilla-ts/src/main.ts:37
`viteLogo` 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. (×4) — packages/create-vite/template-vanilla-ts/src/main.ts:12, packages/create-vite/template-vanilla-ts/src/main.ts:31, packages/create-vite/template-vanilla/src/main.js:12, …
``Count is ${counter}`` 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. — packages/create-vite/template-vanilla/src/counter.js:5
`javascriptLogo` 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) — packages/create-vite/template-vanilla/src/main.js:11, packages/create-vite/template-vanilla/src/main.js:37
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.
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.
`.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. (×4) — playground/vitestSetupUtils.ts:326, packages/vite/src/node/server/environment.ts:269, packages/vite/src/node/server/environment.ts:458, …
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. (×26) — playground/optimize-deps/injected-import.js:6, playground/lib/src/main-helpers-injection.js:8, packages/vite/src/node/commandLock.ts:89, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×8) — packages/vite/src/node/commandLock.ts:101, packages/vite/src/node/commandLock.ts:113, packages/vite/src/node/processStartTime.ts:58, …
`.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — packages/vite/src/node/server/bundledDev.ts:332, REDACTED:2115
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.
5/49 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.
~5.5 `!` null assertions per 1k TypeScript source lines — 311 assertion(s) across the 56784 source line(s) of the 276 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: REDACTED (32), packages/vite/src/node/plugins/html.ts (29), REDACTED (20). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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 — 4 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 5 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.
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 — 48 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — Not applicable: 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm -r --parallel --filter='./packages/*' run dev / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
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 does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
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) — 35 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — 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'.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: REDACTED:7 (express()))
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. 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.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. 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
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 69 finding(s)
AC1 · Text alternatives· <img> without a text alternative · ×23
<img> without a text alternative packages/create-vite/template-vanilla-ts/src/main.ts:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/create-vite/template-vanilla/src/main.js:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:203— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:214— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:219— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:328— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:332— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:336— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:340— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:352— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:356— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:361— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:365— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:374— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:378— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:384— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:388— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:394— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:398— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/assets/index.html:506— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/hmr/index.html:51— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/hmr/index.html:52— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative playground/html/malformed-url.html:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<html> without a lang playground/alias/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/assets-sanitize/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/assets/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/backend-integration/frontend/entrypoints/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/base/index.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 playground/build-old/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/chunk-importmap/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/cli-module/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang playground/cli/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×7
Document without a <title> playground/alias/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/assets-sanitize/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/assets/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/backend-integration/frontend/entrypoints/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/build-old/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/chunk-importmap/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> playground/cli-module/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AX8 · Test isolation· Production project references a test project · ×7
Production project references a test project: @vitejs/test-forward-console → @vitejs/test-forward-console-throw-dep playground/forward-console/package.json:13— `@vitejs/test-forward-console` (production) references the test project `@vitejs/test-forward-console-throw-dep`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-a playground/nested-deps/package.json:13— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-a`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-b playground/nested-deps/package.json:14— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-b`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-c playground/nested-deps/package.json:15— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-c`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-d playground/nested-deps/package.json:16— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-d`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-e playground/nested-deps/package.json:17— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-e`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @vitejs/test-nested-deps → @vitejs/test-package-f playground/nested-deps/package.json:18— `@vitejs/test-nested-deps` (production) references the test project `@vitejs/test-package-f`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text packages/create-vite/template-vanilla-ts/src/main.ts:18— 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 packages/create-vite/template-vanilla/src/main.js:18— 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).
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label playground/client-reload/index.html:3— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
No assertions: loads relative module scripts from the trailing slash directory playground/ssr-html/__tests__/ssr-html.spec.ts:61— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: with Vite runtime playground/ssr-html/__tests__/ssr-html.spec.ts:130— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: with Vite SSR playground/ssr-html/__tests__/ssr-html.spec.ts:142— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: with Vite runtime playground/ssr-html/__tests__/ssr-html.spec.ts:152— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ssr.resolve settings do not affect non-ssr imports playground/ssr-conditions/__tests__/ssr-conditions.spec.ts:23— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should load the worker playground/legacy/__tests__/legacy.spec.ts:14— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work playground/legacy/__tests__/legacy.spec.ts:18— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: import.meta.env.LEGACY playground/legacy/__tests__/legacy.spec.ts:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: transpiles down iterators correctly playground/legacy/__tests__/legacy.spec.ts:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: async generator playground/legacy/__tests__/legacy.spec.ts:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: wraps with iife playground/legacy/__tests__/legacy.spec.ts:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: generates assets playground/legacy/__tests__/legacy.spec.ts:46— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should load dynamic import with css playground/legacy/__tests__/legacy.spec.ts:96— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should load and execute the JS file playground/legacy/__tests__/no-polyfills/legacy-no-polyfills.spec.ts:4— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should load and execute the JS file playground/legacy/__tests__/modern-target/legacy-modern-target.spec.ts:4— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: correct sourcemap during ssr dev when using object as "define" value playground/js-sourcemap/__tests__/js-sourcemap.spec.ts:461— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: css playground/html/__tests__/html.spec.ts:84— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: passing relative path to rolldownOptions.input works playground/html/__tests__/html.spec.ts:429— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should warmup /warmup/warm.js playground/html/__tests__/html.spec.ts:435— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: invalidate in circular dep should not trigger infinite HMR playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:275— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: invalidate in circular dep should be hot updated if possible playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:285— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: plugin hmr handler + custom event playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:295— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: plugin hmr remove custom events playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:301— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: plugin client-server communication playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:308— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not full reload playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:585— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/assetSource.spec.ts:3— packages/vite/src/node/__tests__/assetSource.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../assetSource) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/build.spec.ts:26— packages/vite/src/node/__tests__/build.spec.ts:26 reaches past another workspace package's public entry into its internals with a relative path (../build) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/build.spec.ts:36— packages/vite/src/node/__tests__/build.spec.ts:36 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/build.spec.ts:37— packages/vite/src/node/__tests__/build.spec.ts:37 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/commandLock.spec.ts:5— packages/vite/src/node/__tests__/commandLock.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../commandLock) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/commandLock.spec.ts:6— packages/vite/src/node/__tests__/commandLock.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/commandLock.spec.ts:8— packages/vite/src/node/__tests__/commandLock.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../processStartTime) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/commandLock.spec.ts:9— packages/vite/src/node/__tests__/commandLock.spec.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:8— packages/vite/src/node/__tests__/config.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../shared/utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:10— packages/vite/src/node/__tests__/config.spec.ts:10 reaches past another workspace package's public entry into its internals with a relative path (../config) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:16— packages/vite/src/node/__tests__/config.spec.ts:16 reaches past another workspace package's public entry into its internals with a relative path (../env) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:17— packages/vite/src/node/__tests__/config.spec.ts:17 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:19— packages/vite/src/node/__tests__/config.spec.ts:19 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/config.spec.ts:20— packages/vite/src/node/__tests__/config.spec.ts:20 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/constants.spec.ts:2— packages/vite/src/node/__tests__/constants.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../constants) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:5— REDACTED:5 reaches past another workspace package's public entry into its internals with a relative path (../../shared/utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:6— REDACTED:6 reaches past another workspace package's public entry into its internals with a relative path (../logger) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:7— REDACTED:7 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:8— REDACTED:8 reaches past another workspace package's public entry into its internals with a relative path (../server/environment) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:9— REDACTED:9 reaches past another workspace package's public entry into its internals with a relative path (../server/middlewares/static) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] REDACTED:13— REDACTED:13 reaches past another workspace package's public entry into its internals with a relative path (../utils) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/env.spec.ts:3— packages/vite/src/node/__tests__/env.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../env) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/environment.spec.ts:4— packages/vite/src/node/__tests__/environment.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../build) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/environment.spec.ts:6— packages/vite/src/node/__tests__/environment.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../server) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/vite/src/node/__tests__/environment.spec.ts:7— packages/vite/src/node/__tests__/environment.spec.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../ssr/runtime/serverModuleRunner) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×35
No test reaches this file packages/create-vite/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-lit/src/my-element.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 packages/create-vite/template-lit-ts/src/my-element.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vite/scripts/benchCircularImport.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/vite/rollupLicensePlugin.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-react-ts/src/App.tsx: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-vite/template-react/src/App.jsx: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-vite/template-solid-ts/src/App.tsx: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-vite/template-solid/src/App.jsx: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-vite/template-preact-ts/src/app.tsx: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-vite/template-preact/src/app.jsx: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-vite/template-qwik-ts/src/app.tsx: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-vite/template-qwik/src/app.jsx: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/vite/bin/openChrome.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 packages/create-vite/template-vanilla-ts/src/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-vanilla/src/main.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 packages/vite/scripts/generateTarget.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 playground/devtools/src/counter.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 playground/devtools/src/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-react-ts/src/main.tsx: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-vite/template-react/src/main.jsx: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-vite/template-svelte-ts/src/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-svelte/src/main.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 packages/create-vite/template-vanilla-ts/src/counter.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/create-vite/template-vanilla/src/counter.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.
TodoComment playground/vitestSetupUtils.ts:327— // TODO: workaround — an edit fired while no client is connected is — 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 playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:29— // TODO: inline worker should inline assets — 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 playground/ssr-deps/__tests__/ssr-deps.spec.ts:130— // TODO: the server file is not imported on the client at all — 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 playground/hmr-ssr/__tests__/hmr-ssr.spec.ts:955— // TODO: why is `runner.clearCache()` not enough? — 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/vite/src/node/build.ts:689— // TODO: remove this and enable rolldown's CSS support later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:450— // TODO: remove this and enable rolldown's CSS support later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/vite/src/node/optimizer/index.ts:850— // TODO: remove this and enable rolldown's CSS support later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/vite/src/node/optimizer/index.ts:1126— // TODO: remove this and enable rolldown's CSS support later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:1285— // TODO: Introduce ResolvedDepOptimizationOptions — 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:2243— // TODO: Deprecate config.getSortedPlugins and config.getSortedPluginHooks — 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/vite/src/node/http.ts:141— // @ts-expect-error TODO: is this correct? — 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/vite/src/node/ssr/fetchModule.ts:244— // TODO: seems like rolldown uses `process.cwd()` instead of `config.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 packages/vite/src/node/ssr/fetchModule.ts:251— // TODO: this should be done in rolldown, there is already a function for 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 packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts:53— // TODO: this fails during bundle, not at runtime — 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/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts:154— // TODO: fix in rolldown https://github.com/rolldown/rolldown/issues/7722
TodoComment packages/vite/src/node/server/bundledDev.ts:211— // TODO: send to the specific client — 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/vite/src/node/server/hmr.ts:468— // TODO: support handleHotUpdate / hotUpdate — 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/vite/src/node/server/index.ts:763— // TODO: Should we also update the node moduleGraph for backward compatibility? — 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/vite/src/node/server/mixedModuleGraph.ts:408— // TODO: Maybe this isn't needed? — 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/vite/src/node/server/pluginContainer.ts:992— // TODO: move it to overrides — 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/vite/src/node/server/transformRequest.ts:71— // TODO: This function could be moved to the DevEnvironment class. — 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:152— // TODO: the main server port may not have been chosen yet as it may use the next available — 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/vite/src/node/server/middlewares/transform.ts:61— // TODO: consolidate this regex pattern with the url, raw, and inline checks in 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:1734— // TODO: support source map — 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:3431— // TODO: support source map — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FunctionTooLong: config.resolveConfig REDACTED:1480— FunctionTooLong — resolveConfig runs 559 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 459 over it, 5.59× 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: importAnalysis.importAnalysisPlugin REDACTED:185— FunctionTooLong — importAnalysisPlugin runs 465 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 365 over it, 4.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: html.buildHtmlPlugin packages/vite/src/node/plugins/html.ts:438— FunctionTooLong — buildHtmlPlugin runs 440 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 340 over it, 4.40× 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: importAnalysis.importAnalysisPlugin.transform REDACTED:224— FunctionTooLong — importAnalysisPlugin.transform runs 437 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 337 over it, 4.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.viteLegacyPlugin packages/plugin-legacy/src/index.ts:207— FunctionTooLong — viteLegacyPlugin runs 426 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 326 over it, 4.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: optimizer.createDepsOptimizer packages/vite/src/node/optimizer/optimizer.ts:40— FunctionTooLong — createDepsOptimizer runs 391 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 291 over it, 3.91× 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: importAnalysisBuild.buildImportAnalysisPlugin packages/vite/src/node/plugins/importAnalysisBuild.ts:417— FunctionTooLong — buildImportAnalysisPlugin runs 353 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× 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: scan.rolldownScanPlugin packages/vite/src/node/optimizer/scan.ts:366— FunctionTooLong — rolldownScanPlugin runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× 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: ws.createWebSocketServer REDACTED:118— FunctionTooLong — createWebSocketServer runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.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.
FunctionTooLong: index.init packages/create-vite/src/index.ts:468— FunctionTooLong — init runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) 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: indexHtml.devHtmlHook REDACTED:135— FunctionTooLong — devHtmlHook runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: html.buildHtmlPlugin.generateBundle packages/vite/src/node/plugins/html.ts:847— FunctionTooLong — buildHtmlPlugin.generateBundle runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: worker.webWorkerPlugin REDACTED:679— FunctionTooLong — webWorkerPlugin runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rolldownDepPlugin.rolldownDepPlugin REDACTED:61— FunctionTooLong — rolldownDepPlugin runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: hmr.handleHMRUpdate packages/vite/src/node/server/hmr.ts:411— FunctionTooLong — handleHMRUpdate runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: build.resolveRolldownOptions packages/vite/src/node/build.ts:600— FunctionTooLong — resolveRolldownOptions runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: transform.transformMiddleware packages/vite/src/node/server/middlewares/transform.ts:130— FunctionTooLong — transformMiddleware runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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: asset.assetPlugin packages/vite/src/node/plugins/asset.ts:190— FunctionTooLong — assetPlugin runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.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.
FunctionTooLong: index.runOptimizeDeps packages/vite/src/node/optimizer/index.ts:514— FunctionTooLong — runOptimizeDeps runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: importMetaGlob.transformGlobImport packages/vite/src/node/plugins/importMetaGlob.ts:418— FunctionTooLong — transformGlobImport runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: transformRequest.loadAndTransform packages/vite/src/node/server/transformRequest.ts:237— FunctionTooLong — loadAndTransform runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: worker.bundleWorkerEntry REDACTED:401— FunctionTooLong — bundleWorkerEntry runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: resolve.oxcResolvePlugin REDACTED:221— FunctionTooLong — oxcResolvePlugin runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: config.bundleConfigFile REDACTED:2576— FunctionTooLong — bundleConfigFile runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: hmr.normalizeHotChannel packages/vite/src/node/server/hmr.ts:212— FunctionTooLong — normalizeHotChannel runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Swallowed exception (empty catch) playground/vitestSetupUtils.ts:326— `.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) playground/optimize-deps/injected-import.js:6— 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) playground/lib/src/main-helpers-injection.js:8— 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/vite/src/node/commandLock.ts:89— 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:1661— 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:2653— 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/vite/src/node/packages.ts:19— 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/vite/src/node/packages.ts:119— 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/vite/src/node/packages.ts:150— 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/vite/src/node/processStartTime.ts:31— 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:406— 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/vite/src/node/server/bundledDev.ts:332— `.then(…, () => {})` 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/vite/src/node/server/environment.ts:269— `.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/vite/src/node/server/environment.ts:458— `.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) REDACTED:127— 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/vite/src/node/server/index.ts:1367— 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/vite/src/node/server/openBrowser.ts:102— 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/vite/src/node/server/pluginContainer.ts:979— 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/vite/src/node/server/pluginContainer.ts:1018— 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/vite/src/node/server/searchRoot.ts:48— 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/vite/src/node/server/sourcemap.ts:66— 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:114— 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:313— 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/vite/src/node/server/middlewares/hostCheck.ts:40— 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:100— 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.
Hotspot: packages/create-vite/src/index.ts packages/create-vite/src/index.ts:468— packages/create-vite/src/index.ts changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in index.init at line 468. 16 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/create-vite/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1480— REDACTED changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 103 in config.resolveConfig at line 1480. 5 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:527— REDACTED changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in css.cssPostPlugin at line 527. 8 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:224— REDACTED changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in importAnalysis.importAnalysisPlugin.transform at line 224. 3 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/importAnalysisBuild.ts packages/vite/src/node/plugins/importAnalysisBuild.ts:417— packages/vite/src/node/plugins/importAnalysisBuild.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 88 in importAnalysisBuild.buildImportAnalysisPlugin at line 417. 7 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/importAnalysisBuild.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/server/index.ts packages/vite/src/node/server/index.ts:512— packages/vite/src/node/server/index.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in index._createServer at line 512. 6 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/server/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/build.ts packages/vite/src/node/build.ts:600— packages/vite/src/node/build.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in build.resolveRolldownOptions at line 600. 7 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/build.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1448— REDACTED changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in utils.mergeConfigRecursively at line 1448. 8 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/html.ts packages/vite/src/node/plugins/html.ts:438— packages/vite/src/node/plugins/html.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in html.buildHtmlPlugin at line 438. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/html.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:135— REDACTED changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in indexHtml.devHtmlHook at line 135. 4 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:61— REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in rolldownDepPlugin.rolldownDepPlugin at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/asset.ts packages/vite/src/node/plugins/asset.ts:190— packages/vite/src/node/plugins/asset.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in asset.assetPlugin at line 190. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/asset.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/server/middlewares/transform.ts packages/vite/src/node/server/middlewares/transform.ts:130— packages/vite/src/node/server/middlewares/transform.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in transform.transformMiddleware at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/server/middlewares/transform.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/optimizer/scan.ts packages/vite/src/node/optimizer/scan.ts:366— packages/vite/src/node/optimizer/scan.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in scan.rolldownScanPlugin at line 366. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/optimizer/scan.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:221— REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in resolve.oxcResolvePlugin at line 221. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/server/bundledDev.ts packages/vite/src/node/server/bundledDev.ts:132— packages/vite/src/node/server/bundledDev.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in BundledDev.listen at line 132. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/server/bundledDev.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:679— REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in worker.webWorkerPlugin at line 679. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/optimizer/optimizer.ts packages/vite/src/node/optimizer/optimizer.ts:40— packages/vite/src/node/optimizer/optimizer.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in optimizer.createDepsOptimizer at line 40. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/optimizer/optimizer.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/workerImportMetaUrl.ts packages/vite/src/node/plugins/workerImportMetaUrl.ts:193— packages/vite/src/node/plugins/workerImportMetaUrl.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in workerImportMetaUrl.workerImportMetaUrlPlugin at line 193. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/workerImportMetaUrl.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:118— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in ws.createWebSocketServer at line 118. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/preview.ts packages/vite/src/node/preview.ts:131— packages/vite/src/node/preview.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in preview.preview at line 131. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/preview.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/server/environment.ts packages/vite/src/node/server/environment.ts:116— packages/vite/src/node/server/environment.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DevEnvironment.constructor at line 116. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/server/environment.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/shared/bundledDevHmr.ts packages/vite/src/shared/bundledDevHmr.ts:153— packages/vite/src/shared/bundledDevHmr.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in BundledDevHMRClient.bubble at line 153. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/shared/bundledDevHmr.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/wasm.ts packages/vite/src/node/plugins/wasm.ts:108— packages/vite/src/node/plugins/wasm.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in wasm.wasmHelperPlugin at line 108. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/wasm.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vite/src/node/plugins/assetImportMetaUrl.ts packages/vite/src/node/plugins/assetImportMetaUrl.ts:37— packages/vite/src/node/plugins/assetImportMetaUrl.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in assetImportMetaUrl.assetImportMetaUrlPlugin at line 37. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- packages/vite/src/node/plugins/assetImportMetaUrl.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
+ 4 more in this group — see findings.md.
AC3 · Page structure· Page without a main landmark · ×24
Page without a main landmark packages/create-vite/template-lit-ts/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 packages/create-vite/template-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 packages/create-vite/template-preact-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-preact/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-qwik-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-qwik/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-react-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-react/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-solid-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-solid/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-svelte-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-svelte/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-vanilla-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-vanilla/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-vue-ts/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/create-vite/template-vue/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark playground/assets-sanitize/index.html:1— 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 playground/assets/index.html:1— 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 playground/backend-integration/frontend/entrypoints/index.html:1— 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 playground/base-conflict/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark playground/base/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 playground/build-old/index.html:1— 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 playground/chunk-importmap/index.html:1— 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 playground/cli-module/index.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Sync-over-async blocking packages/vite/src/node/commandLock.ts:100— `fs.readdirSync` in `scanCommandLocks` 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/vite/src/node/commandLock.ts:110— `fs.readFileSync` in `scanCommandLocks` 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 REDACTED:1901— `fs.existsSync` in `resolveConfig` 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 REDACTED:2468— `fs.existsSync` in `getTime` 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/vite/src/node/optimizer/index.ts:589— `fs.writeFileSync` in `commit` 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/vite/src/node/optimizer/index.ts:603— `fs.existsSync` in `commit` 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/vite/src/node/optimizer/index.ts:616— `fs.renameSync` in `commit` 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/vite/src/node/optimizer/index.ts:621— `fs.renameSync` in `commit` 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/vite/src/node/optimizer/index.ts:1153— `fs.readFileSync` in `extractExportsData` 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/vite/src/node/optimizer/index.ts:1450— `fs.existsSync` in `cleanupDepsCacheStaleDirs` 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/vite/src/node/optimizer/scan.ts:255— `fs.existsSync` in `callback to entries.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/vite/src/node/plugins/clientInjections.ts:160— `fs.readFileSync` in `getHmrImplementation` 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 REDACTED:1879— `globSync` in `runPostCSS` 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 REDACTED:3418— `fs.readFileSync` in `read` 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 REDACTED:3512— `fs.readFileSync` in `compileLightningCSS` 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 REDACTED:3542— `globSync` in `compileLightningCSS` 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 REDACTED:3545— `globSync` in `compileLightningCSS` 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/vite/src/node/plugins/preAlias.ts:67— `fs.existsSync` in `resolveId` 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/vite/src/node/preview.ts:149— `fs.existsSync` in `preview` 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/vite/src/node/server/index.ts:1316— `execSync` in `resolveServerOptions` 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/vite/src/node/server/index.ts:1322— `execSync` in `resolveServerOptions` 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/vite/src/node/server/index.ts:1352— `fs.readFileSync` in `resolveServerOptions` 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 REDACTED:517— `fs.existsSync` in `viteIndexHtmlMiddleware` 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 REDACTED:695— `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.
FileTooLong: REDACTED REDACTED— FileTooLong — 2496 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1996 over it, 4.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1801 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1301 over it, 3.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1261 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 761 over it, 2.52× 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: node/build.ts packages/vite/src/node/build.ts— FileTooLong — 1226 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 726 over it, 2.45× 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: plugins/html.ts packages/vite/src/node/plugins/html.ts— FileTooLong — 1145 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 645 over it, 2.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: server/pluginContainer.ts packages/vite/src/node/server/pluginContainer.ts— FileTooLong — 894 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 394 over it, 1.79× 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: optimizer/index.ts packages/vite/src/node/optimizer/index.ts— FileTooLong — 874 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 374 over it, 1.75× 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: server/index.ts packages/vite/src/node/server/index.ts— FileTooLong — 869 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 369 over it, 1.74× 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/index.ts packages/create-vite/src/index.ts— FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 337 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 785 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 285 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: importAnalysisPlugin (185-916). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: server/hmr.ts packages/vite/src/node/server/hmr.ts— FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 262 over it, 1.52× 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/index.ts packages/plugin-legacy/src/index.ts— FileTooLong — 761 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 261 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 163 over it, 1.33× 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: plugins/importAnalysisBuild.ts packages/vite/src/node/plugins/importAnalysisBuild.ts— FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 113 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: plugins/asset.ts packages/vite/src/node/plugins/asset.ts— FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 59 over it, 1.12× 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: optimizer/scan.ts packages/vite/src/node/optimizer/scan.ts— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 over it, 1.02× 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: plugins/importMetaGlob.ts packages/vite/src/node/plugins/importMetaGlob.ts— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×11
Untrusted text written into markup unescaped packages/create-vite/template-vanilla-ts/src/main.ts:10— `heroImg` 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/create-vite/template-vanilla-ts/src/main.ts:11— `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/create-vite/template-vanilla-ts/src/main.ts:12— `viteLogo` 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/create-vite/template-vanilla-ts/src/main.ts:31— `viteLogo` 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/create-vite/template-vanilla-ts/src/main.ts:37— `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/create-vite/template-vanilla/src/counter.js:5— ``Count is ${counter}`` 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/create-vite/template-vanilla/src/main.js:10— `heroImg` 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/create-vite/template-vanilla/src/main.js:11— `javascriptLogo` 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/create-vite/template-vanilla/src/main.js:12— `viteLogo` 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/create-vite/template-vanilla/src/main.js:31— `viteLogo` 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/create-vite/template-vanilla/src/main.js:37— `javascriptLogo` 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.
Fake-async — async method never awaits packages/vite/src/node/build.ts:1790— `init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/vite/src/shared/bundledDevHmr.ts:444— `applyUpdate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/dynamic-import/nested/index.js:208— `resolveSpecifier` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/environment-react-ssr/src/entry-client.tsx:5— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/lib/src/main-multiple-output.js:4— `message` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/lib/src/sub-multiple-output.js:4— `message` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/ssr-conditions/src/app.js:4— `render` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits playground/ssr-noexternal/src/entry-server.js:3— `render` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (15 lines × 2 locations) packages/vite/rolldown.dts.config.ts:220— packages/vite/rolldown.dts.config.ts:220 · packages/vite/rolldown.dts.config.ts:250 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) packages/vite/src/node/cli.ts:384— packages/vite/src/node/cli.ts:384 · packages/vite/src/node/cli.ts:478 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) packages/vite/src/node/plugins/index.ts:199— packages/vite/src/node/plugins/index.ts:199 · packages/vite/src/node/server/hmr.ts:383 — 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 (15 lines × 2 locations) REDACTED:792— REDACTED:792 · packages/vite/src/node/plugins/workerImportMetaUrl.ts:285 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) packages/vite/src/node/server/hmr.ts:561— packages/vite/src/node/server/hmr.ts:561 · packages/vite/src/node/server/hmr.ts: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 (15 lines × 2 locations) playground/hmr/intermediate-file-delete/index.js:3— playground/hmr/intermediate-file-delete/index.js:3 · playground/hmr/orphan-no-boundary/index.js:3 — 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 (15 lines × 2 locations) REDACTED:44— REDACTED:44 · REDACTED:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) playground/worker/deeply-nested-second-worker.js:3— playground/worker/deeply-nested-second-worker.js:3 · playground/worker/deeply-nested-worker.js:3 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Swallowed exception (caught, then discarded) packages/vite/src/node/commandLock.ts:101— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vite/src/node/commandLock.ts:113— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vite/src/node/processStartTime.ts:58— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:1886— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:48— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vite/src/node/plugins/wasm.ts:131— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) REDACTED:640— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vite/src/module-runner/importMetaResolver.ts:52— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Skipped test: inlined playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:30— Skipped — switched off by test.skip
Skipped test: handle isomorphic module updates playground/ssr-deps/__tests__/ssr-deps.spec.ts:134— Skipped — switched off by test.skip
Skipped test: chained invalidate in an import cycle settles playground/hmr-full-bundle-mode/__tests__/hmr-full-bundle-mode.spec.ts:545— Skipped — switched off by test.skip
Skipped test: should load both stylesheets playground/css-codesplit-cjs/__tests__/css-codesplit-cjs.spec.ts:4— Skipped — switched off by test.skip
Skipped test: parse error packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:188— Skipped — switched off by test.skip
R4 · Test Coverage· This test file cannot be loaded · ×5
This test file cannot be loaded packages/vite/src/node/__tests__/plugins/license.spec.ts:8— packages/vite/src/node/__tests__/plugins/license.spec.ts:8 imports './fixtures/license', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/vite/src/node/server/__tests__/watcher.spec.ts:10— packages/vite/src/node/server/__tests__/watcher.spec.ts:10 imports './fixtures/watcher/nested-root', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/vite/src/node/ssr/__tests__/fixtures/modules/has-invalid-import.js:1— packages/vite/src/node/ssr/__tests__/fixtures/modules/has-invalid-import.js:1 imports './non-existent.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:10— packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:10 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/vite/src/node/ssr/__tests__/ssrStacktrace.spec.ts:5— packages/vite/src/node/ssr/__tests__/ssrStacktrace.spec.ts:5 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
Dead file (~1 LoC) playground/hmr/orphan-no-boundary/local.js— no import path from any entry point (792 application, 209 tooling, 615 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 (~1 LoC) playground/js-sourcemap/plugin-foo.js— no import path from any entry point (792 application, 209 tooling, 615 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 (~1 LoC) playground/resolve/exact-extension/file.js.js— no import path from any entry point (792 application, 209 tooling, 615 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 (~1 LoC) playground/resolve/imports-path/star/dollar$$.js— no import path from any entry point (792 application, 209 tooling, 615 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 (~1 LoC) playground/resolve/non-normalized.js— no import path from any entry point (792 application, 209 tooling, 615 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
Repeated repair: playground/optimize-deps/index.html playground/optimize-deps/index.html:254— playground/optimize-deps/index.html changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is index.html.callPeerDep().catch() at line 254), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(deps): update all non-major dependencies (#24027)”; “fix(optimizer): resolve subpath imports (#) with Vite's resolver (#23959)”; “fix(optimizer): scan deep imports with custom extensions (#23678)”; “fix(optimize-deps): avoid "unsupported" warnings for browser:false mappings (#23590)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- playground/optimize-deps/index.html`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: playground/resolve/index.html playground/resolve/index.html:222— playground/resolve/index.html changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is index.html.text at line 222), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(deps): update all non-major dependencies (#24027)”; “fix(bundled-dev): allow named imports from Node built-ins (#23858)”; “fix(resolve): support subpath imports with multiple `#` (#23631)”; “fix(resolve): update resolve.exports to 2.0.4 (#23739)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- playground/resolve/index.html`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: playground/assets/index.html playground/assets/index.html:742— playground/assets/index.html changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is index.html.testDynamicImportMetaUrlWithTernaryOperator at line 742), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(html): resolve percent-encoded srcset urls (#23609)”; “fix(html): don't inline preload link targets (fix #13355) (#23387)”; “fix(build): keep hash placeholders as-is in `resolveFileUrl` hook (#23422)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- playground/assets/index.html`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: playground/fs-serve/root/src/index.html playground/fs-serve/root/src/index.html:51— playground/fs-serve/root/src/index.html changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is index.html.joinUrlSegments at line 51), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(wasm): reject `.wasm` outside `server.fs` (#23914)”; “fix(server): store ids to `safeModulePaths` rather than URLs (#23656)”; “fix(server): check `fs.serve` for `?vite-wasm-instance` (#23655)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:27:35 +09:00' --until='2026-11-13 18:27:35 +09:00' --full-history --no-merges -- playground/fs-serve/root/src/index.html`: 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×3
Animation without a prefers-reduced-motion guard docs/.vitepress/theme/live/Events.vue:76— `.event-card:hover` moves (`animation: event-card-hover 10s ease-in-out 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 docs/.vitepress/theme/landing/Community.vue:180— `.testimonial-card::before` moves (`animation: move-background 16s ease-in-out 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 docs/.vitepress/theme/components/AsideSponsors.vue:62— `.viteconf img` moves (`transition: transform 0.5s`) 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.
Duplicated block (14 lines × 2 locations) packages/vite/src/node/idResolver.ts:48— packages/vite/src/node/idResolver.ts:48 · packages/vite/src/node/idResolver.ts:88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) packages/vite/src/node/ssr/fetchModule.ts:169— packages/vite/src/node/ssr/fetchModule.ts:169 · packages/vite/src/node/ssr/fetchModule.ts:257 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) playground/optimize-deps/cjs.js:41— playground/optimize-deps/cjs.js:41 · playground/optimize-deps/dedupe.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
optimizer.createDepsOptimizer::runOptimizer (cognitive 39) packages/vite/src/node/optimizer/optimizer.ts:324— optimizer.createDepsOptimizer::runOptimizer has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (30 pts), ternaries 2 (7 pts), boolean chains 1, error handling 1 (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. This shape REPEATS in the file: one other method here (optimizer.createDepsOptimizer::onCrawlEnd) 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.
optimizer.createDepsOptimizer::onCrawlEnd (cognitive 26) packages/vite/src/node/optimizer/optimizer.ts:643— optimizer.createDepsOptimizer::onCrawlEnd has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 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. This shape REPEATS in the file: one other method here (optimizer.createDepsOptimizer::runOptimizer) 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.
Off the main sequence: dep-ts-enum — dep-ts-enum: 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: vite — vite: abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×2
Duplicated block with local edits (26 matched lines × 2 locations) packages/vite/src/node/server/pluginContainer.ts:481— packages/vite/src/node/server/pluginContainer.ts:481 · packages/vite/src/node/server/pluginContainer.ts:548 — the two spans are one implementation copied and then locally edited — 104 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 with local edits (26 matched lines × 2 locations) REDACTED:3— REDACTED:3 · REDACTED:1 — the two spans are one implementation copied and then locally edited — 135 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 (22 lines × 2 locations) REDACTED:16— REDACTED:16 · REDACTED:17 — 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 (22 lines × 2 locations) playground/fs-serve/root/vite.config-base.js:16— playground/fs-serve/root/vite.config-base.js:16 · playground/fs-serve/root/vite.config.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (17 lines × 2 locations) packages/vite/src/node/build.ts:1413— packages/vite/src/node/build.ts:1413 · packages/vite/src/node/build.ts:1436 — 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 (17 lines × 2 locations) playground/optimize-deps/dep-lodash-clonedeep/index.js:4— playground/optimize-deps/dep-lodash-clonedeep/index.js:4 · playground/optimize-deps/dep-lodash/cloneDeep.js:4 — 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 (15 matched lines × 2 locations) · ×2
Duplicated block with local edits (15 matched lines × 2 locations) REDACTED:427— REDACTED:427 · REDACTED:458 — the two spans are one implementation copied and then locally edited — 77 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 with local edits (15 matched lines × 2 locations) packages/vite/src/shared/bundledDevHmr.ts:335— packages/vite/src/shared/bundledDevHmr.ts:335 · packages/vite/src/shared/bundledDevHmr.ts:380 — the two spans are one implementation copied and then locally edited — 84 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.
Low contrast colour pair in CSS (1.0:1) playground/css/treeshake-scoped/order/a-scoped.css:1— `.treeshake-scoped-order` sets color: red on background-color: red — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) playground/css/treeshake-scoped/order/after.css:1— `.treeshake-scoped-order` sets color: red on background-color: blue — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
importAnalysis.importAnalysisPlugin.transform (cyclomatic 131) REDACTED:224— importAnalysis.importAnalysisPlugin.transform has cyclomatic complexity 131 (threshold 15). Of this number, 41 points are the body's own statements and 90 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.viteLegacyPlugin (cyclomatic 103) packages/plugin-legacy/src/index.ts:207— index.viteLegacyPlugin has cyclomatic complexity 103 (threshold 15). Of this number, 96 points are the body's own statements and 7 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.
config.resolveConfig (cyclomatic 103) REDACTED:1480— config.resolveConfig has cyclomatic complexity 103 (threshold 15). Of this number, 95 points are the body's own statements and 8 belong to 5 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.
importAnalysisBuild.buildImportAnalysisPlugin (cyclomatic 88) packages/vite/src/node/plugins/importAnalysisBuild.ts:417— importAnalysisBuild.buildImportAnalysisPlugin has cyclomatic complexity 88 (threshold 15). Of this number, 74 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index._createServer (cyclomatic 72) packages/vite/src/node/server/index.ts:512— index._createServer has cyclomatic complexity 72 (threshold 15). Of this number, 48 points are the body's own statements and 24 belong to 13 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.
ssrTransform.ssrTransformScript (cyclomatic 68) packages/vite/src/node/ssr/ssrTransform.ts:59— ssrTransform.ssrTransformScript has cyclomatic complexity 68 (threshold 15). Of this number, 64 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
css.cssPostPlugin (cyclomatic 68) REDACTED:527— css.cssPostPlugin has cyclomatic complexity 68 (threshold 15). Of this number, 61 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.init (cyclomatic 59) packages/create-vite/src/index.ts:468— index.init has cyclomatic complexity 59 (threshold 15). Of this number, 53 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
html.buildHtmlPlugin (cyclomatic 59) packages/vite/src/node/plugins/html.ts:438— html.buildHtmlPlugin has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 13 of the 59 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 562, processAssetUrl, nodeStartWithLeadingWhitespace, …). 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.
resolve.tryNodeResolve (cyclomatic 49) REDACTED:722— resolve.tryNodeResolve has cyclomatic complexity 49 (threshold 15). Of this number, 43 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
transformRequest.loadAndTransform (cyclomatic 47) packages/vite/src/node/server/transformRequest.ts:237— transformRequest.loadAndTransform has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ssrTransform.walk (cyclomatic 44) packages/vite/src/node/ssr/ssrTransform.ts:476— ssrTransform.walk has cyclomatic complexity 44 (threshold 15). Of this number, 33 points are the body's own statements and 11 belong to 5 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.
utils.mergeConfigRecursively (cyclomatic 43) REDACTED:1448— utils.mergeConfigRecursively has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
transform.transformMiddleware (cyclomatic 40) packages/vite/src/node/server/middlewares/transform.ts:130— transform.transformMiddleware has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 140, warnAboutExplicitPublicPathInUrl). 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.
css.compileLightningCSS (cyclomatic 39) REDACTED:3380— css.compileLightningCSS has cyclomatic complexity 39 (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.
rolldownDepPlugin.rolldownDepPlugin (cyclomatic 39) REDACTED:61— rolldownDepPlugin.rolldownDepPlugin has cyclomatic complexity 39 (threshold 15). Of this number, 28 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hmr.handleHMRUpdate (cyclomatic 38) packages/vite/src/node/server/hmr.ts:411— hmr.handleHMRUpdate has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 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.
ws.createWebSocketServer (cyclomatic 38) REDACTED:118— ws.createWebSocketServer has cyclomatic complexity 38 (threshold 15). Of this number, 19 points are the body's own statements and 19 belong to 10 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
importMetaGlob.transformGlobImport (cyclomatic 38) packages/vite/src/node/plugins/importMetaGlob.ts:418— importMetaGlob.transformGlobImport has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 5 of the 38 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 478, 521, 446). 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.
PluginContext._formatLog (cyclomatic 33) packages/vite/src/node/server/pluginContainer.ts:936— PluginContext._formatLog has cyclomatic complexity 33 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
esbuild.transformWithEsbuild (cyclomatic 33) packages/vite/src/node/plugins/esbuild.ts:97— esbuild.transformWithEsbuild has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
css.cssPostPlugin.generateBundle (cyclomatic 33) REDACTED:1058— css.cssPostPlugin.generateBundle has cyclomatic complexity 33 (threshold 15). Of this number, 25 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scan.rolldownScanPlugin::htmlTypeOnLoadCallback (cyclomatic 33) packages/vite/src/node/optimizer/scan.ts:456— scan.rolldownScanPlugin::htmlTypeOnLoadCallback 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. This shape REPEATS in the file: one other method here (scan.rolldownScanPlugin) 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.
html.buildHtmlPlugin.generateBundle (cyclomatic 32) packages/vite/src/node/plugins/html.ts:847— html.buildHtmlPlugin.generateBundle has cyclomatic complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolve.oxcResolvePlugin (cyclomatic 31) REDACTED:221— resolve.oxcResolvePlugin has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 233, 299, 241, …). 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.
scan.rolldownScanPlugin (cyclomatic 30) packages/vite/src/node/optimizer/scan.ts:366— scan.rolldownScanPlugin 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. This shape REPEATS in the file: one other method here (scan.rolldownScanPlugin::htmlTypeOnLoadCallback) 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.
build.resolveRolldownOptions::buildOutputOptions (cyclomatic 30) packages/vite/src/node/build.ts:713— build.resolveRolldownOptions::buildOutputOptions has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (build.resolveRolldownOptions) 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.
client.handleMessage (cyclomatic 28) REDACTED:201— client.handleMessage has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 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.
ssrTransform.isRefIdentifier (cyclomatic 28) packages/vite/src/node/ssr/ssrTransform.ts:630— ssrTransform.isRefIdentifier has cyclomatic complexity 28 (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.
asset.assetPlugin (cyclomatic 28) packages/vite/src/node/plugins/asset.ts:190— asset.assetPlugin has cyclomatic complexity 28 (threshold 15). Of this number, 27 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.
importMetaGlob.parseGlobOptions (cyclomatic 28) packages/vite/src/node/plugins/importMetaGlob.ts:153— importMetaGlob.parseGlobOptions 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.
worker.webWorkerPlugin (cyclomatic 26) REDACTED:679— worker.webWorkerPlugin 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.
preview.preview (cyclomatic 26) packages/vite/src/node/preview.ts:131— preview.preview has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to 3 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.
resolve.tryCleanFsResolve (cyclomatic 25) REDACTED:613— resolve.tryCleanFsResolve 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.
css.compilePostCSS (cyclomatic 25) REDACTED:1640— css.compilePostCSS 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.
config.resolveDepOptimizationOptions (cyclomatic 25) REDACTED:1286— config.resolveDepOptimizationOptions has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 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.
interceptor.CallSiteToString (cyclomatic 24) packages/vite/src/module-runner/sourcemap/interceptor.ts:276— interceptor.CallSiteToString 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.
manifest.manifestPlugin (cyclomatic 24) packages/vite/src/node/plugins/manifest.ts:70— manifest.manifestPlugin 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 82, 172). 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.
importAnalysisBuild.preload (cyclomatic 24) packages/vite/src/node/plugins/importAnalysisBuild.ts:244— importAnalysisBuild.preload has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 294, a function literal at line 371, importMetaResolve, …). 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.
EnvironmentPluginContainer.resolveId (cyclomatic 24) packages/vite/src/node/server/pluginContainer.ts:351— EnvironmentPluginContainer.resolveId has cyclomatic complexity 24 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
build.resolveRolldownOptions (cyclomatic 24) packages/vite/src/node/build.ts:600— build.resolveRolldownOptions has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (build.resolveRolldownOptions::buildOutputOptions) 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.
hmr.lexAcceptedHmrDeps (cyclomatic 23) packages/vite/src/node/server/hmr.ts:1009— hmr.lexAcceptedHmrDeps 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.
indexHtml.indexHtmlMiddleware.viteIndexHtmlMiddleware (cyclomatic 23) REDACTED:438— indexHtml.indexHtmlMiddleware.viteIndexHtmlMiddleware 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.
config.bundleConfigFile (cyclomatic 23) REDACTED:2576— config.bundleConfigFile has cyclomatic complexity 23 (threshold 15). Of this number, 22 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.
rollupLicensePlugin.licensePlugin (cyclomatic 22) packages/vite/rollupLicensePlugin.ts:7— rollupLicensePlugin.licensePlugin has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
preAlias.preAliasPlugin.resolveId (cyclomatic 22) packages/vite/src/node/plugins/preAlias.ts:34— preAlias.preAliasPlugin.resolveId 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.
build.createBuilder (cyclomatic 22) packages/vite/src/node/build.ts:1850— build.createBuilder has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
worker.bundleWorkerEntry (cyclomatic 21) REDACTED:401— worker.bundleWorkerEntry has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BundledDev.listen (cyclomatic 21) packages/vite/src/node/server/bundledDev.ts:132— BundledDev.listen has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 203, 241, 287, …). 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.
css.cssPlugin (cyclomatic 21) REDACTED:351— css.cssPlugin has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (urlResolver). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
asset.assetPlugin.generateBundle (cyclomatic 21) packages/vite/src/node/plugins/asset.ts:371— asset.assetPlugin.generateBundle has cyclomatic complexity 21 (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.
commandLock.isCommandLockRecord (cyclomatic 21) packages/vite/src/node/commandLock.ts:40— commandLock.isCommandLockRecord has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
importAnalysis.transformCjsImport (cyclomatic 20) REDACTED:1055— importAnalysis.transformCjsImport has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
assetImportMetaUrl.assetImportMetaUrlPlugin (cyclomatic 20) packages/vite/src/node/plugins/assetImportMetaUrl.ts:37— assetImportMetaUrl.assetImportMetaUrlPlugin 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.
resolve.optimizerResolvePlugin (cyclomatic 19) REDACTED:392— resolve.optimizerResolvePlugin 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.
resolve.resolvePackageEntry (cyclomatic 19) REDACTED:938— resolve.resolvePackageEntry 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.
wasm.wasmHelperPlugin (cyclomatic 19) packages/vite/src/node/plugins/wasm.ts:108— wasm.wasmHelperPlugin has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 109). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
fetchModule.fetchModule (cyclomatic 19) packages/vite/src/node/ssr/fetchModule.ts:33— fetchModule.fetchModule has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
fetchModule.fetchBundledModule (cyclomatic 19) packages/vite/src/node/ssr/fetchModule.ts:139— fetchModule.fetchBundledModule 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.
build.resolveBuildEnvironmentOptions (cyclomatic 19) packages/vite/src/node/build.ts:432— build.resolveBuildEnvironmentOptions has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils.generateCodeFrame (cyclomatic 19) REDACTED:536— utils.generateCodeFrame 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.
index.getFullCustomCommand (cyclomatic 18) packages/create-vite/src/index.ts:1173— index.getFullCustomCommand has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1208, 1179, 1207). 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.
forwardConsole.formatConsoleArgs.message (cyclomatic 18) packages/vite/src/shared/forwardConsole.ts:130— forwardConsole.formatConsoleArgs.message 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.
proxy.proxyMiddleware (cyclomatic 18) REDACTED:91— proxy.proxyMiddleware has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 162, 99, 113). 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.
transformRequest.handleModuleSoftInvalidation (cyclomatic 18) packages/vite/src/node/server/transformRequest.ts:450— transformRequest.handleModuleSoftInvalidation 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.
worker.webWorkerPlugin.generateBundle (cyclomatic 18) REDACTED:880— worker.webWorkerPlugin.generateBundle 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.
forwardConsole.formatError (cyclomatic 18) packages/vite/src/node/plugins/forwardConsole.ts:79— forwardConsole.formatError has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, 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.
workerImportMetaUrl.workerImportMetaUrlPlugin (cyclomatic 18) packages/vite/src/node/plugins/workerImportMetaUrl.ts:193— workerImportMetaUrl.workerImportMetaUrlPlugin 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.
htmlSafeModulePaths.addHtmlRequestToSafeModulePaths (cyclomatic 18) REDACTED:73— htmlSafeModulePaths.addHtmlRequestToSafeModulePaths 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.
oxc.transformWithOxc (cyclomatic 18) packages/vite/src/node/plugins/oxc.ts:120— oxc.transformWithOxc 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.
optimizer.createDepsOptimizer::runOptimizer (cyclomatic 18) packages/vite/src/node/optimizer/optimizer.ts:324— optimizer.createDepsOptimizer::runOptimizer 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.
logger.createLogger (cyclomatic 18) packages/vite/src/node/logger.ts:68— logger.createLogger has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (output, format). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
nativeConfigCompat.analyzeConfigModuleReferences (cyclomatic 18) packages/vite/src/node/nativeConfigCompat.ts:140— nativeConfigCompat.analyzeConfigModuleReferences has cyclomatic complexity 18 (threshold 15). Of this number, 15 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.
pluginConverter.createResolveIdHandler.<returned closure> (cyclomatic 18) packages/vite/src/node/optimizer/pluginConverter.ts:202— pluginConverter.createResolveIdHandler.<returned closure> has cyclomatic complexity 18 (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.
interceptor.mapSourcePosition (cyclomatic 17) packages/vite/src/module-runner/sourcemap/interceptor.ts:174— interceptor.mapSourcePosition has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hmr.updateModules (cyclomatic 17) packages/vite/src/node/server/hmr.ts:683— hmr.updateModules has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
optimizedDeps.optimizedDepsPlugin.load (cyclomatic 17) REDACTED:42— optimizedDeps.optimizedDepsPlugin.load has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolve.expandGlobIds (cyclomatic 17) REDACTED:46— resolve.expandGlobIds has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DevEnvironment.constructor (cyclomatic 17) packages/vite/src/node/server/environment.ts:116— DevEnvironment.constructor has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
importMetaGlob.parseImportGlob (cyclomatic 17) packages/vite/src/node/plugins/importMetaGlob.ts:251— importMetaGlob.parseImportGlob 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 2 function literals inside it that branch (lines 267, 303). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
build.onRollupLog (cyclomatic 17) packages/vite/src/node/build.ts:1130— build.onRollupLog has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function item inside it that branches (viteLog). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
utils.resolveServerUrls (cyclomatic 17) REDACTED:1078— utils.resolveServerUrls has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vitestSetupUtils.setupTest (cyclomatic 17) playground/vitestSetupUtils.ts:121— vitestSetupUtils.setupTest has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BundledDevHMRClient.bubble (cyclomatic 16) packages/vite/src/shared/bundledDevHmr.ts:153— BundledDevHMRClient.bubble 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.
forwardConsole.setupForwardConsoleHandler (cyclomatic 16) packages/vite/src/shared/forwardConsole.ts:27— forwardConsole.setupForwardConsoleHandler has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (sendLog, a function literal at line 89, sendError, …). 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.
interceptor.wrapCallSite (cyclomatic 16) packages/vite/src/module-runner/sourcemap/interceptor.ts:366— interceptor.wrapCallSite has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
send.send (cyclomatic 16) packages/vite/src/node/server/send.ts:32— send.send has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
hmr.propagateUpdate (cyclomatic 16) packages/vite/src/node/server/hmr.ts:808— hmr.propagateUpdate 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.
EnvironmentPluginContainer.transform (cyclomatic 16) packages/vite/src/node/server/pluginContainer.ts:528— EnvironmentPluginContainer.transform has cyclomatic complexity 16 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
css.convertTargets (cyclomatic 16) REDACTED:3714— css.convertTargets has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
indexHtml.devHtmlHook::processNodeUrl::replacer (cyclomatic 16) REDACTED:188— indexHtml.devHtmlHook::processNodeUrl::replacer 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.
html.applyHtmlTransforms (cyclomatic 16) packages/vite/src/node/plugins/html.ts:1496— html.applyHtmlTransforms 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.
env.loadEnv (cyclomatic 16) packages/vite/src/node/env.ts:33— env.loadEnv has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: 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.
pluginConverter.createLoadHandler.<returned closure> (cyclomatic 16) packages/vite/src/node/optimizer/pluginConverter.ts:258— pluginConverter.createLoadHandler.<returned closure> has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: playground/base-conflict playground/base-conflict/__tests__/base-conflict.spec.ts:4— No conventional assertion call was detected in 1 of 1 tests in `playground/base-conflict` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
HackComment REDACTED:931— // hack for parse broken with normalized absolute paths on windows (C:/path/to/something). — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
FixmeComment packages/vite/src/node/server/pluginContainer.ts:693— // FIXME: properly support this later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment REDACTED:1162— // `filename`s (rendered chunk has the !~{XXX}~ placeholder) — 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.
importAnalysisBuild.buildImportAnalysisPlugin (cognitive 246) packages/vite/src/node/plugins/importAnalysisBuild.ts:417— importAnalysisBuild.buildImportAnalysisPlugin has cognitive complexity 246 (threshold 15). Drivers by points: if/else 44 (142 pts), ternaries 10 (50 pts), loops 7 (26 pts), boolean chains 20, error handling 2 (8 pts) (nesting depth added 163). Of this number, 233 points are the body's own statements and 13 belong to 7 function items inside it that branch. 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.
css.cssPostPlugin (cognitive 138) REDACTED:527— css.cssPostPlugin has cognitive complexity 138 (threshold 15). Drivers by points: if/else 38 (90 pts), boolean chains 21, ternaries 7 (16 pts), loops 4 (11 pts) (nesting depth added 68). Of this number, 125 points are the body's own statements and 13 belong to 3 function items inside it that branch. 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.
ssrTransform.ssrTransformScript (cognitive 136) packages/vite/src/node/ssr/ssrTransform.ts:59— ssrTransform.ssrTransformScript has cognitive complexity 136 (threshold 15). Drivers by points: if/else 49 (90 pts), loops 9 (27 pts), boolean chains 12, ternaries 3 (6 pts), error handling 1 (nesting depth added 62). Of this number, 130 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.viteLegacyPlugin (cognitive 128) packages/plugin-legacy/src/index.ts:207— index.viteLegacyPlugin has cognitive complexity 128 (threshold 15). Drivers by points: if/else 70 (87 pts), boolean chains 21, loops 5 (10 pts), ternaries 6 (10 pts) (nesting depth added 26). Of this number, 115 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.init (cognitive 101) packages/create-vite/src/index.ts:468— index.init has cognitive complexity 101 (threshold 15). Drivers by points: if/else 46 (75 pts), ternaries 6 (13 pts), boolean chains 10, match/switch 1 (2 pts), loops 1 (nesting depth added 37). Of this number, 90 points are the body's own statements and 11 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.
config.resolveConfig (cognitive 101) REDACTED:1480— config.resolveConfig has cognitive complexity 101 (threshold 15). Drivers by points: if/else 46 (53 pts), boolean chains 33, ternaries 8 (10 pts), loops 3, error handling 1 (2 pts) (nesting depth added 10). Of this number, 95 points are the body's own statements and 6 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
html.buildHtmlPlugin (cognitive 98) packages/vite/src/node/plugins/html.ts:438— html.buildHtmlPlugin has cognitive complexity 98 (threshold 15). Drivers by points: if/else 37 (74 pts), boolean chains 13, ternaries 2 (5 pts), error handling 2 (3 pts), loops 3 (nesting depth added 41). Most of this is not in the body itself: 14 of the 98 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 562, processAssetUrl, a function literal at line 661, …). 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.
transform.transformMiddleware (cognitive 81) packages/vite/src/node/server/middlewares/transform.ts:130— transform.transformMiddleware has cognitive complexity 81 (threshold 15). Drivers by points: if/else 31 (64 pts), boolean chains 6, ternaries 2 (6 pts), error handling 3 (5 pts) (nesting depth added 39). None of this is in the body itself: all 81 points belong to 2 function items inside it that branch (a function literal at line 140, warnAboutExplicitPublicPathInUrl). 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.
transformRequest.loadAndTransform (cognitive 76) packages/vite/src/node/server/transformRequest.ts:237— transformRequest.loadAndTransform has cognitive complexity 76 (threshold 15). Drivers by points: if/else 27 (48 pts), boolean chains 11, ternaries 6 (8 pts), error handling 2 (6 pts), loops 1 (3 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hmr.handleHMRUpdate (cognitive 70) packages/vite/src/node/server/hmr.ts:411— hmr.handleHMRUpdate has cognitive complexity 70 (threshold 15). Drivers by points: if/else 23 (49 pts), loops 5 (8 pts), error handling 4 (6 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 33). Of this number, 59 points are the body's own statements and 11 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.
manifest.manifestPlugin (cognitive 68) packages/vite/src/node/plugins/manifest.ts:70— manifest.manifestPlugin has cognitive complexity 68 (threshold 15). Drivers by points: if/else 17 (52 pts), ternaries 3 (7 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 43). None of this is in the body itself: all 68 points belong to 2 function literals inside it that branch (lines 82, 172). 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.
esbuild.transformWithEsbuild (cognitive 65) packages/vite/src/node/plugins/esbuild.ts:97— esbuild.transformWithEsbuild has cognitive complexity 65 (threshold 15). Drivers by points: if/else 20 (44 pts), loops 2 (9 pts), boolean chains 8, error handling 2, ternaries 1 (2 pts) (nesting depth added 32). Of this number, 61 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
resolve.expandGlobIds (cognitive 64) REDACTED:46— resolve.expandGlobIds has cognitive complexity 64 (threshold 15). Drivers by points: if/else 15 (54 pts), loops 2 (9 pts), boolean chains 1 (nesting depth added 46). Of this number, 27 points are the body's own statements and 37 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
importAnalysis.importAnalysisPlugin.transform (cognitive 60) REDACTED:224— importAnalysis.importAnalysisPlugin.transform has cognitive complexity 60 (threshold 15). Drivers by points: if/else 69 (128 pts), ternaries 19 (48 pts), boolean chains 32, loops 3 (6 pts), error handling 2 (nesting depth added 91). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (importAnalysis.importAnalysisPlugin.transform::resolveId) 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.
PluginContext._formatLog (cognitive 60) packages/vite/src/node/server/pluginContainer.ts:936— PluginContext._formatLog has cognitive complexity 60 (threshold 15). Drivers by points: if/else 17 (37 pts), error handling 3 (13 pts), boolean chains 9, ternaries 1 (nesting depth added 30). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
resolve.tryCleanFsResolve (cognitive 57) REDACTED:613— resolve.tryCleanFsResolve has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (50 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 34). 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.
hmr.lexAcceptedHmrDeps (cognitive 57) packages/vite/src/node/server/hmr.ts:1009— hmr.lexAcceptedHmrDeps has cognitive complexity 57 (threshold 15). Drivers by points: if/else 25 (53 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.mergeConfigRecursively (cognitive 57) REDACTED:1448— utils.mergeConfigRecursively has cognitive complexity 57 (threshold 15). Drivers by points: if/else 19 (31 pts), boolean chains 19, loops 3 (7 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index._createServer (cognitive 56) packages/vite/src/node/server/index.ts:512— index._createServer has cognitive complexity 56 (threshold 15). Drivers by points: if/else 41 (49 pts), ternaries 13 (21 pts), boolean chains 13, loops 3 (4 pts) (nesting depth added 17). 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. This shape REPEATS in the file: one other method here (index._createServer::onFileAddUnlink) 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.
css.cssPostPlugin.generateBundle (cognitive 55) REDACTED:1058— css.cssPostPlugin.generateBundle has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 5 (9 pts), boolean chains 6, ternaries 2 (5 pts) (nesting depth added 26). Of this number, 43 points are the body's own statements and 12 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.
ssrTransform.walk (cognitive 53) packages/vite/src/node/ssr/ssrTransform.ts:476— ssrTransform.walk has cognitive complexity 53 (threshold 15). Drivers by points: if/else 34 (43 pts), boolean chains 10 (nesting depth added 9). Of this number, 38 points are the body's own statements and 15 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
utils.generateCodeFrame (cognitive 53) REDACTED:536— utils.generateCodeFrame has cognitive complexity 53 (threshold 15). Drivers by points: if/else 9 (32 pts), ternaries 4 (15 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 36). 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.
worker.webWorkerPlugin (cognitive 51) REDACTED:679— worker.webWorkerPlugin has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (26 pts), ternaries 7 (16 pts), loops 2 (6 pts), boolean chains 3 (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.
rollupLicensePlugin.licensePlugin (cognitive 50) packages/vite/rollupLicensePlugin.ts:7— rollupLicensePlugin.licensePlugin has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (39 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
indexHtml.indexHtmlMiddleware.viteIndexHtmlMiddleware (cognitive 50) REDACTED:438— indexHtml.indexHtmlMiddleware.viteIndexHtmlMiddleware has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (33 pts), error handling 2 (6 pts), ternaries 2 (6 pts), boolean chains 5 (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.
html.buildHtmlPlugin.generateBundle (cognitive 50) packages/vite/src/node/plugins/html.ts:847— html.buildHtmlPlugin.generateBundle has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (31 pts), boolean chains 8, ternaries 3 (7 pts), loops 3 (4 pts) (nesting depth added 21). Of this number, 39 points are the body's own statements and 11 belong to 6 function items inside it that branch. 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.
ws.createWebSocketServer (cognitive 49) REDACTED:118— ws.createWebSocketServer has cognitive complexity 49 (threshold 15). Drivers by points: if/else 25 (33 pts), boolean chains 13, ternaries 2, error handling 1 (nesting depth added 8). Of this number, 22 points are the body's own statements and 27 belong to 10 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.
rolldownDepPlugin.rolldownDepPlugin (cognitive 49) REDACTED:61— rolldownDepPlugin.rolldownDepPlugin has cognitive complexity 49 (threshold 15). Drivers by points: if/else 27 (36 pts), ternaries 5 (7 pts), boolean chains 5, loops 1 (nesting depth added 11). Of this number, 38 points are the body's own statements and 11 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.
importMetaGlob.transformGlobImport (cognitive 48) packages/vite/src/node/plugins/importMetaGlob.ts:418— importMetaGlob.transformGlobImport has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (25 pts), ternaries 10 (15 pts), boolean chains 8 (nesting depth added 10). Most of this is not in the body itself: 4 of the 48 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 478, 521, 446). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
proxy.proxyMiddleware (cognitive 47) REDACTED:91— proxy.proxyMiddleware has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (37 pts), error handling 1 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 30). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 162, 113, 99). 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.
scan.rolldownScanPlugin (cognitive 47) packages/vite/src/node/optimizer/scan.ts:366— scan.rolldownScanPlugin has cognitive complexity 47 (threshold 15). Drivers by points: if/else 40 (74 pts), boolean chains 21, ternaries 2 (3 pts), loops 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (scan.rolldownScanPlugin::htmlTypeOnLoadCallback) 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.
ssrManifestPlugin.ssrManifestPlugin.generateBundle (cognitive 46) packages/vite/src/node/ssr/ssrManifestPlugin.ts:32— ssrManifestPlugin.ssrManifestPlugin.generateBundle has cognitive complexity 46 (threshold 15). Drivers by points: if/else 7 (31 pts), loops 3 (9 pts), error handling 1 (4 pts), boolean chains 1, ternaries 1 (nesting depth added 33). Of this number, 28 points are the body's own statements and 18 belong to 2 function items inside it that branch. 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.createBuilder (cognitive 46) packages/vite/src/node/build.ts:1850— build.createBuilder has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 5 (15 pts), boolean chains 3, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 25). Of this number, 21 points are the body's own statements and 25 belong to 2 function items inside it that branch. 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.
resolve.tryNodeResolve (cognitive 45) REDACTED:722— resolve.tryNodeResolve has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (26 pts), boolean chains 16, ternaries 3 (nesting depth added 8). Of this number, 39 points are the body's own statements and 6 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.
assetImportMetaUrl.assetImportMetaUrlPlugin (cognitive 43) packages/vite/src/node/plugins/assetImportMetaUrl.ts:37— assetImportMetaUrl.assetImportMetaUrlPlugin has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (31 pts), ternaries 2 (6 pts), error handling 1 (3 pts), boolean chains 2, 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.
transformRequest.handleModuleSoftInvalidation (cognitive 42) packages/vite/src/node/server/transformRequest.ts:450— transformRequest.handleModuleSoftInvalidation has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (23 pts), ternaries 2 (10 pts), loops 2 (5 pts), boolean chains 4 (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.
workerImportMetaUrl.workerImportMetaUrlPlugin (cognitive 42) packages/vite/src/node/plugins/workerImportMetaUrl.ts:193— workerImportMetaUrl.workerImportMetaUrlPlugin has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (33 pts), loops 2 (5 pts), boolean chains 2, ternaries 1 (2 pts) (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.
scan.rolldownScanPlugin::htmlTypeOnLoadCallback (cognitive 42) packages/vite/src/node/optimizer/scan.ts:456— scan.rolldownScanPlugin::htmlTypeOnLoadCallback has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 12, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (scan.rolldownScanPlugin) 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.
importAnalysis.transformCjsImport (cognitive 41) REDACTED:1055— importAnalysis.transformCjsImport has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (27 pts), ternaries 2 (10 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 20). Of this number, 33 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
asset.assetPlugin (cognitive 40) packages/vite/src/node/plugins/asset.ts:190— asset.assetPlugin has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (20 pts), ternaries 7 (11 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 12). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
asset.assetPlugin.generateBundle (cognitive 40) packages/vite/src/node/plugins/asset.ts:371— asset.assetPlugin.generateBundle has cognitive complexity 40 (threshold 15). Drivers by points: loops 5 (19 pts), if/else 6 (17 pts), boolean chains 4 (nesting depth added 25). 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.
client.handleMessage (cognitive 38) REDACTED:201— client.handleMessage has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 6, ternaries 1 (2 pts), match/switch 1 (nesting depth added 17). Of this number, 31 points are the body's own statements and 7 belong to 2 function literals inside it that branch. 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.
interceptor.CallSiteToString (cognitive 38) packages/vite/src/module-runner/sourcemap/interceptor.ts:276— interceptor.CallSiteToString has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 6 (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.
css.compileLightningCSS (cognitive 37) REDACTED:3380— css.compileLightningCSS has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 6 (13 pts), error handling 2 (4 pts), boolean chains 2, match/switch 1 (2 pts), ternaries 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.
utils.resolveServerUrls (cognitive 37) REDACTED:1078— utils.resolveServerUrls has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 2 (9 pts), boolean chains 3, ternaries 2 (nesting depth added 18). Of this number, 31 points are the body's own statements and 6 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.
EnvironmentPluginContainer.transform (cognitive 34) packages/vite/src/node/server/pluginContainer.ts:528— EnvironmentPluginContainer.transform has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (26 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 18). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
importMetaGlob.parseGlobOptions (cognitive 33) packages/vite/src/node/plugins/importMetaGlob.ts:153— importMetaGlob.parseGlobOptions has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 7, loops 2 (3 pts), ternaries 1 (2 pts), error handling 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.
config.resolveDepOptimizationOptions (cognitive 33) REDACTED:1286— config.resolveDepOptimizationOptions has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 9, loops 1 (3 pts) (nesting depth added 13). Of this number, 30 points are the body's own statements and 3 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.
resolve.optimizerResolvePlugin (cognitive 32) REDACTED:392— resolve.optimizerResolvePlugin has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 6, ternaries 2 (4 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.
optimizedDeps.optimizedDepsPlugin.load (cognitive 32) REDACTED:42— optimizedDeps.optimizedDepsPlugin.load has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (21 pts), error handling 2 (5 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EnvironmentPluginContainer.resolveId (cognitive 32) packages/vite/src/node/server/pluginContainer.ts:351— EnvironmentPluginContainer.resolveId has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 6, ternaries 2 (3 pts), loops 2 (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
html.applyHtmlTransforms (cognitive 32) packages/vite/src/node/plugins/html.ts:1496— html.applyHtmlTransforms has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (4 pts), match/switch 1 (4 pts), boolean chains 3 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.resolvePackageEntry (cognitive 31) REDACTED:938— resolve.resolvePackageEntry has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (3 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.resolveRolldownOptions::buildOutputOptions (cognitive 31) packages/vite/src/node/build.ts:713— build.resolveRolldownOptions::buildOutputOptions has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 12, if/else 3 (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. This shape REPEATS in the file: one other method here (build.resolveRolldownOptions) 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.
vitestSetupUtils.startDefaultServe (cognitive 31) playground/vitestSetupUtils.ts:286— vitestSetupUtils.startDefaultServe has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (27 pts), boolean chains 4 (nesting depth added 16). Of this number, 20 points are the body's own statements and 11 belong to 2 function literals inside it that branch. 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.
resolve.oxcResolvePlugin (cognitive 29) REDACTED:221— resolve.oxcResolvePlugin has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 10, if/else 5 (8 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 233, 299, 241, …). 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.
worker.webWorkerPlugin.generateBundle (cognitive 29) REDACTED:880— worker.webWorkerPlugin.generateBundle has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 3 (5 pts), boolean chains 3, loops 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.
config.bundleConfigFile (cognitive 29) REDACTED:2576— config.bundleConfigFile has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (nesting depth added 8). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.httpServerStart (cognitive 28) packages/vite/src/node/http.ts:249— http.httpServerStart has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
css.compilePostCSS (cognitive 28) REDACTED:1640— css.compilePostCSS has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 7, loops 1 (2 pts), ternaries 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.
css.convertTargets (cognitive 28) REDACTED:3714— css.convertTargets has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 13). Of this number, 25 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.
preview.preview (cognitive 28) packages/vite/src/node/preview.ts:131— preview.preview has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 6, ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 5). Of this number, 24 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
build.resolveRolldownOptions (cognitive 28) packages/vite/src/node/build.ts:600— build.resolveRolldownOptions has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 22 (32 pts), boolean chains 17, if/else 9 (10 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. This shape REPEATS in the file: one other method here (build.resolveRolldownOptions::buildOutputOptions) 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.
proxy.proxyMiddleware.viteProxyMiddleware (cognitive 27) REDACTED:210— proxy.proxyMiddleware.viteProxyMiddleware has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (21 pts), error handling 1 (4 pts), boolean chains 1, loops 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.
ssrTransform.isRefIdentifier (cognitive 27) packages/vite/src/node/ssr/ssrTransform.ts:630— ssrTransform.isRefIdentifier has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 11 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
utils.emptyDir (cognitive 27) REDACTED:637— utils.emptyDir has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2 (3 pts) (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.
packages.resolvePackageData (cognitive 25) packages/vite/src/node/packages.ts:63— packages.resolvePackageData has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 2 (4 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasm.wasmHelperPlugin (cognitive 25) packages/vite/src/node/plugins/wasm.ts:108— wasm.wasmHelperPlugin has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, ternaries 2 (3 pts), error handling 1, loops 1 (nesting depth added 6). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 109). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
fetchModule.fetchBundledModule (cognitive 25) packages/vite/src/node/ssr/fetchModule.ts:139— fetchModule.fetchBundledModule has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 5 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
commandLock.scanCommandLocks (cognitive 25) packages/vite/src/node/commandLock.ts:94— commandLock.scanCommandLocks has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (5 pts), error handling 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forwardConsole.setupForwardConsoleHandler (cognitive 24) packages/vite/src/shared/forwardConsole.ts:27— forwardConsole.setupForwardConsoleHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 4 (7 pts), boolean chains 3, loops 1 (nesting depth added 10). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (sendLog, a function literal at line 89, a function literal at line 105, …). 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.
interceptor.mapSourcePosition (cognitive 24) packages/vite/src/module-runner/sourcemap/interceptor.ts:174— interceptor.mapSourcePosition has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 5 (nesting depth added 9). Of this number, 19 points are the body's own statements and 5 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.
WorkerOutputCache.getLiveAssetFileNames (cognitive 24) REDACTED:203— WorkerOutputCache.getLiveAssetFileNames has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (9 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.
index.addManuallyIncludedOptimizeDeps (cognitive 24) packages/vite/src/node/optimizer/index.ts:881— index.addManuallyIncludedOptimizeDeps has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (4 pts) (nesting depth added 14). Of this number, 22 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
license.licensePlugin.generateBundle (cognitive 24) packages/vite/src/node/plugins/license.ts:48— license.licensePlugin.generateBundle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (3 pts), boolean chains 1, ternaries 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.
sourcemap.applySourcemapIgnoreList (cognitive 23) packages/vite/src/node/server/sourcemap.ts:167— sourcemap.applySourcemapIgnoreList has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
oxc.transformWithOxc (cognitive 23) packages/vite/src/node/plugins/oxc.ts:120— oxc.transformWithOxc has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (5 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.resolveBuildOutputs (cognitive 23) packages/vite/src/node/build.ts:1060— build.resolveBuildOutputs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 5 (nesting depth added 11). Of this number, 19 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
nativeConfigCompat.analyzeConfigModuleReferences (cognitive 23) packages/vite/src/node/nativeConfigCompat.ts:140— nativeConfigCompat.analyzeConfigModuleReferences has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (4 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (nesting depth added 9). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lightningcss-plugins.nestedLikePlugin (cognitive 23) playground/css/lightningcss-plugins.js:115— lightningcss-plugins.nestedLikePlugin has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 1 (2 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.
vitestSetupUtils.setupTest (cognitive 23) playground/vitestSetupUtils.ts:121— vitestSetupUtils.setupTest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3, error handling 1 (nesting depth added 8). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nestedLikePlugin::style (cognitive 23) playground/css/lightningcss-plugins.js:118— nestedLikePlugin::style has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 1 (2 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.
preAlias.preAliasPlugin.resolveId (cognitive 22) packages/vite/src/node/plugins/preAlias.ts:34— preAlias.preAliasPlugin.resolveId has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 6 (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.
css.cssPlugin::urlResolver (cognitive 22) REDACTED:431— css.cssPlugin::urlResolver has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 2 (3 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.
importMetaGlob.parseImportGlob (cognitive 22) packages/vite/src/node/plugins/importMetaGlob.ts:251— importMetaGlob.parseImportGlob has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 267, 303). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
config.loadConfigFromBundledFile (cognitive 22) REDACTED:2783— config.loadConfigFromBundledFile has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5 (9 pts), error handling 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.
BundledDevHMRClient.bubble (cognitive 21) packages/vite/src/shared/bundledDevHmr.ts:153— BundledDevHMRClient.bubble has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mixedModuleGraph.createBackwardCompatibleFileToModulesMap.getFileToModulesMap (cognitive 21) packages/vite/src/node/server/mixedModuleGraph.ts:651— mixedModuleGraph.createBackwardCompatibleFileToModulesMap.getFileToModulesMap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (8 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.
mixedModuleGraph.createBackwardCompatibleFileToModulesMap.get (cognitive 21) packages/vite/src/node/server/mixedModuleGraph.ts:692— mixedModuleGraph.createBackwardCompatibleFileToModulesMap.get has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hmr.propagateUpdate (cognitive 21) packages/vite/src/node/server/hmr.ts:808— hmr.propagateUpdate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransformPluginContext._getCombinedSourcemap (cognitive 21) packages/vite/src/node/server/pluginContainer.ts:1109— TransformPluginContext._getCombinedSourcemap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 1 (nesting depth added 7). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
shortcuts.bindCLIShortcuts (cognitive 21) packages/vite/src/node/shortcuts.ts:33— shortcuts.bindCLIShortcuts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (onInput, a function literal at line 115). 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.
resolve.resolveDeepImport (cognitive 20) REDACTED:1081— resolve.resolveDeepImport has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (18 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.
hmr.updateModules (cognitive 20) packages/vite/src/node/server/hmr.ts:683— hmr.updateModules has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
worker.webWorkerPostPlugin (cognitive 20) REDACTED:615— worker.webWorkerPostPlugin has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 1 (2 pts), loops 1 (2 pts) (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.
importAnalysisBuild.getChunkImportMapKeySignatures (cognitive 20) packages/vite/src/node/plugins/importAnalysisBuild.ts:44— importAnalysisBuild.getChunkImportMapKeySignatures has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), ternaries 2, boolean chains 1 (nesting depth added 8). Of this number, 18 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
oxc.convertEsbuildConfigToOxcConfig (cognitive 20) packages/vite/src/node/plugins/oxc.ts:353— oxc.convertEsbuildConfigToOxcConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
send.send (cognitive 19) packages/vite/src/node/server/send.ts:32— send.send has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
esbuildBannerFooterCompatPlugin.esbuildBannerFooterCompatPlugin.transform (cognitive 19) packages/vite/src/node/plugins/esbuildBannerFooterCompatPlugin.ts:26— esbuildBannerFooterCompatPlugin.esbuildBannerFooterCompatPlugin.transform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4 (nesting depth added 8). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forwardConsole.formatError (cognitive 19) packages/vite/src/node/plugins/forwardConsole.ts:79— forwardConsole.formatError has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, error handling 1 (2 pts), loops 1, ternaries 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 4 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.
wasm.generateInstanceGlue (cognitive 19) packages/vite/src/node/plugins/wasm.ts:292— wasm.generateInstanceGlue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 4 (7 pts) (nesting depth added 6). Of this number, 13 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.
htmlSafeModulePaths.addHtmlRequestToSafeModulePaths (cognitive 19) REDACTED:73— htmlSafeModulePaths.addHtmlRequestToSafeModulePaths has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.onRollupLog (cognitive 19) packages/vite/src/node/build.ts:1130— build.onRollupLog has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, match/switch 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (viteLog). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BundledDevHMRClient.applyUpdate (cognitive 18) packages/vite/src/shared/bundledDevHmr.ts:444— BundledDevHMRClient.applyUpdate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 4 (5 pts), ternaries 2 (5 pts), error handling 1 (2 pts) (nesting depth added 8). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sourcemap.injectSourcesContent (cognitive 18) packages/vite/src/node/server/sourcemap.ts:70— sourcemap.injectSourcesContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, loops 1 (nesting depth added 8). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 94). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
worker.bundleWorkerEntry (cognitive 18) REDACTED:401— worker.bundleWorkerEntry has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 4 (5 pts), error handling 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
css.minifyCSS (cognitive 18) REDACTED:2371— css.minifyCSS has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (3 pts), boolean chains 2, ternaries 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.
fetchModule.fetchModule (cognitive 18) packages/vite/src/node/ssr/fetchModule.ts:33— fetchModule.fetchModule has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
plugin.resolveEnvironmentPlugins (cognitive 18) packages/vite/src/node/plugin.ts:415— plugin.resolveEnvironmentPlugins has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (5 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.
index._createServer::onFileAddUnlink (cognitive 18) packages/vite/src/node/server/index.ts:929— index._createServer::onFileAddUnlink has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (index._createServer) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
index.resolveServerOptions (cognitive 18) packages/vite/src/node/server/index.ts:1277— index.resolveServerOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.getFullCustomCommand (cognitive 17) packages/create-vite/src/index.ts:1173— index.getFullCustomCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, ternaries 4, boolean chains 2. Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1208, 1179, 1207). 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.
ModuleRunner.constructor (cognitive 17) REDACTED:71— ModuleRunner.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.resolveSubpathImports (cognitive 17) REDACTED:493— resolve.resolveSubpathImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.tryOptimizedResolve (cognitive 17) REDACTED:883— resolve.tryOptimizedResolve has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
asset.resolveBuiltAsset (cognitive 17) packages/vite/src/node/plugins/asset.ts:630— asset.resolveBuiltAsset has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
importMetaGlob.importGlobPlugin (cognitive 17) packages/vite/src/node/plugins/importMetaGlob.ts:37— importMetaGlob.importGlobPlugin has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 76, 99, 67). 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.buildEnvironment (cognitive 17) packages/vite/src/node/build.ts:844— build.buildEnvironment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (4 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 4). Of this number, 13 points are the body's own statements and 4 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.
env.loadEnv (cognitive 17) packages/vite/src/node/env.ts:33— env.loadEnv has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, loops 3 (nesting depth added 2). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: 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.
logger.createLogger::output (cognitive 17) packages/vite/src/node/logger.ts:104— logger.createLogger::output has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 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.
pluginConverter.createResolveIdHandler.<returned closure> (cognitive 17) packages/vite/src/node/optimizer/pluginConverter.ts:202— pluginConverter.createResolveIdHandler.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 3 (4 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
config.loadConfigFromFile (cognitive 17) REDACTED:2426— config.loadConfigFromFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (4 pts), loops 1 (2 pts), boolean chains 1, 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.
pretty-format.printBasicValue (cognitive 16) packages/vite/src/shared/pretty-format.ts:59— pretty-format.printBasicValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 3 (6 pts), boolean chains 2 (nesting depth added 3). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
forwardConsole.formatConsoleArgs.message (cognitive 16) packages/vite/src/shared/forwardConsole.ts:130— forwardConsole.formatConsoleArgs.message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packages.findNearestPackageData (cognitive 16) packages/vite/src/node/packages.ts:129— packages.findNearestPackageData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
importAnalysis.importAnalysisPlugin.transform::resolveId (cognitive 16) REDACTED:300— importAnalysis.importAnalysisPlugin.transform::resolveId has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (importAnalysis.importAnalysisPlugin.transform) 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.
dynamicImportVars.dynamicImportVarsPlugin (cognitive 16) packages/vite/src/node/plugins/dynamicImportVars.ts:170— dynamicImportVars.dynamicImportVarsPlugin has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
indexHtml.devHtmlHook::processNodeUrl::replacer (cognitive 16) REDACTED:188— indexHtml.devHtmlHook::processNodeUrl::replacer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openBrowser.startBrowserProcess (cognitive 16) packages/vite/src/node/server/openBrowser.ts:71— openBrowser.startBrowserProcess has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 3 (4 pts), ternaries 3 (4 pts), error handling 2 (3 pts) (nesting depth added 3). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
asset.shouldInline (cognitive 16) packages/vite/src/node/plugins/asset.ts:754— asset.shouldInline has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 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.
build.resolveBuildEnvironmentOptions (cognitive 16) packages/vite/src/node/build.ts:432— build.resolveBuildEnvironmentOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 4, ternaries 3 (4 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils.mergeInput (cognitive 16) REDACTED:1570— utils.mergeInput has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 2 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MethodTooLong: BundledDev.listen packages/vite/src/node/server/bundledDev.ts:132— MethodTooLong — listen runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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.
Change coupling: REDACTED ↔ customEvent.d.ts REDACTED:1— `REDACTED` and `packages/vite/types/customEvent.d.ts` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `67a68076` refactor: remove HmrUrl concept (#23172); `4f0949f3` feat(bundled-dev): add lazy bundling support (#21406); `2540ed06` feat: forward browser console logs and errors to dev server terminal … — run `git show` on any of them.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Dead branch — condition is always false playground/optimize-deps/dep-linked-include/index.mjs:15— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `semgrep.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
Wholesale file copy (94 identical lines × 2 files) packages/create-vite/template-react-ts/src/App.tsx:1— packages/create-vite/template-react-ts/src/App.tsx:1 · packages/create-vite/template-react/src/App.jsx:1 — these 2 files are line-for-line copies of one another — 94 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.
Wholesale file copy (74 identical lines × 6 files) packages/create-vite/template-preact-ts/src/app.tsx:1— packages/create-vite/template-preact-ts/src/app.tsx:1 · packages/create-vite/template-preact/src/app.jsx:1 · packages/create-vite/template-qwik-ts/src/app.tsx:1 · packages/create-vite/template-qwik/src/app.jsx:1 · +2 more site(s) not listed — these 6 files are line-for-line copies of one another — 74 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.
R10 · Code Duplication· Duplicated block with local edits (73 matched lines × 2 locations) · ×1
Duplicated block with local edits (73 matched lines × 2 locations) playground/hmr-ssr/hmr.ts:16— playground/hmr-ssr/hmr.ts:16 · playground/hmr/hmr.ts:18 — the two spans are one implementation copied and then locally edited — 541 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 (60 lines × 2 locations) playground/ssr-bundled-dev/src/app.js:3— playground/ssr-bundled-dev/src/app.js:3 · playground/ssr/src/app.js:3 — 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 (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) playground/hmr-ssr/vite.config.ts:18— playground/hmr-ssr/vite.config.ts:18 · playground/hmr/vite.config.ts:74 — the two spans are one implementation copied and then locally edited — 271 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 (36 lines × 2 locations) packages/plugin-legacy/src/index.ts:62— packages/plugin-legacy/src/index.ts:62 · packages/vite/src/node/build.ts:1712 — 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 (35 lines × 2 locations) playground/tailwind-v3/vite.config.ts:4— playground/tailwind-v3/vite.config.ts:4 · playground/tailwind/vite.config.ts:5 — 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 (32 lines × 2 locations) REDACTED:6— REDACTED:6 · REDACTED: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.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×1
Duplicated block with local edits (30 matched lines × 2 locations) packages/vite/src/node/server/hmr.ts:910— packages/vite/src/node/server/hmr.ts:910 · packages/vite/src/shared/bundledDevHmr.ts:235 — the two spans are one implementation copied and then locally edited — 143 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 (28 matched lines × 2 locations) · ×1
Duplicated block with local edits (28 matched lines × 2 locations) packages/vite/src/node/plugins/importAnalysisBuild.ts:567— packages/vite/src/node/plugins/importAnalysisBuild.ts:567 · packages/vite/src/node/plugins/importAnalysisBuild.ts:651 — the two spans are one implementation copied and then locally edited — 215 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 (27 lines × 2 locations) REDACTED:8— REDACTED:8 · REDACTED: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 (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) packages/vite/src/node/plugins/html.ts:1587— packages/vite/src/node/plugins/html.ts:1587 · packages/vite/src/node/plugins/html.ts:1623 — 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 (21 lines × 11 locations) playground/multiple-entrypoints/entrypoints/a0.js:26— playground/multiple-entrypoints/entrypoints/a0.js:26 · playground/multiple-entrypoints/entrypoints/a1.js:27 · playground/multiple-entrypoints/entrypoints/a10.js:18 · playground/multiple-entrypoints/entrypoints/a2.js:26 · +7 more site(s) not listed — the 11 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 11 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 (20 lines × 2 locations) playground/worker/vite.config-es.js:32— playground/worker/vite.config-es.js:32 · playground/worker/vite.config-relative-base.js:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) REDACTED:61— REDACTED:61 · REDACTED:99 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) packages/vite/src/node/optimizer/index.ts:279— packages/vite/src/node/optimizer/index.ts:279 · packages/vite/src/node/optimizer/index.ts:318 — the two spans are one implementation copied and then locally edited — 68 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 (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) REDACTED:155— REDACTED:155 · REDACTED:226 — the two spans are one implementation copied and then locally edited — 95 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 (15 lines × 3 locations) playground/optimize-deps/dep-lodash-clonedeep/index.js:4— playground/optimize-deps/dep-lodash-clonedeep/index.js:4 · playground/optimize-deps/dep-lodash/cloneDeep.js:4 · playground/optimize-deps/dep-lodash/index.js:12 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) REDACTED:162— REDACTED:162 · REDACTED:210 — the two spans are one implementation copied and then locally edited — 102 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 (13 lines × 2 locations) packages/vite/src/node/nativeConfigCompat.ts:61— packages/vite/src/node/nativeConfigCompat.ts:61 · packages/vite/src/node/nativeConfigCompat.ts:79 — 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 (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) REDACTED:2463— REDACTED:2463 · packages/vite/src/node/plugins/esbuild.ts:402 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function resolveConfig (cyclomatic 104, cognitive 115) REDACTED:1480— resolveConfig has cyclomatic complexity 104 and cognitive complexity 115; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateBundle (cyclomatic 63, cognitive 222) packages/vite/src/node/plugins/importAnalysisBuild.ts:536— generateBundle has cyclomatic complexity 63 and cognitive complexity 222; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 54, cognitive 110) REDACTED:511— (anonymous) has cyclomatic complexity 54 and cognitive complexity 110; 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 init (cyclomatic 54, cognitive 96) packages/create-vite/src/index.ts:468— init has cyclomatic complexity 54 and cognitive complexity 96; 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 loadAndTransform (cyclomatic 47, cognitive 79) packages/vite/src/node/server/transformRequest.ts:237— loadAndTransform has cyclomatic complexity 47 and cognitive complexity 79; 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 mergeConfigRecursively (cyclomatic 43, cognitive 58) REDACTED:1448— mergeConfigRecursively has cyclomatic complexity 43 and cognitive complexity 58; 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 tryNodeResolve (cyclomatic 43, cognitive 41) REDACTED:722— tryNodeResolve has cyclomatic complexity 43 and cognitive complexity 41; 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 ssrTransformScript (cyclomatic 42, cognitive 105) packages/vite/src/node/ssr/ssrTransform.ts:59— ssrTransformScript has cyclomatic complexity 42 and cognitive complexity 105; 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 transform (cyclomatic 42, cognitive 60) REDACTED:224— transform has cyclomatic complexity 42 and cognitive complexity 60; 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 renderChunk (cyclomatic 39, cognitive 70) REDACTED:721— renderChunk has cyclomatic complexity 39 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function viteTransformMiddleware (cyclomatic 38, cognitive 76) packages/vite/src/node/server/middlewares/transform.ts:140— viteTransformMiddleware has cyclomatic complexity 38 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 33, cognitive 45) packages/vite/src/node/optimizer/scan.ts:456— (anonymous) has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _createServer (cyclomatic 33, cognitive 36) packages/vite/src/node/server/index.ts:512— _createServer has cyclomatic complexity 33 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function transformWithEsbuild (cyclomatic 32, cognitive 64) packages/vite/src/node/plugins/esbuild.ts:97— transformWithEsbuild has cyclomatic complexity 32 and cognitive complexity 64; 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 handleHMRUpdate (cyclomatic 31, cognitive 59) packages/vite/src/node/server/hmr.ts:411— handleHMRUpdate has cyclomatic complexity 31 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 47) packages/vite/src/node/plugins/html.ts:562— (anonymous) has cyclomatic complexity 31 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 29) packages/vite/src/node/build.ts:713— (anonymous) has cyclomatic complexity 31 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 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.
R2 · Cyclomatic Complexity· Complex function enter (cyclomatic 30, cognitive 35) · ×1
Complex function enter (cyclomatic 30, cognitive 35) packages/vite/src/node/ssr/ssrTransform.ts:530— enter has cyclomatic complexity 30 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 parseGlobOptions (cyclomatic 28, cognitive 34) packages/vite/src/node/plugins/importMetaGlob.ts:153— parseGlobOptions has cyclomatic complexity 28 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isRefIdentifier (cyclomatic 28, cognitive 26) packages/vite/src/node/ssr/ssrTransform.ts:630— isRefIdentifier has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 generateBundle (cyclomatic 26, cognitive 45) REDACTED:1058— generateBundle has cyclomatic complexity 26 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compileLightningCSS (cyclomatic 26, cognitive 41) REDACTED:3380— compileLightningCSS has cyclomatic complexity 26 and cognitive complexity 41; 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 resolveId (cyclomatic 26, cognitive 36) packages/vite/src/node/server/pluginContainer.ts:351— resolveId has cyclomatic complexity 26 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveRolldownOptions (cyclomatic 26, cognitive 29) packages/vite/src/node/build.ts:600— resolveRolldownOptions has cyclomatic complexity 26 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 tryCleanFsResolve (cyclomatic 25, cognitive 57) REDACTED:613— tryCleanFsResolve has cyclomatic complexity 25 and cognitive complexity 57; 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 handleMessage (cyclomatic 25, cognitive 32) REDACTED:201— handleMessage has cyclomatic complexity 25 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 resolveDepOptimizationOptions (cyclomatic 25, cognitive 32) REDACTED:1286— resolveDepOptimizationOptions has cyclomatic complexity 25 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 generateBundle (cyclomatic 24, cognitive 66) packages/vite/src/node/plugins/manifest.ts:121— generateBundle has cyclomatic complexity 24 and cognitive complexity 66; 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 CallSiteToString (cyclomatic 24, cognitive 41) packages/vite/src/module-runner/sourcemap/interceptor.ts:276— CallSiteToString has cyclomatic complexity 24 and cognitive complexity 41; 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 resolveId (cyclomatic 24, cognitive 40) packages/vite/src/node/optimizer/scan.ts:599— resolveId has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function lexAcceptedHmrDeps (cyclomatic 23, cognitive 57) packages/vite/src/node/server/hmr.ts:1009— lexAcceptedHmrDeps has cyclomatic complexity 23 and cognitive complexity 57; 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 viteIndexHtmlMiddleware (cyclomatic 23, cognitive 50) REDACTED:438— viteIndexHtmlMiddleware has cyclomatic complexity 23 and cognitive complexity 50; 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 resolveId (cyclomatic 22, cognitive 25) packages/vite/src/node/plugins/preAlias.ts:34— resolveId has cyclomatic complexity 22 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 handler (cyclomatic 21, cognitive 47) packages/vite/src/node/plugins/assetImportMetaUrl.ts:64— handler has cyclomatic complexity 21 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateBundle (cyclomatic 21, cognitive 39) packages/vite/src/node/plugins/asset.ts:371— generateBundle 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 handler (cyclomatic 21, cognitive 29) REDACTED:604— handler 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 resolveBuildEnvironmentOptions (cyclomatic 21, cognitive 20) packages/vite/src/node/build.ts:432— resolveBuildEnvironmentOptions has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 20) packages/vite/src/node/optimizer/pluginConverter.ts:202— (anonymous) has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isCommandLockRecord (cyclomatic 21, cognitive 13) packages/vite/src/node/commandLock.ts:40— isCommandLockRecord has cyclomatic complexity 21 and cognitive complexity 13; 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 generateBundle (cyclomatic 20, cognitive 39) packages/vite/src/node/plugins/html.ts:847— generateBundle has cyclomatic complexity 20 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 3467 lines of code REDACTED:1— REDACTED has 3467 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: 2755 lines of code REDACTED:1— REDACTED has 2755 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/vite/src/node/build.ts · ×1
packages/vite/src/node/build.ts: 1859 lines of code packages/vite/src/node/build.ts:1— packages/vite/src/node/build.ts has 1859 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: 1786 lines of code REDACTED:1— REDACTED has 1786 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/vite/src/node/plugins/html.ts · ×1
packages/vite/src/node/plugins/html.ts: 1612 lines of code packages/vite/src/node/plugins/html.ts:1— packages/vite/src/node/plugins/html.ts has 1612 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/vite/src/node/server/index.ts · ×1
packages/vite/src/node/server/index.ts: 1396 lines of code packages/vite/src/node/server/index.ts:1— packages/vite/src/node/server/index.ts has 1396 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/vite/src/node/optimizer/index.ts · ×1
packages/vite/src/node/optimizer/index.ts: 1383 lines of code packages/vite/src/node/optimizer/index.ts:1— packages/vite/src/node/optimizer/index.ts has 1383 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/vite/src/node/server/pluginContainer.ts · ×1
packages/vite/src/node/server/pluginContainer.ts: 1220 lines of code packages/vite/src/node/server/pluginContainer.ts:1— packages/vite/src/node/server/pluginContainer.ts has 1220 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/create-vite/src/index.ts · ×1
packages/create-vite/src/index.ts: 1194 lines of code packages/create-vite/src/index.ts:1— packages/create-vite/src/index.ts has 1194 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: 1126 lines of code REDACTED:1— REDACTED has 1126 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/vite/src/node/server/hmr.ts · ×1
packages/vite/src/node/server/hmr.ts: 1107 lines of code packages/vite/src/node/server/hmr.ts:1— packages/vite/src/node/server/hmr.ts has 1107 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: 1099 lines of code REDACTED:1— REDACTED has 1099 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/plugin-legacy/src/index.ts · ×1
packages/plugin-legacy/src/index.ts: 1090 lines of code packages/plugin-legacy/src/index.ts:1— packages/plugin-legacy/src/index.ts has 1090 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: 904 lines of code REDACTED:1— REDACTED has 904 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/vite/src/node/plugins/importAnalysisBuild.ts · ×1
packages/vite/src/node/plugins/importAnalysisBuild.ts: 855 lines of code packages/vite/src/node/plugins/importAnalysisBuild.ts:1— packages/vite/src/node/plugins/importAnalysisBuild.ts has 855 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/vite/src/node/plugins/asset.ts · ×1
packages/vite/src/node/plugins/asset.ts: 762 lines of code packages/vite/src/node/plugins/asset.ts:1— packages/vite/src/node/plugins/asset.ts has 762 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/vite/src/node/optimizer/scan.ts · ×1
packages/vite/src/node/optimizer/scan.ts: 734 lines of code packages/vite/src/node/optimizer/scan.ts:1— packages/vite/src/node/optimizer/scan.ts has 734 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/vite/src/node/ssr/ssrTransform.ts · ×1
packages/vite/src/node/ssr/ssrTransform.ts: 728 lines of code packages/vite/src/node/ssr/ssrTransform.ts:1— packages/vite/src/node/ssr/ssrTransform.ts has 728 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/vite/src/node/optimizer/optimizer.ts · ×1
packages/vite/src/node/optimizer/optimizer.ts: 705 lines of code packages/vite/src/node/optimizer/optimizer.ts:1— packages/vite/src/node/optimizer/optimizer.ts has 705 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/vite/src/node/server/mixedModuleGraph.ts · ×1
packages/vite/src/node/server/mixedModuleGraph.ts: 694 lines of code packages/vite/src/node/server/mixedModuleGraph.ts:1— packages/vite/src/node/server/mixedModuleGraph.ts has 694 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/vite/src/node/plugins/importMetaGlob.ts · ×1
packages/vite/src/node/plugins/importMetaGlob.ts: 643 lines of code packages/vite/src/node/plugins/importMetaGlob.ts:1— packages/vite/src/node/plugins/importMetaGlob.ts has 643 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/vite/src/node/server/bundledDev.ts · ×1
packages/vite/src/node/server/bundledDev.ts: 631 lines of code packages/vite/src/node/server/bundledDev.ts:1— packages/vite/src/node/server/bundledDev.ts has 631 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: 584 lines of code REDACTED:1— REDACTED has 584 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: 555 lines of code REDACTED:1— REDACTED has 555 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/vite/src/shared/bundledDevHmr.ts · ×1
packages/vite/src/shared/bundledDevHmr.ts: 523 lines of code packages/vite/src/shared/bundledDevHmr.ts:1— packages/vite/src/shared/bundledDevHmr.ts has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 522 lines of code REDACTED:1— REDACTED has 522 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/vite/src/node/server/transformRequest.ts · ×1
packages/vite/src/node/server/transformRequest.ts: 506 lines of code packages/vite/src/node/server/transformRequest.ts:1— packages/vite/src/node/server/transformRequest.ts has 506 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/vite/src/node/cli.ts · ×1
packages/vite/src/node/cli.ts: 467 lines of code packages/vite/src/node/cli.ts:1— packages/vite/src/node/cli.ts has 467 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/vite/src/node/plugins/esbuild.ts · ×1
packages/vite/src/node/plugins/esbuild.ts: 459 lines of code packages/vite/src/node/plugins/esbuild.ts:1— packages/vite/src/node/plugins/esbuild.ts has 459 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/vite/src/node/server/environment.ts · ×1
packages/vite/src/node/server/environment.ts: 453 lines of code packages/vite/src/node/server/environment.ts:1— packages/vite/src/node/server/environment.ts has 453 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/vite/src/node/plugins/wasm.ts · ×1
packages/vite/src/node/plugins/wasm.ts: 447 lines of code packages/vite/src/node/plugins/wasm.ts:1— packages/vite/src/node/plugins/wasm.ts has 447 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/vite/src/node/plugin.ts · ×1
packages/vite/src/node/plugin.ts: 444 lines of code packages/vite/src/node/plugin.ts:1— packages/vite/src/node/plugin.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/vite/src/node/server/moduleGraph.ts · ×1
packages/vite/src/node/server/moduleGraph.ts: 441 lines of code packages/vite/src/node/server/moduleGraph.ts:1— packages/vite/src/node/server/moduleGraph.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 440 lines of code REDACTED:1— REDACTED has 440 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: 433 lines of code REDACTED:1— REDACTED has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded packages/vite/src/node/__tests__/plugins/license.spec.ts:8— This repository declares test tooling, and the ✓ above records that declaration — but packages/vite/src/node/__tests__/plugins/license.spec.ts and 4 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~68 LoC) packages/vite/bin/openChrome.js— no import path from any entry point (792 application, 209 tooling, 615 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 (~11 LoC) playground/hmr-ssr/counter/index.ts— no import path from any entry point (792 application, 209 tooling, 615 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 (~10 LoC) playground/css/postcss-caching/serve.ts— no import path from any entry point (792 application, 209 tooling, 615 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 (~7 LoC) playground/resolve/ts-extension/index.ts— no import path from any entry point (792 application, 209 tooling, 615 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 (~4 LoC) playground/hmr-ssr/counter/dep.ts— no import path from any entry point (792 application, 209 tooling, 615 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (playground/hmr-ssr/counter/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~3 LoC) playground/ssr-webworker/cjs-node-builtin/installed-node-builtin.cjs— no import path from any entry point (792 application, 209 tooling, 615 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
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked playground/package.json:9— playground/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: compileFromUrl packages/vite/src/node/plugins/wasm.ts:78— `compileFromUrl` 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 })`.
No direct assertions: named playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:19— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: TS output playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:25— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shared worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:34— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: named shared worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:38— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: inline shared worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:42— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: worker emitted and import.meta.url in nested worker (serve) playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:48— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: worker emitted and import.meta.url in nested worker (build) playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:89— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: module worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:99— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: import.meta.glob in worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:130— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: import.meta.glob with eager in worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:136— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: self reference worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:142— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: self reference url worker playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:148— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: worker emitted and import.meta.url in nested worker (build) playground/worker/__tests__/iife/worker-iife.spec.ts:117— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: worker emitted and import.meta.url in nested worker (build) playground/worker/__tests__/es/worker-es.spec.ts:176— No conventional assertion call was detected, and 14 of 23 tests in `playground/worker` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should work when inlined playground/wasm/__tests__/wasm.spec.ts:4— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should work when output playground/wasm/__tests__/wasm.spec.ts:14— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: init function returns WebAssembly.Instance playground/wasm/__tests__/wasm.spec.ts:21— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should work when wasm in worker playground/wasm/__tests__/wasm.spec.ts:34— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: direct wasm import playground/wasm/__tests__/wasm.spec.ts:38— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: direct wasm import with wasm imports playground/wasm/__tests__/wasm.spec.ts:42— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: direct wasm import unwraps exported WebAssembly.Global playground/wasm/__tests__/wasm.spec.ts:48— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: wasm importing a global from another wasm playground/wasm/__tests__/wasm.spec.ts:54— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: wasm reading a mutable global mutated by another wasm playground/wasm/__tests__/wasm.spec.ts:60— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: wasm using js-string builtins and imported string constants playground/wasm/__tests__/wasm.spec.ts:66— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: source phase import yields a WebAssembly.Module playground/wasm/__tests__/wasm.spec.ts:72— No conventional assertion call was detected, and 13 of 14 tests in `playground/wasm` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Orphaned file packages/create-vite/template-lit/src/my-element.js: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/create-vite/template-lit-ts/src/my-element.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/vite/scripts/benchCircularImport.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/vite/src/node/external.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/create-vite/template-react-ts/src/App.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/create-vite/template-react/src/App.jsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/create-vite/template-solid-ts/src/App.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/create-vite/template-solid/src/App.jsx: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/create-vite/template-preact-ts/src/app.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/create-vite/template-preact/src/app.jsx: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/create-vite/template-qwik-ts/src/app.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/create-vite/template-qwik/src/app.jsx: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/create-vite/template-vue-ts/src/components/HelloWorld.vue: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/create-vite/template-vue/src/components/HelloWorld.vue: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/create-vite/template-svelte-ts/src/App.svelte: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/create-vite/template-svelte/src/App.svelte: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/create-vite/template-vanilla-ts/src/main.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/create-vite/template-vanilla/src/main.js: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.
Duplicated predicate playground/hmr/vite.config.ts:11— `!!process.env.VITEST && inject('playgroundMode') === 'serve-bundled'` appears character-identically in 2 files — playground/hmr/vite.config.ts, playground/html/vite.config.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 docs/_data/acknowledgements.data.ts:154— `!url.includes(':') && url.split('/').length === 2` appears character-identically in 2 files — docs/_data/acknowledgements.data.ts, packages/vite/rollupLicensePlugin.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 playground/worker/classic-shared-worker.js:2— `base.endsWith('.js') || base === `/worker-entries`` appears character-identically in 2 files — playground/worker/classic-shared-worker.js, playground/worker/classic-worker.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/vite/src/node/preview.ts:293— `config.appType === 'spa' || config.appType === 'mpa'` appears character-identically in 2 files — packages/vite/src/node/preview.ts, packages/vite/src/node/server/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 packages/plugin-legacy/src/index.ts:71— `config.base === '' || config.base === './'` appears character-identically in 3 files — packages/plugin-legacy/src/index.ts, packages/vite/src/node/build.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/plugin-legacy/src/index.ts:102— `config.base === './' || config.base === ''` appears character-identically in 4 files — packages/plugin-legacy/src/index.ts, REDACTED, packages/vite/src/node/plugins/html.ts, packages/vite/src/node/plugins/importAnalysisBuild.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 playground/glob-import/root/side-effect/writedom.js:2— `document && (document.querySelector('.side-effect-result').textContent = 'Hello from side effect')` appears character-identically in 2 files — playground/glob-import/root/side-effect/writedom.js, playground/glob-import/root/side-effect/writetodom.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/vite/src/node/plugins/html.ts:749— `node.nodeName === 'style' && node.childNodes.length` appears character-identically in 2 files — packages/vite/src/node/plugins/html.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:2466— `options.minifyIdentifiers != null || options.minifySyntax != null || options.minifyWhitespace != null` appears character-identically in 2 files — REDACTED, packages/vite/src/node/plugins/esbuild.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:343— `rawUrl[0] === '`' && rawUrl.includes('${')` appears character-identically in 3 files — REDACTED, packages/vite/src/node/plugins/assetImportMetaUrl.ts, packages/vite/src/node/plugins/workerImportMetaUrl.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/plugin-legacy/src/index.ts:903— `typeof chunkImportMap === 'object' && chunkImportMap.fileName` appears character-identically in 2 files — packages/plugin-legacy/src/index.ts, packages/vite/src/node/plugins/html.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 playground/hmr-ssr/hmr.ts:78— `update.type === 'css-update' && update.path.includes('global.css')` appears character-identically in 2 files — playground/hmr-ssr/hmr.ts, playground/hmr/hmr.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 playground/optimize-deps/dep-lodash-clonedeep/index.js:5— `value == null || typeof value !== 'object'` appears character-identically in 3 files — playground/optimize-deps/dep-lodash-clonedeep/index.js, playground/optimize-deps/dep-lodash/cloneDeep.js, playground/optimize-deps/dep-lodash/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.
No app-layer HTTPS enforcement detected REDACTED:411— `wsHttpServer.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:81— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:67— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:75— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:81— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:121— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:119— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:79— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:71— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:56— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:69— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
P2 · Observability· Console output used as the logging channel · ×9
Console output used as the logging channel packages/vite/rollupLicensePlugin.ts:111— `packages/vite/rollupLicensePlugin.ts` reports through `console.*` at line 111 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/vite/src/node/env.ts:120— `packages/vite/src/node/env.ts` reports through `console.*` at line 120 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/vite/src/node/plugins/esbuild.ts:89— `packages/vite/src/node/plugins/esbuild.ts` reports through `console.*` at line 89 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/vite/src/node/plugins/oxc.ts:185— `packages/vite/src/node/plugins/oxc.ts` reports through `console.*` at line 185 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 REDACTED:305— `REDACTED` reports through `console.*` at line 305 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/vite/src/module-runner/hmrLogger.ts:11— `packages/vite/src/module-runner/hmrLogger.ts` reports through `console.*` at line 11 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/vite/src/module-runner/hmrLogger.ts:12— `packages/vite/src/module-runner/hmrLogger.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/vite/src/client/bundledDevClient.ts:59— `packages/vite/src/client/bundledDevClient.ts` reports through `console.*` at line 59 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/vite/src/client/bundledDevClient.ts:60— `packages/vite/src/client/bundledDevClient.ts` reports through `console.*` at line 60 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
redundant comment REDACTED:2246— "call configResolved hooks" repeats the code it sits on: 4 of its 4 words (call, config, resolved, hooks) are already in `await Promise.all(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:2895— "data-uri() calls" repeats the code it sits on: 3 of its 3 words (data, uri, calls) are already in `const hasDataUris = cssDataUriRE.test(content)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:256— "add HTML Proxy to Map" repeats the code it sits on: 4 of its 4 words (add, html, proxy, map) are already in `addToHTMLProxyCache(config, proxyCacheUrl, inlineModuleIndex, { code, map })`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/vite/src/node/ssr/ssrTransform.ts:693— "member expression property" repeats the code it sits on: 3 of its 3 words (member, expression, property) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:1041— "Set host name to localhost when possible" repeats the code it sits on: 4 of its 5 words (set, host, name, localhost) are already in `let name = host === undefined || wildcardHosts.has(host) ? 'localhost' : host`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment playground/dynamic-import/__tests__/dynamic-import.spec.ts:63— "dynamic import css" repeats the code it sits on: 3 of its 3 words (dynamic, import, css) are already in `test('should load dynamic import with css', async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment playground/legacy/__tests__/legacy.spec.ts:95— "dynamic import css" repeats the code it sits on: 3 of its 3 words (dynamic, import, css) are already in `test('should load dynamic import with css', async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Disabled test packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts:188— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test playground/css-codesplit-cjs/__tests__/css-codesplit-cjs.spec.ts:4— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test playground/hmr-full-bundle-mode/__tests__/hmr-full-bundle-mode.spec.ts:545— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test playground/ssr-deps/__tests__/ssr-deps.spec.ts:134— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:30— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Blanket warning suppression playground/tsconfig-json-load-error/src/main.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression playground/tsconfig-json/nested-with-extends/main.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression playground/tsconfig-json/nested/main.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression playground/tsconfig-json/src/decorator.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression playground/tsconfig-json/src/main.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Hand-rolled JSON/XML parsing via regex packages/vite/src/node/plugins/html.ts:73— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/vite/src/node/plugins/html.ts:1576— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/vite/src/node/plugins/html.ts:1579— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/vite/src/node/plugins/html.ts:1582— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/vite/src/node/optimizer/scan.ts:357— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Unused export 'default' playground/css/treeshake-scoped/b.js:3— Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-scoped/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-scoped/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' playground/css/treeshake-scoped/c.js:3— Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-scoped/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-scoped/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' playground/css/treeshake-scoped/d.js:3— Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-scoped/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-scoped/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' playground/hmr-ssr/accept-exports/side-effects/side-effects.ts:5— Nothing imports this binding — it is safe to review for removal.
Mock-dominated test: binding custom shortcuts with the %s packages/vite/src/node/__tests__/shortcuts.spec.ts:8— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 9 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: hook filter with build packages/vite/src/node/__tests__/plugins/index.spec.ts:91— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Unused export 'b' playground/css/treeshake-module/b.js:3— Nothing ultimately consumes this binding: its only referrer is the re-export in playground/css/treeshake-module/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in playground/css/treeshake-module/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'b' playground/hmr-ssr/accept-exports/main-non-accepted/named.ts:5— Nothing imports this binding — it is safe to review for removal.
Fat interface: ViteDevServer (17 required operations) packages/vite/src/node/server/index.ts:329— `ViteDevServer` declares 17 required operations: `transformRequest`, `warmupRequest`, `transformIndexHtml`, `ssrTransform`, `ssrLoadModule`, `ssrRewriteStacktrace`, `ssrFixStacktrace`, `reloadModule`, `listen`, `close`, `printUrls`, `bindCLIShortcuts`, `restart`, `openBrowser`, `waitForRequestsIdle`, `_setInternalServer`, `_closeServer`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies REDACTED:388— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: playground/resolve-tsconfig-paths playground/resolve-tsconfig-paths/__tests__/resolve.spec.ts:4— No conventional assertion call was detected in 9 of 9 tests in `playground/resolve-tsconfig-paths` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Deprecated: glob REDACTED:6081— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Outdated (npm): birpc packages/vite/src/node/ssr/runtime/__tests__/package.json:13— birpc is pinned at 0.2.19; registry.npmjs.org publishes 4.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: packages/vite/src/node/plugins/forwardConsole.ts, packages/vite/src/node/baseEnvironment.ts, packages/vite/src/node/deprecations.ts, packages/vite/src/node/__tests_dts__/config.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (7 single-owned of 120 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 120 of the 207 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/vite/src/node/nativeConfigCompat.ts, packages/vite/scripts/benchCircularImport.ts, packages/vite/src/shared/pretty-format.ts.
Documentation: no build, run or usage example packages/vite/README.md:1— `vite` is a command-line package (`bin` in `package.json`) and neither `packages/vite/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 229 project(s) overshoot their size bounds, lowering Project Cohesion to 9.9/10. The most over is `packages/vite` (45942 LoC, 300 module-visible types across 16 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 19 of 120 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; 120 of the 207 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/create-vite/template-lit/src/my-element.js, packages/create-vite/template-lit-ts/src/my-element.ts, packages/vite/scripts/benchCircularImport.ts, packages/vite/src/node/external.ts, packages/create-vite/template-react-ts/src/App.tsx, packages/create-vite/template-react/src/App.jsx, REDACTED, packages/create-vite/template-solid-ts/src/App.tsx (and 11 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.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body playground/dynamic-import/files/mxd.js:1— `default` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Logging is not universal — Only 3/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `playground`, `playground/css-lightningcss-proxy`, `playground/js-sourcemap`, `playground/optimize-missing-deps`, `playground/ssr` and 8 more.
No dependency-update automation package.json:44— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Unused export 'updateStyle' REDACTED:564— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/vite/src/client/bundledDevClient.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/vite/src/client/bundledDevClient.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'removeStyle' REDACTED:597— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/vite/src/client/bundledDevClient.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/vite/src/client/bundledDevClient.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'createHotContext' · ×1
Unused export 'createHotContext' REDACTED:614— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/vite/src/client/bundledDevClient.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/vite/src/client/bundledDevClient.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'injectQuery' REDACTED:621— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/vite/src/client/bundledDevClient.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/vite/src/client/bundledDevClient.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'UnknownEnvironment' · ×1
Unused export 'UnknownEnvironment' packages/vite/src/node/baseEnvironment.ts:136— No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`.
Unused export 'y' playground/hmr-ssr/accept-exports/side-effects/side-effects.ts:3— Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene· Test-only dependency '@jridgewell/trace-mapping' in production deps · ×1
Test-only dependency '@jridgewell/trace-mapping' in production deps playground/js-sourcemap/package.json:13— Only test files import it (first: playground/js-sourcemap/__tests__/js-sourcemap.spec.ts:5) — move it to devDependencies.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted packages/vite/src/shared/bundledDevHmr.ts:277— `debug` at line 277 is called with an argument built by `importChain.join(' -> ')` (line 278), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
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 — 5/49 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~5.5 `!` null assertions per 1k TypeScript source lines — 311 assertion(s) across the 56784 source line(s) of the 276 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: REDACTED (32), packages/vite/src/node/plugins/html.ts (29), REDACTED (20). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default in catch packages/vite/src/shared/forwardConsole.ts:169— `formatConsoleArgs.message` swallows every exception into `return '[Circular]'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Skipped (documented): (unnamed test) playground/worker/__tests__/relative-base-iife/worker-relative-base-iife.spec.ts:4— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:6— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:105— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/relative-base/worker-relative-base.spec.ts:119— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:16— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:33— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:39— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:43— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:47— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:53— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:57— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:61— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:67— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:142— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:157— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:171— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:177— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:183— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:189— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:195— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:201— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/iife/worker-iife.spec.ts:210— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) playground/worker/__tests__/es/worker-es.spec.ts:6— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/es/worker-es.spec.ts:24— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) playground/worker/__tests__/es/worker-es.spec.ts:30— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Outdated (npm): @babel/core — @babel/core is pinned at 7.29.13; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-dynamic-import — @babel/plugin-transform-dynamic-import is pinned at 7.29.7; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-modules-systemjs — @babel/plugin-transform-modules-systemjs is pinned at 7.29.8; registry.npmjs.org publishes 8.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-env — @babel/preset-env is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/runtime — @babel/runtime is pinned at 7.29.13; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): babel-plugin-polyfill-corejs3 — babel-plugin-polyfill-corejs3 is pinned at 0.14.2; registry.npmjs.org publishes 1.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): babel-plugin-polyfill-regenerator — babel-plugin-polyfill-regenerator is pinned at 0.6.8; registry.npmjs.org publishes 1.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): postcss — postcss is pinned at 8.5.32; registry.npmjs.org publishes 8.5.33 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): rolldown — rolldown is pinned at 1.3.1; registry.npmjs.org publishes 1.3.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tinyspy — tinyspy is pinned at 2.2.0; registry.npmjs.org publishes 4.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names playground/ssr-bundled-dev/src/forked-deadlock/common-module.js:5— 0 of 0 documented parameters and 16 of 16 summaries in `@vitejs/test-ssr` only repeat the member or parameter name (e.g. "module H" for `commonModuleExport`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/vite/src/node/build.ts:280— 0 of 29 documented parameters and 7 of 498 summaries in `vite` only repeat the member or parameter name (e.g. "Emit assets during SSR." for `ssrEmitAssets`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 35 file(s) — `docs/.vitepress/config.ts`, `packages/create-vite/src/index.ts`, `packages/plugin-legacy/src/index.ts`, `REDACTED`, `packages/vite/rolldown.dts.config.ts`, … (+30 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d96d-49f3-71ad-88f9-1973c60a39f9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 69 · Warnings: 794 · Recommendations: 285 · Info: 190 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 09:39 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.