Public report of parcel-bundler/parcel, published 13 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.3). 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, 13 November 2026, 17:17 UTC · Survey ID cd_7ac27b6765204252a71c2d87ecc589ba
parcel-bundler/parcel
Measured 13 November 2026, 17:16 UTC, at code version 634ef6c
CAI scoreAt riskDown 7 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: 90,890 lines of product code in 36 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Security and Compliance, 14
Findings by how serious they are
82 critical736 serious112 minor
17 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
13 November 2026, 17:16 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
65of 65 dimensions measured by tools.
890of 930 findings point to an exact file and line, so you can open each one in the code. The other 40 concern the repository as a whole, such as missing documentation.
65dimensions across 7 lenses, read from 90,890 lines of product code in 36 projects.
parcel-bundler/parcel is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no access checks on the code's endpoints or handlers and 14 of the dependencies have a known vulnerability. It scores 37 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 14, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 18 points. Fixing the two runtimes or frameworks that no longer get security updates comes next, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 56.
Fifty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixteen known security holes in the packages the code depends on can be used by attackers, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command.
The product code is 90,890 lines, about €95,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 14 to 70, the lowest score rated Strong, the score would rise from 37 to about 56.
Code composition: what the lines of code are
Product code 81%Tests 19%
New since the last survey: 715 findings
These 715 critical or serious findings weren't in the previous survey, on 24 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: 1480 findings
These 1480 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one. The first 100 are listed here.
€32,000 to €160,000, for 526 to 1,669 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 37. 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: 90,890 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
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Raises the score by about 18 points · Medium effort · Access Controls
2
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (2).
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 1 point · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €95,000 to build again, about 0.7 person-years of work. Its weakest lens is Security and Compliance, at 14 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. Of all the actions in this report, it raises the score most for the work it takes: about 18 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 6.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 114,330 lines over the last 90 days, which is about 463,672 lines a year. At that pace, the extra work comes to an estimated 36.8 to 220.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
207 modules, with 545 dependencies between them. 5 loops run through 27 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 167 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.
parcel_core.fs uses parcel_core.path, so a change to parcel_core.path can break parcel_core.fs, while a change to parcel_core.fs can't break parcel_core.path.
Position
Below the diagonal: parcel_core.fs uses a module listed above it, which is the healthy direction.
parcel_core.location uses parcel_core.path, so a change to parcel_core.path can break parcel_core.location, while a change to parcel_core.location can't break parcel_core.path.
Position
Below the diagonal: parcel_core.location uses a module listed above it, which is the healthy direction.
parcel_core.target uses parcel_core.path, so a change to parcel_core.path can break parcel_core.target, while a change to parcel_core.target can't break parcel_core.path.
Position
Below the diagonal: parcel_core.target uses a module listed above it, which is the healthy direction.
5→13 parcel_core.target uses parcel_core.assetpart of a loop✕
Connections
1 pair of types, where a type in parcel_core.target uses a type in parcel_core.asset.
parcel_core.target uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.target, while a change to parcel_core.target can't break parcel_core.asset.
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.
parcel_highlight.js uses parcel_highlight, so a change to parcel_highlight can break parcel_highlight.js, while a change to parcel_highlight.js can't break parcel_highlight.
Position
Below the diagonal: parcel_highlight.js uses a module listed above it, which is the healthy direction.
parcel_core.bundle_graph uses parcel_core.path, so a change to parcel_core.path can break parcel_core.bundle_graph, while a change to parcel_core.bundle_graph can't break parcel_core.path.
Position
Below the diagonal: parcel_core.bundle_graph uses a module listed above it, which is the healthy direction.
parcel_core.bundle_graph uses parcel_core.target, so a change to parcel_core.target can break parcel_core.bundle_graph, while a change to parcel_core.bundle_graph can't break parcel_core.target.
Position
Below the diagonal: parcel_core.bundle_graph uses a module listed above it, which is the healthy direction.
7→11 parcel_core.bundle_graph uses parcel_core.bundlepart of a loop✕
Connections
1 pair of types, where a type in parcel_core.bundle_graph uses a type in parcel_core.bundle.
parcel_core.bundle_graph uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_core.bundle_graph, while a change to parcel_core.bundle_graph can't break parcel_core.bundle.
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.
7→16 parcel_core.bundle_graph uses parcel_core.asset_graphpart of a loop✕
Connections
3 pairs of types, where a type in parcel_core.bundle_graph uses a type in parcel_core.asset_graph.
parcel_core.bundle_graph uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.bundle_graph, while a change to parcel_core.bundle_graph can't break parcel_core.asset_graph.
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.
parcel_core.diagnostic uses parcel_highlight, so a change to parcel_highlight can break parcel_core.diagnostic, while a change to parcel_core.diagnostic can't break parcel_highlight.
Position
Below the diagonal: parcel_core.diagnostic uses a module listed above it, which is the healthy direction.
parcel_core.diagnostic uses parcel_core.location, so a change to parcel_core.location can break parcel_core.diagnostic, while a change to parcel_core.diagnostic can't break parcel_core.location.
Position
Below the diagonal: parcel_core.diagnostic uses a module listed above it, which is the healthy direction.
8→13 parcel_core.diagnostic uses parcel_core.assetpart of a loop✕
Connections
2 pairs of types, where a type in parcel_core.diagnostic uses a type in parcel_core.asset.
parcel_core.diagnostic uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.diagnostic, while a change to parcel_core.diagnostic can't break parcel_core.asset.
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.
parcel_core.reporter uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_core.reporter, while a change to parcel_core.reporter can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_core.reporter uses a module listed above it, which is the healthy direction.
parcel_core.reporter uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_core.reporter, while a change to parcel_core.reporter can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_core.reporter uses a module listed above it, which is the healthy direction.
9→10 parcel_core.reporter uses parcel_core.optionspart of a loop✕
Connections
3 pairs of types, where a type in parcel_core.reporter uses a type in parcel_core.options.
parcel_core.reporter uses parcel_core.options, so a change to parcel_core.options can break parcel_core.reporter, while a change to parcel_core.reporter can't break parcel_core.options.
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.
parcel_core.options uses parcel_core.path, so a change to parcel_core.path can break parcel_core.options, while a change to parcel_core.options can't break parcel_core.path.
Position
Below the diagonal: parcel_core.options uses a module listed above it, which is the healthy direction.
parcel_core.options uses parcel_core.target, so a change to parcel_core.target can break parcel_core.options, while a change to parcel_core.options can't break parcel_core.target.
Position
Below the diagonal: parcel_core.options uses a module listed above it, which is the healthy direction.
parcel_core.options uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_core.options, while a change to parcel_core.options can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_core.options uses a module listed above it, which is the healthy direction.
parcel_core.options uses parcel_core.reporter, so a change to parcel_core.reporter can break parcel_core.options, while a change to parcel_core.options can't break parcel_core.reporter.
Position
Below the diagonal: parcel_core.options uses a module listed above it, which is the healthy direction.
parcel_core.bundle uses parcel_core.path, so a change to parcel_core.path can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.path.
Position
Below the diagonal: parcel_core.bundle uses a module listed above it, which is the healthy direction.
parcel_core.bundle uses parcel_core.location, so a change to parcel_core.location can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.location.
Position
Below the diagonal: parcel_core.bundle uses a module listed above it, which is the healthy direction.
parcel_core.bundle uses parcel_core.target, so a change to parcel_core.target can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.target.
Position
Below the diagonal: parcel_core.bundle uses a module listed above it, which is the healthy direction.
parcel_core.bundle uses parcel_core.options, so a change to parcel_core.options can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.options.
Position
Below the diagonal: parcel_core.bundle uses a module listed above it, which is the healthy direction.
11→13 parcel_core.bundle uses parcel_core.assetpart of a loop✕
Connections
1 pair of types, where a type in parcel_core.bundle uses a type in parcel_core.asset.
parcel_core.bundle uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.asset.
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.
11→16 parcel_core.bundle uses parcel_core.asset_graphpart of a loop✕
Connections
1 pair of types, where a type in parcel_core.bundle uses a type in parcel_core.asset_graph.
parcel_core.bundle uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.bundle, while a change to parcel_core.bundle can't break parcel_core.asset_graph.
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.
parcel_core.dependency uses parcel_core.location, so a change to parcel_core.location can break parcel_core.dependency, while a change to parcel_core.dependency can't break parcel_core.location.
Position
Below the diagonal: parcel_core.dependency uses a module listed above it, which is the healthy direction.
parcel_core.dependency uses parcel_core.target, so a change to parcel_core.target can break parcel_core.dependency, while a change to parcel_core.dependency can't break parcel_core.target.
Position
Below the diagonal: parcel_core.dependency uses a module listed above it, which is the healthy direction.
parcel_core.dependency uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_core.dependency, while a change to parcel_core.dependency can't break parcel_core.bundle.
Position
Below the diagonal: parcel_core.dependency uses a module listed above it, which is the healthy direction.
12→13 parcel_core.dependency uses parcel_core.assetpart of a loop✕
Connections
3 pairs of types, where a type in parcel_core.dependency uses a type in parcel_core.asset.
parcel_core.dependency uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.dependency, while a change to parcel_core.dependency can't break parcel_core.asset.
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.
1 pair of types, where a type in parcel_core.asset uses a type in parcel_core.path.
The types involved
parcel_core.asset.Asset → parcel_core.path.PathId
Direction
parcel_core.asset uses parcel_core.path, so a change to parcel_core.path can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.path.
Position
Below the diagonal: parcel_core.asset uses a module listed above it, which is the healthy direction.
parcel_core.asset uses parcel_core.location, so a change to parcel_core.location can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.location.
Position
Below the diagonal: parcel_core.asset uses a module listed above it, which is the healthy direction.
parcel_core.asset uses parcel_core.target, so a change to parcel_core.target can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.target.
Position
Below the diagonal: parcel_core.asset uses a module listed above it, which is the healthy direction.
parcel_core.asset uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.bundle.
Position
Below the diagonal: parcel_core.asset uses a module listed above it, which is the healthy direction.
parcel_core.asset uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.asset uses a module listed above it, which is the healthy direction.
13→16 parcel_core.asset uses parcel_core.asset_graphpart of a loop✕
Connections
2 pairs of types, where a type in parcel_core.asset uses a type in parcel_core.asset_graph.
parcel_core.asset uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.asset, while a change to parcel_core.asset can't break parcel_core.asset_graph.
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.
parcel_core.config uses parcel_core.path, so a change to parcel_core.path can break parcel_core.config, while a change to parcel_core.config can't break parcel_core.path.
Position
Below the diagonal: parcel_core.config uses a module listed above it, which is the healthy direction.
parcel_core.config uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_core.config, while a change to parcel_core.config can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_core.config uses a module listed above it, which is the healthy direction.
parcel_core.config uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.config, while a change to parcel_core.config can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.config uses a module listed above it, which is the healthy direction.
parcel_core.entry uses parcel_core.path, so a change to parcel_core.path can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.path.
Position
Below the diagonal: parcel_core.entry uses a module listed above it, which is the healthy direction.
parcel_core.entry uses parcel_core.location, so a change to parcel_core.location can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.location.
Position
Below the diagonal: parcel_core.entry uses a module listed above it, which is the healthy direction.
parcel_core.entry uses parcel_core.target, so a change to parcel_core.target can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.target.
Position
Below the diagonal: parcel_core.entry uses a module listed above it, which is the healthy direction.
parcel_core.entry uses parcel_core.options, so a change to parcel_core.options can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.options.
Position
Below the diagonal: parcel_core.entry uses a module listed above it, which is the healthy direction.
parcel_core.entry uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.entry uses a module listed above it, which is the healthy direction.
15→16 parcel_core.entry uses parcel_core.asset_graphpart of a loop✕
Connections
1 pair of types, where a type in parcel_core.entry uses a type in parcel_core.asset_graph.
parcel_core.entry uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.entry, while a change to parcel_core.entry can't break parcel_core.asset_graph.
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.
parcel_core.asset_graph uses parcel_core.target, so a change to parcel_core.target can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.target.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.asset_graph uses parcel_core.options, so a change to parcel_core.options can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.options.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.asset_graph uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.asset_graph uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.asset.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.asset_graph uses parcel_core.config, so a change to parcel_core.config can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.config.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.asset_graph uses parcel_core.entry, so a change to parcel_core.entry can break parcel_core.asset_graph, while a change to parcel_core.asset_graph can't break parcel_core.entry.
Position
Below the diagonal: parcel_core.asset_graph uses a module listed above it, which is the healthy direction.
parcel_core.context uses parcel_core.options, so a change to parcel_core.options can break parcel_core.context, while a change to parcel_core.context can't break parcel_core.options.
Position
Below the diagonal: parcel_core.context uses a module listed above it, which is the healthy direction.
parcel_core.context uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.context, while a change to parcel_core.context can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.context uses a module listed above it, which is the healthy direction.
parcel_core.context uses parcel_core.config, so a change to parcel_core.config can break parcel_core.context, while a change to parcel_core.context can't break parcel_core.config.
Position
Below the diagonal: parcel_core.context uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.path, so a change to parcel_core.path can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.path.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.target, so a change to parcel_core.target can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.target.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.options, so a change to parcel_core.options can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.options.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.asset, so a change to parcel_core.asset can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.asset.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.hmr uses parcel_core.config, so a change to parcel_core.config can break parcel_js.hmr, while a change to parcel_js.hmr can't break parcel_core.config.
Position
Below the diagonal: parcel_js.hmr uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.path, so a change to parcel_core.path can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.path.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.location, so a change to parcel_core.location can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.location.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.target, so a change to parcel_core.target can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.target.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.dependency.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel_js.transformer uses parcel_core.asset, so a change to parcel_core.asset can break parcel_js.transformer, while a change to parcel_js.transformer can't break parcel_core.asset.
Position
Below the diagonal: parcel_js.transformer uses a module listed above it, which is the healthy direction.
parcel.bundler.bundle_roots uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel.bundler.bundle_roots, while a change to parcel.bundler.bundle_roots can't break parcel_core.bundle.
Position
Below the diagonal: parcel.bundler.bundle_roots uses a module listed above it, which is the healthy direction.
parcel.bundler.bundle_roots uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel.bundler.bundle_roots, while a change to parcel.bundler.bundle_roots can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel.bundler.bundle_roots uses a module listed above it, which is the healthy direction.
parcel_core uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_core, while a change to parcel_core can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_core uses a module listed above it, which is the healthy direction.
parcel_core uses parcel_core.options, so a change to parcel_core.options can break parcel_core, while a change to parcel_core can't break parcel_core.options.
Position
Below the diagonal: parcel_core uses a module listed above it, which is the healthy direction.
parcel_core uses parcel_core.config, so a change to parcel_core.config can break parcel_core, while a change to parcel_core can't break parcel_core.config.
Position
Below the diagonal: parcel_core uses a module listed above it, which is the healthy direction.
parcel_core uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core, while a change to parcel_core can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_core uses a module listed above it, which is the healthy direction.
parcel_core.content uses parcel_core.path, so a change to parcel_core.path can break parcel_core.content, while a change to parcel_core.content can't break parcel_core.path.
Position
Below the diagonal: parcel_core.content uses a module listed above it, which is the healthy direction.
parcel_core.content uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_core.content, while a change to parcel_core.content can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_core.content uses a module listed above it, which is the healthy direction.
parcel_core.content uses parcel_core.options, so a change to parcel_core.options can break parcel_core.content, while a change to parcel_core.content can't break parcel_core.options.
Position
Below the diagonal: parcel_core.content uses a module listed above it, which is the healthy direction.
parcel_core.content uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_core.content, while a change to parcel_core.content can't break parcel_core.bundle.
Position
Below the diagonal: parcel_core.content uses a module listed above it, which is the healthy direction.
parcel_core.content uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.content, while a change to parcel_core.content can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_core.content uses a module listed above it, which is the healthy direction.
parcel_core.resolver uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.resolver, while a change to parcel_core.resolver can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.resolver uses a module listed above it, which is the healthy direction.
parcel_core.resolver uses parcel_core.context, so a change to parcel_core.context can break parcel_core.resolver, while a change to parcel_core.resolver can't break parcel_core.context.
Position
Below the diagonal: parcel_core.resolver uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.path, so a change to parcel_core.path can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.path.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.location, so a change to parcel_core.location can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.location.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.options, so a change to parcel_core.options can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.options.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.dependency.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.asset, so a change to parcel_core.asset can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.asset.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.config, so a change to parcel_core.config can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.config.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_core.transformer uses parcel_core.context, so a change to parcel_core.context can break parcel_core.transformer, while a change to parcel_core.transformer can't break parcel_core.context.
Position
Below the diagonal: parcel_core.transformer uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.path, so a change to parcel_core.path can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.path.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.location, so a change to parcel_core.location can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.location.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.bundle.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.dependency.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.asset, so a change to parcel_core.asset can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.asset.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel_js.packager.rsc uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_js.packager.rsc, while a change to parcel_js.packager.rsc can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_js.packager.rsc uses a module listed above it, which is the healthy direction.
parcel uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel, while a change to parcel can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel uses a module listed above it, which is the healthy direction.
parcel uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel, while a change to parcel can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel uses a module listed above it, which is the healthy direction.
parcel.bundler.optimizer uses parcel_core.options, so a change to parcel_core.options can break parcel.bundler.optimizer, while a change to parcel.bundler.optimizer can't break parcel_core.options.
Position
Below the diagonal: parcel.bundler.optimizer uses a module listed above it, which is the healthy direction.
parcel.bundler.optimizer uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel.bundler.optimizer, while a change to parcel.bundler.optimizer can't break parcel_core.bundle.
Position
Below the diagonal: parcel.bundler.optimizer uses a module listed above it, which is the healthy direction.
parcel.bundler.optimizer uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel.bundler.optimizer, while a change to parcel.bundler.optimizer can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel.bundler.optimizer uses a module listed above it, which is the healthy direction.
parcel.bundler.optimizer uses parcel.bundler.bundle_roots, so a change to parcel.bundler.bundle_roots can break parcel.bundler.optimizer, while a change to parcel.bundler.optimizer can't break parcel.bundler.bundle_roots.
Position
Below the diagonal: parcel.bundler.optimizer uses a module listed above it, which is the healthy direction.
parcel.bundler.optimizer uses parcel_core.content, so a change to parcel_core.content can break parcel.bundler.optimizer, while a change to parcel.bundler.optimizer can't break parcel_core.content.
Position
Below the diagonal: parcel.bundler.optimizer uses a module listed above it, which is the healthy direction.
parcel.bundler.reachability uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel.bundler.reachability, while a change to parcel.bundler.reachability can't break parcel_core.dependency.
Position
Below the diagonal: parcel.bundler.reachability uses a module listed above it, which is the healthy direction.
parcel.bundler.reachability uses parcel_core.asset, so a change to parcel_core.asset can break parcel.bundler.reachability, while a change to parcel.bundler.reachability can't break parcel_core.asset.
Position
Below the diagonal: parcel.bundler.reachability uses a module listed above it, which is the healthy direction.
parcel.bundler.reachability uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel.bundler.reachability, while a change to parcel.bundler.reachability can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel.bundler.reachability uses a module listed above it, which is the healthy direction.
parcel.bundler.reachability uses parcel.bundler.bundle_roots, so a change to parcel.bundler.bundle_roots can break parcel.bundler.reachability, while a change to parcel.bundler.reachability can't break parcel.bundler.bundle_roots.
Position
Below the diagonal: parcel.bundler.reachability uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.path, so a change to parcel_core.path can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.path.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.location, so a change to parcel_core.location can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.location.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.target, so a change to parcel_core.target can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.target.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.dependency.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.asset, so a change to parcel_core.asset can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.asset.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.context, so a change to parcel_core.context can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.context.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_css.transformer uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_css.transformer, while a change to parcel_css.transformer can't break parcel_core.transformer.
Position
Below the diagonal: parcel_css.transformer uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.location, so a change to parcel_core.location can break parcel_html, while a change to parcel_html can't break parcel_core.location.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.target, so a change to parcel_core.target can break parcel_html, while a change to parcel_html can't break parcel_core.target.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_html, while a change to parcel_html can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_html, while a change to parcel_html can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.options, so a change to parcel_core.options can break parcel_html, while a change to parcel_html can't break parcel_core.options.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_html, while a change to parcel_html can't break parcel_core.bundle.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_html, while a change to parcel_html can't break parcel_core.dependency.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.asset, so a change to parcel_core.asset can break parcel_html, while a change to parcel_html can't break parcel_core.asset.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_html, while a change to parcel_html can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.context, so a change to parcel_core.context can break parcel_html, while a change to parcel_html can't break parcel_core.context.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.content, so a change to parcel_core.content can break parcel_html, while a change to parcel_html can't break parcel_core.content.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_html uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_html, while a change to parcel_html can't break parcel_core.transformer.
Position
Below the diagonal: parcel_html uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_image, while a change to parcel_image can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_image, while a change to parcel_image can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.options, so a change to parcel_core.options can break parcel_image, while a change to parcel_image can't break parcel_core.options.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_image, while a change to parcel_image can't break parcel_core.bundle.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.asset, so a change to parcel_core.asset can break parcel_image, while a change to parcel_image can't break parcel_core.asset.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.context, so a change to parcel_core.context can break parcel_image, while a change to parcel_image can't break parcel_core.context.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_image uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_image, while a change to parcel_image can't break parcel_core.transformer.
Position
Below the diagonal: parcel_image uses a module listed above it, which is the healthy direction.
parcel_js uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_js, while a change to parcel_js can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_js uses a module listed above it, which is the healthy direction.
parcel_js uses parcel_core.options, so a change to parcel_core.options can break parcel_js, while a change to parcel_js can't break parcel_core.options.
Position
Below the diagonal: parcel_js uses a module listed above it, which is the healthy direction.
parcel_js uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_js, while a change to parcel_js can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_js uses a module listed above it, which is the healthy direction.
parcel_js uses parcel_js.transformer, so a change to parcel_js.transformer can break parcel_js, while a change to parcel_js can't break parcel_js.transformer.
Position
Below the diagonal: parcel_js uses a module listed above it, which is the healthy direction.
parcel_js uses parcel_core.content, so a change to parcel_core.content can break parcel_js, while a change to parcel_js can't break parcel_core.content.
Position
Below the diagonal: parcel_js uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.path, so a change to parcel_core.path can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.path.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.reporter, so a change to parcel_core.reporter can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.reporter.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.options, so a change to parcel_core.options can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.options.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.bundle.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.context, so a change to parcel_core.context can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.context.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.resolver, so a change to parcel_core.resolver can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.resolver.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_abi.plugin uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_plugin_abi.plugin, while a change to parcel_plugin_abi.plugin can't break parcel_core.transformer.
Position
Below the diagonal: parcel_plugin_abi.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.path, so a change to parcel_core.path can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.path.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_highlight, so a change to parcel_highlight can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_highlight.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.target, so a change to parcel_core.target can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.target.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_highlight.js, so a change to parcel_highlight.js can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_highlight.js.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.reporter, so a change to parcel_core.reporter can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.reporter.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.options, so a change to parcel_core.options can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.options.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.bundle.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.dependency.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.asset, so a change to parcel_core.asset can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.asset.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.context, so a change to parcel_core.context can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.context.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.resolver, so a change to parcel_core.resolver can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.resolver.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel_plugin_js.plugin uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_plugin_js.plugin, while a change to parcel_plugin_js.plugin can't break parcel_core.transformer.
Position
Below the diagonal: parcel_plugin_js.plugin uses a module listed above it, which is the healthy direction.
parcel.bundler.internalization uses parcel_core.target, so a change to parcel_core.target can break parcel.bundler.internalization, while a change to parcel.bundler.internalization can't break parcel_core.target.
Position
Below the diagonal: parcel.bundler.internalization uses a module listed above it, which is the healthy direction.
parcel.bundler.internalization uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel.bundler.internalization, while a change to parcel.bundler.internalization can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel.bundler.internalization uses a module listed above it, which is the healthy direction.
parcel.bundler.internalization uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel.bundler.internalization, while a change to parcel.bundler.internalization can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel.bundler.internalization uses a module listed above it, which is the healthy direction.
parcel.bundler.internalization uses parcel.bundler.bundle_roots, so a change to parcel.bundler.bundle_roots can break parcel.bundler.internalization, while a change to parcel.bundler.internalization can't break parcel.bundler.bundle_roots.
Position
Below the diagonal: parcel.bundler.internalization uses a module listed above it, which is the healthy direction.
parcel.bundler.internalization uses parcel.bundler.reachability, so a change to parcel.bundler.reachability can break parcel.bundler.internalization, while a change to parcel.bundler.internalization can't break parcel.bundler.reachability.
Position
Below the diagonal: parcel.bundler.internalization uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel_core.location, so a change to parcel_core.location can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel_core.location.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel_core.options, so a change to parcel_core.options can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel_core.options.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel_core.asset, so a change to parcel_core.asset can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel_core.asset.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel.bundler.bundle_roots, so a change to parcel.bundler.bundle_roots can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel.bundler.bundle_roots.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel.bundler.style_order uses parcel.bundler.reachability, so a change to parcel.bundler.reachability can break parcel.bundler.style_order, while a change to parcel.bundler.style_order can't break parcel.bundler.reachability.
Position
Below the diagonal: parcel.bundler.style_order uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.location, so a change to parcel_core.location can break parcel_css, while a change to parcel_css can't break parcel_core.location.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.target, so a change to parcel_core.target can break parcel_css, while a change to parcel_css can't break parcel_core.target.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_css, while a change to parcel_css can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.diagnostic, so a change to parcel_core.diagnostic can break parcel_css, while a change to parcel_css can't break parcel_core.diagnostic.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.options, so a change to parcel_core.options can break parcel_css, while a change to parcel_css can't break parcel_core.options.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_css, while a change to parcel_css can't break parcel_core.bundle.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_css, while a change to parcel_css can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_core.content, so a change to parcel_core.content can break parcel_css, while a change to parcel_css can't break parcel_core.content.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_css uses parcel_css.transformer, so a change to parcel_css.transformer can break parcel_css, while a change to parcel_css can't break parcel_css.transformer.
Position
Below the diagonal: parcel_css uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.location, so a change to parcel_core.location can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.location.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.options, so a change to parcel_core.options can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.options.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.bundle.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.asset, so a change to parcel_core.asset can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.asset.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.context, so a change to parcel_core.context can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.context.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.content, so a change to parcel_core.content can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.content.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_html.xml uses parcel_core.transformer, so a change to parcel_core.transformer can break parcel_html.xml, while a change to parcel_html.xml can't break parcel_core.transformer.
Position
Below the diagonal: parcel_html.xml uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.path, so a change to parcel_core.path can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.path.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.target, so a change to parcel_core.target can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.target.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.options, so a change to parcel_core.options can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.options.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.bundle.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.asset, so a change to parcel_core.asset can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.asset.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_js.packager uses parcel_js.transformer, so a change to parcel_js.transformer can break parcel_js.packager, while a change to parcel_js.packager can't break parcel_js.transformer.
Position
Below the diagonal: parcel_js.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.location, so a change to parcel_core.location can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.location.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.target, so a change to parcel_core.target can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.target.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.bundle_graph, so a change to parcel_core.bundle_graph can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.bundle_graph.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.bundle, so a change to parcel_core.bundle can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.bundle.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.dependency, so a change to parcel_core.dependency can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.dependency.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.asset, so a change to parcel_core.asset can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.asset.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_core.asset_graph, so a change to parcel_core.asset_graph can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_core.asset_graph.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
parcel_css.packager uses parcel_css, so a change to parcel_css can break parcel_css.packager, while a change to parcel_css.packager can't break parcel_css.
Position
Below the diagonal: parcel_css.packager uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 50% · Weak · gated by D2, R2, 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
133
High / Critical
A03:2025 — Software Supply Chain Failures
32
High / Critical
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (2); Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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 — 82
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 — 736
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 — 112
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 17
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 65 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 — 65 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, 890 of 930 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 22 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 59 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .mjs, .cjs, .ts) and this repository declares a Cargo test suite (repository root, 119 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
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.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages-v3/rsc/src/server.tsx`, `plugin-swift/Examples/Sources/AsyncPlugin/AsyncPlugin.swift`, `plugin-swift/Examples/Sources/CustomContentTransformer/CustomContentTransformer.swift`, `plugin-swift/Examples/Sources/CustomNamer/CustomNamer.swift`, `plugin-swift/Examples/Sources/CustomOptimizer/CustomOptimizer.swift`, … (+9 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.
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 plugin-swift/Sources/ParcelPlugin/Plugin.swift, 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.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Rust, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Rust, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, 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. The .NET and Node.js version checks are a different kind and still publish.
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.
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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
107 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Evaluator::eval at 96. A further 10 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being parcel_html::jsx::jsx_attr_name at 366 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/core/src/asset.rs (AssetType::from_mime at 39), crates/core/src/dependency.rs (ExportsCondition::try_from at 19), crates/highlight/src/css.rs (parcel_highlight::css::walk at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Evaluator::eval (cyclomatic 96), DependencyCollector::visit_element (cyclomatic 86), parcel_html::optimize::optimize (cyclomatic 69). — 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 6 together lifts Cyclomatic Complexity from 5.5 to about 6.1/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.
+ 85 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 24 bodies over 60 down to 60 or less in Cognitive Complexity — start with DependencyCollector::fold_call_expr (cognitive 211), DependencyCollector::visit_element (cognitive 188), parcel_js::packager::dependencies::asset_dependencies (cognitive 179). — 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 24 together lifts Cognitive Complexity from 2.0 to about 4.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.5 / 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 25 FileTooLong finding(s) in God Classes — start with lib.rs (4), plugin.rs (2), mod.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 20 FunctionTooLong finding(s) in God Classes — start with mod.rs (3), style_order.rs (2), rsc.rs (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 16 MethodTooLong finding(s) in God Classes — start with lib.rs (2), dependencies.rs, bundler.rs. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
61 duplicated block group(s) detected. A further 60 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Edited copy of a member (13 corresponding lines) · ×9crates/parcel-plugin-abi/src/bundle.rs:213
+ 54 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with arena.rs (2), bundle.rs, dependencies.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with dependency_collector.rs (2), memory.rs, packager.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with asset.rs, macos.rs, path.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
36 production modules (Cargo+npm+Go+SwiftPM), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 27 of the 36 (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: browserslist-rs · ×6
Unstable project parcel-js
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Unstable project parcel-js finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with arena.rs, server.rs, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 22 tests. Measured on the JavaScript/TypeScript suite only — at least 59 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
19 outdated, 0 yanked direct Cargo dependencies. 82 of 84 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: bitflags · ×19
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 589 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 25 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, package.json and a Go module (REDACTED/go.sum), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 42 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs (4), mod.rs (3), dependencies.rs (2). — One of this dimension's main actionable groups (42 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 Factor2.2 / 10Critical✓ 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.
145 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/parcel-resolver/src/lib.rs. Counted over 185 of the 210 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
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
55 deducted task-comment markers across 90890 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 53 TodoComment finding(s) in Explicit Debt — start with lib.rs (11), env_replacer.rs (7), entry.rs (4). — One of this dimension's main actionable groups (53 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with serialize_html.rs (2). — One of this dimension's main actionable groups (2 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. 24 document(s) read across 15 unit(s).
Documentation: no build, run or usage examplepackages-v3/babel/README.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
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).
146 finding(s): 0 critical, 66 high, 4 medium, 76 low. 59 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `crates/parcel-plugin-abi/plugin.h`, `crates/parcel/src/macos.rs` (line 36, line 79, line 90, …), `packages-v3/rsc/src/server.tsx` (line 16, lines 17–18, line 19, …), `plugin-go/plugin.h`, `plugin-swift/Sources/CParcelABI/include/plugin.h` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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).
No action in Static Analysis (SAST) — all 59 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (59 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
3 of 185 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/js/src/transformer/typeof_replacer.rs. Counted over 185 of the 210 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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 any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 15 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
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.
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. 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. — packages-v3/create-parcel/templates/react-client/src/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>. (×2) — packages-v3/create-parcel/templates/react-server/src/Page.tsx:10, packages-v3/create-parcel/templates/vanilla/src/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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.
This repository serves requests — a server (Server::new(listener) (crates/parcel/src/server.rs:210) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — crates/parcel/src/server.rs:210
What to do
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
README.md names Parcel 2, but the manifest declares `parcel` ^3.0.0-alpha.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:31
What to do
Reconcile the README with reality: README.md names Parcel 2, but the manifest declares `parcel` ^3.0.0-alpha.0.
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 · Observability4.5 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/dev-dep-resolver`, `crates/parcel`, `packages-v3/create-parcel`, `packages-v3/create-parcel/templates/react-server`, `plugin-swift`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, `cargo`, `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:8
What to do
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `npm`, `cargo`, `gomod` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.readFileSync` in `loadFile` 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-v3/less/src/LessTransformer.ts:118, packages-v3/less/src/LessTransformer.ts:134
`fs.readFileSync` in `findConfig` 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-v3/postcss/src/PostCSSTransformer.ts:97, packages-v3/posthtml/src/PostHTMLTransformer.ts:80
`fs.readFileSync` in `loadConfigFile` 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-v3/postcss/src/PostCSSTransformer.ts:131, packages-v3/posthtml/src/PostHTMLTransformer.ts:114
`nativeFS.readFileSync` in `callback to map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages-v3/stylus/src/StylusTransformer.ts:167
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 Safety4.8 / 10Weak✓ 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.
21 typed · 23 plain JS — the untyped files are REDACTED, crates/js/src/runtime.js, crates/js/src/runtime_modules/esmodule-helpers.js, crates/js/src/runtime_modules/mdx-components.jsx, crates/js/src/runtime_modules/react-refresh-runtime.development.js, crates/js/src/runtime_modules/react-refresh.js (+17 more). 0 production file(s) opt out entirely with @ts-nocheck · 6 @ts-ignore suppression(s).
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
REDACTED:25 · crates/js/src/runtime.js:6 — the two spans are one implementation copied and then locally edited — 710 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:25
packages-v3/postcss/src/PostCSSTransformer.ts:21 · packages-v3/posthtml/src/PostHTMLTransformer.ts:22 — the two spans are one implementation copied and then locally edited — 419 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-v3/postcss/src/PostCSSTransformer.ts:21
crates/plugin-js/builtin-src/path-win32.js:235 · crates/plugin-js/builtin-src/path-win32.js:355 — 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. — crates/plugin-js/builtin-src/path-win32.js:235
crates/plugin-js/builtin-src/path-win32.js:997 · crates/plugin-js/builtin-src/path-win32.js:1147 — 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. — crates/plugin-js/builtin-src/path-win32.js:997
crates/plugin-js/builtin-src/path-win32.js:811 · crates/plugin-js/builtin-src/path-win32.js:1076 — 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. — crates/plugin-js/builtin-src/path-win32.js:811
gulpfile.js:54 · gulpfile.js:77 — the two spans are one implementation copied and then locally edited — 110 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. — gulpfile.js:54
REDACTED:108 · crates/js/src/runtime_modules/esmodule-helpers.js:9 — 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:108
crates/js/src/runtime_modules/react-refresh-runtime.development.js:310 · crates/js/src/runtime_modules/react-refresh-runtime.development.js:326 — the two spans are one implementation copied and then locally edited — 66 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. — crates/js/src/runtime_modules/react-refresh-runtime.development.js:310
crates/js/src/runtime_modules/react-refresh.js:173 · crates/js/src/runtime_modules/react-refresh.js:191 — the two spans are one implementation copied and then locally edited — 76 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. — crates/js/src/runtime_modules/react-refresh.js:173
crates/plugin-js/builtin-src/path-win32.js:655 · crates/plugin-js/builtin-src/path-win32.js:671 — 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. — crates/plugin-js/builtin-src/path-win32.js:655
packages-v3/rsc/src/node.tsx:59 · packages-v3/rsc/src/server.tsx:101 — 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. — packages-v3/rsc/src/node.tsx:59
REDACTED:611 · REDACTED:1123 — 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. — REDACTED:611
crates/plugin-js/builtin-src/native-zlib/index.js:198 · crates/plugin-js/builtin-src/native-zlib/index.js:205 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — crates/plugin-js/builtin-src/native-zlib/index.js:198
crates/plugin-js/buildBuiltins.cjs:437 · crates/plugin-js/buildBuiltins.cjs:450 — 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. — crates/plugin-js/buildBuiltins.cjs:437
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.
crates/plugin-js/builtin-src/assert/index.js:9 imports assert/build/assert.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — crates/plugin-js/builtin-src/assert/index.js:9
packages-v3/stylus/src/StylusTransformer.ts:6 imports stylus/lib/parser, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages-v3/stylus/src/StylusTransformer.ts:6
packages-v3/stylus/src/StylusTransformer.ts:7 imports stylus/lib/visitor/deps-resolver, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages-v3/stylus/src/StylusTransformer.ts:7
packages-v3/stylus/src/StylusTransformer.ts:8 imports stylus/lib/nodes/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages-v3/stylus/src/StylusTransformer.ts:8
packages-v3/stylus/src/StylusTransformer.ts:9 imports stylus/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages-v3/stylus/src/StylusTransformer.ts:9
packages-v3/stylus/src/StylusTransformer.ts:10 imports stylus/lib/visitor/evaluator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages-v3/stylus/src/StylusTransformer.ts:10
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
normalize has cyclomatic complexity 48 and cognitive complexity 92; 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. — crates/plugin-js/builtin-src/path-win32.js:339
resolve has cyclomatic complexity 46 and cognitive complexity 108; 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. — crates/plugin-js/builtin-src/path-win32.js:179
relative has cyclomatic complexity 42 and cognitive complexity 67; 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. — crates/plugin-js/builtin-src/path-win32.js:599
parse has cyclomatic complexity 40 and cognitive complexity 71; 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. — crates/plugin-js/builtin-src/path-win32.js:1051
assetPanel has cyclomatic complexity 31 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. — crates/parcel/src/analyzer/client.js:1364
dirname has cyclomatic complexity 27 and cognitive complexity 56; 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. — crates/plugin-js/builtin-src/path-win32.js:792
basename has cyclomatic complexity 23 and cognitive complexity 49; 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. — crates/plugin-js/builtin-src/path-win32.js:888
join has cyclomatic complexity 23 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. — crates/plugin-js/builtin-src/path-win32.js:495
normalizeString has cyclomatic complexity 20 and cognitive complexity 49; 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. — crates/plugin-js/builtin-src/path-win32.js:81
evaluate has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/model.mjs:115
(anonymous) has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/js/src/runtime_modules/react-refresh-runtime.development.js:267
showTooltip has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/parcel/src/analyzer/client.js:747
readPackage has cyclomatic complexity 18 and cognitive complexity 28; 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. — crates/plugin-js/buildBuiltins.cjs:254
validate has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/model.mjs:282
extname has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/plugin-js/builtin-src/path-win32.js:975
bestCandidate has cyclomatic complexity 17 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/model.mjs:245
handleMessage has cyclomatic complexity 17 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:545
onCommitFiberRoot has cyclomatic complexity 16 and cognitive complexity 18; 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. — crates/js/src/runtime_modules/react-refresh-runtime.development.js:196
finalize has cyclomatic complexity 15 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. — crates/parcel/src/analyzer/client.js:168
prepare has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/model.mjs:24
(anonymous) has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-v3/stylus/src/StylusTransformer.ts:127
add has cyclomatic complexity 14 and cognitive complexity 18; 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. — crates/plugin-js/buildBuiltins.cjs:367
layout has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/parcel/src/analyzer/client.js:390
loadFile has cyclomatic complexity 13 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-v3/less/src/LessTransformer.ts:79
(anonymous) has cyclomatic complexity 13 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/parcel/src/analyzer/client.js:2
buildBuiltins has cyclomatic complexity 13 and cognitive complexity 19; 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. — crates/plugin-js/buildBuiltins.cjs:526
render has cyclomatic complexity 13 and cognitive complexity 18; 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. — crates/parcel/src/analyzer/client.js:464
isLikelyComponentType has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/js/src/runtime_modules/react-refresh-runtime.development.js:232
fixtures has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/graphs.mjs:34
visit has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/plugin-js/buildBuiltins.cjs:172
hmrApply has cyclomatic complexity 12 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:912
parcelRequire has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:34
link has cyclomatic complexity 12 and cognitive complexity 18; 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. — crates/js/src/tla-runtime.js:148
evaluate has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — crates/js/src/tla-runtime.js:38
transform has cyclomatic complexity 12 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 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-v3/postcss/src/PostCSSTransformer.ts:25
validateOutput has cyclomatic complexity 11 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/plugin-js/buildBuiltins.cjs:486
generated has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/bundle-optimizer-prototype/graphs.mjs:108
fitModels has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/compression-measurement/measure.mjs:144
toNamespacedPath has cyclomatic complexity 11 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 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. — crates/plugin-js/builtin-src/path-win32.js:757
isReactRefreshBoundary has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — crates/js/src/runtime_modules/react-refresh.js:128
Do you agree with this assessment?
R3 · Large Files5.2 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
crates/parcel/src/analyzer/client.js has 1623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — crates/parcel/src/analyzer/client.js:1
crates/plugin-js/builtin-src/path-win32.js has 1115 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — crates/plugin-js/builtin-src/path-win32.js:1
REDACTED has 1056 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages-v3/plugin/src/types.ts has 796 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-v3/plugin/src/types.ts:1
crates/plugin-js/buildBuiltins.cjs has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — crates/plugin-js/buildBuiltins.cjs: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 Coverage0.8 / 10Critical✓ 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.
crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1 imports './dir/*.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. — crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1
crates/parcel/tests/fixtures/url-imports/import-raw-import-meta-url/local-url.js:7 imports './invalid.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. — crates/parcel/tests/fixtures/url-imports/import-raw-import-meta-url/local-url.js:7
crates/parcel/tests/fixtures/workers/service-worker-import-meta-url/missing.js:1 imports './invalid.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. — crates/parcel/tests/fixtures/workers/service-worker-import-meta-url/missing.js:1
crates/parcel/tests/fixtures/workers/worker-import-meta-url/local-url.js:7 imports './invalid.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. — crates/parcel/tests/fixtures/workers/worker-import-meta-url/local-url.js:7
crates/parcel/tests/fixtures/workers/worker-import-meta-url/missing.js:1 imports './invalid.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. — crates/parcel/tests/fixtures/workers/worker-import-meta-url/missing.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. (×34) — crates/parcel/src/analyzer/client.js:1, crates/plugin-js/builtin-src/path-win32.js:1, REDACTED: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 crates/parcel/tests/fixtures/glob/glob-esm-library/index.js 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. — crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1
Do you agree with this assessment?
R7 · Dead Code7.4 / 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.
5 file(s) (~135 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-v3/create-parcel/templates/react-server
Unreachable from the 344 application, 10 tooling and 775 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (344 application, 10 tooling, 775 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 — crates/parcel/src/analyzer/client.js
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.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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.
3/15 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.
~0.4 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 2623 source line(s) of the 21 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages-v3/create-parcel/templates/react-client/src/index.tsx (1). 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 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 7 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 — 61 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 9% of this repository's production lines — rust (82,727 lines), c (4,451 lines), swift (2,989 lines), go (2,901 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-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, Rust, Swift, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 14 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 34 value object(s)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, JavaScript/TypeScript, Rust, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X12 Unreachable branch — X12 reached only 9% of this repository's production lines — rust (82,727 lines), c (4,451 lines), swift (2,989 lines), go (2,901 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 9% of this repository's production lines — rust (82,727 lines), c (4,451 lines), swift (2,989 lines), go (2,901 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 9% of this repository's production lines — rust (82,727 lines), c (4,451 lines), swift (2,989 lines), go (2,901 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 9% of this repository's production lines — rust (82,727 lines), c (4,451 lines), swift (2,989 lines), go (2,901 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 15% of this repository's production lines — rust (82,727 lines), c (4,451 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
TodoComment crates/tailwind/src/lib.rs:24— // TODO: skip if tailwind is not present? — 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 crates/tailwind/src/lib.rs:106— // TODO: error handling — 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 crates/plugin-js/tests/test_transform.rs:923— // TODO: expect "not a valid Parcel transformer plugin" once that is removed before GA. — 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 crates/plugin-js/src/encoding.rs:73— // TODO: other encodings — 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 crates/plugin-js/src/macros.rs:128— // TODO: invalidations — 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 crates/plugin-js/src/plugin.rs:193— // TODO: remove before GA. — 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 crates/parcel-resolver/src/lib.rs:337— // TODO: add file create above invalidation via fs — 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 crates/parcel-resolver/src/lib.rs:405— // // TODO: use the fs find_ancestor_file so we get file_create_above invalidation — 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 crates/parcel-resolver/src/lib.rs:615— // TODO: should this follow aliases?? — 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 crates/parcel-resolver/src/lib.rs:877— // TODO: track location of resolved field — 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 crates/parcel-resolver/src/lib.rs:1001— // TODO: Revert this in the next major version. — 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 crates/parcel-resolver/src/lib.rs:1089— // TODO: TypeScript only removes certain extensions here... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/parcel-resolver/src/lib.rs:1216— // TODO: should aliases apply to tsconfig paths?? — 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 crates/parcel-plugin-abi/src/tests.rs:52— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/js/src/hmr.rs:199— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/js/src/transformer/dependency_collector.rs:2740— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/js/src/packager/tree_shake.rs:652— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/js/src/packager/tree_shake.rs:667— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/entry.rs:244— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/entry.rs:246— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/parcel/src/bundler.rs:265— // TODO: other environment properties? — 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 crates/parcel/src/bundler.rs:467— // TODO: other environment properties? — 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 crates/js/src/hmr.rs:137— // TODO: I think we don't need this anymore. Was added in https://github.com/parcel-bundler/parcel/pull/4311
TodoComment crates/js/src/hmr.rs:173— // TODO: only changed ones?? — 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 crates/js/src/transformer/collect.rs:346— // TODO: optimize `require('foo').bar` / `require('foo').bar()` as well — 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.
Hotspot: crates/js/src/transformer/plugin.rs crates/js/src/transformer/plugin.rs:329— crates/js/src/transformer/plugin.rs changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in parcel_js::transformer::plugin::config at line 329. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/transformer/plugin.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/bundler.rs crates/parcel/src/bundler.rs:173— crates/parcel/src/bundler.rs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in DefaultBundler::bundle at line 173. 2 of those changes were fix/bug commits, and the other 26 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/bundler.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/transformer/mod.rs crates/js/src/transformer/mod.rs:459— crates/js/src/transformer/mod.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in parcel_js::transformer::transform_to_ast at line 459. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/transformer/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/packager/dependencies.rs crates/js/src/packager/dependencies.rs:237— crates/js/src/packager/dependencies.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in parcel_js::packager::dependencies::asset_dependencies at line 237. 7 of those changes were fix/bug commits, and the other 17 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/packager/dependencies.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/transformer/dependency_collector.rs crates/js/src/transformer/dependency_collector.rs:750— crates/js/src/transformer/dependency_collector.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in DependencyCollector::fold_call_expr at line 750. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/transformer/dependency_collector.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/main.rs crates/parcel/src/main.rs:145— crates/parcel/src/main.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in parcel::parse_args at line 145. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/html/src/dependencies.rs crates/html/src/dependencies.rs:243— crates/html/src/dependencies.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 86 in DependencyCollector::visit_element at line 243. 2 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/html/src/dependencies.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/lib.rs crates/core/src/lib.rs:428— crates/core/src/lib.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in parcel_core::bundle_and_package at line 428. 3 of those changes were fix/bug commits, and the other 23 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/core/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/asset_graph.rs crates/core/src/asset_graph.rs:238— crates/core/src/asset_graph.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in AssetGraphBuilder::build_with_changes at line 238. 3 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/core/src/asset_graph.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/packager/mod.rs crates/js/src/packager/mod.rs:69— crates/js/src/packager/mod.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in JsContent::package_app at line 69. 6 of those changes were fix/bug commits, and the other 24 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/packager/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/resolver.rs crates/parcel/src/resolver.rs:24— crates/parcel/src/resolver.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in DefaultResolver::resolve at line 24. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/resolver.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/html/src/lib.rs crates/html/src/lib.rs:718— crates/html/src/lib.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in parcel_html::prepare_to_package at line 718. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/html/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:34— REDACTED changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in dev-runtime.parcelRequire at line 34. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/css/src/packager.rs crates/css/src/packager.rs:457— crates/css/src/packager.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in parcel_css::packager::inline at line 457. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/css/src/packager.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/bundler/optimizer.rs crates/parcel/src/bundler/optimizer.rs:404— crates/parcel/src/bundler/optimizer.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in parcel::bundler::optimizer::optimize at line 404. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/bundler/optimizer.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/bundler/style_order.rs crates/parcel/src/bundler/style_order.rs:153— crates/parcel/src/bundler/style_order.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in parcel::bundler::style_order::segment 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/bundler/style_order.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/lib.rs crates/parcel/src/lib.rs:230— crates/parcel/src/lib.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in parcel::run at line 230. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/html/src/package.rs crates/html/src/package.rs:168— crates/html/src/package.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in parcel_html::package::insert_bundle_references at line 168. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/html/src/package.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/transformer/modules.rs crates/js/src/transformer/modules.rs:335— crates/js/src/transformer/modules.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Esm2Cjs::visit_mut_module at line 335. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/transformer/modules.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/server.rs crates/parcel/src/server.rs:252— crates/parcel/src/server.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in parcel::server::serve_file at line 252. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/server.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/entry.rs crates/core/src/entry.rs:103— crates/core/src/entry.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in EntryResolver::resolve_file_entry at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/core/src/entry.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/css/src/transformer.rs crates/css/src/transformer.rs:110— crates/css/src/transformer.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CssTransformer::transform at line 110. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/css/src/transformer.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/parcel/src/plugin_factory.rs crates/parcel/src/plugin_factory.rs:58— crates/parcel/src/plugin_factory.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in DefaultPluginFactory::transformer at line 58. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/parcel/src/plugin_factory.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/hmr.rs crates/js/src/hmr.rs:62— crates/js/src/hmr.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in parcel_js::hmr::get_hmr_update at line 62. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/hmr.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/js/src/packager/synthetic.rs crates/js/src/packager/synthetic.rs:183— crates/js/src/packager/synthetic.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SyntheticAsset::write_content at line 183. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 22:58:23 -08:00' --until='2026-11-10 22:58:23 -08:00' --full-history --no-merges -- crates/js/src/packager/synthetic.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
+ 17 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×34
No test reaches this file crates/parcel/src/analyzer/client.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 crates/plugin-js/builtin-src/path-win32.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/js/src/runtime_modules/react-refresh-runtime.development.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 crates/js/src/tla-runtime.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-v3/stylus/src/StylusTransformer.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/js/src/runtime.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 crates/js/src/runtime_modules/react-refresh.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-v3/rsc/src/server.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 REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-v3/postcss/src/PostCSSTransformer.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-v3/less/src/LessTransformer.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-v3/posthtml/src/PostHTMLTransformer.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-v3/rsc/src/runtime-helpers.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-v3/rsc/src/node.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-v3/rsc/src/client.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 crates/plugin-js/builtin-src/assert/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-v3/babel/src/BabelTransformer.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-v3/create-parcel/templates/react-server/src/client.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 crates/tailwind/src/compile.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-v3/create-parcel/scripts/update-template-versions.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/js/src/runtime_modules/esmodule-helpers.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-v3/create-parcel/templates/react-server/src/Page.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-v3/rsc/src/runtime-server.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 crates/js/src/runtime_modules/mdx-components.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.
FileTooLong: src/plugin.rs crates/plugin-js/src/plugin.rs— FileTooLong — 1365 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 865 over it, 2.73× 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: analyzer/client.js crates/parcel/src/analyzer/client.js— FileTooLong — 1288 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 788 over it, 2.58× 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: transformer/dependency_collector.rs crates/js/src/transformer/dependency_collector.rs— FileTooLong — 1287 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: DependencyCollector (6 blocks, 334-1980). The bar is 500 significant lines; this is 787 over it, 2.57× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/parcel-plugin/src/lib.rs— FileTooLong — 1232 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 732 over it, 2.46× 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/packager.rs crates/css/src/packager.rs— FileTooLong — 983 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 483 over it, 1.97× 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/asset_graph.rs crates/core/src/asset_graph.rs— FileTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 423 over it, 1.85× 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: packager/mod.rs crates/js/src/packager/mod.rs— FileTooLong — 912 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 412 over it, 1.82× 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: transformer/mod.rs crates/js/src/transformer/mod.rs— FileTooLong — 885 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 385 over it, 1.77× 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: packager/rsc.rs crates/js/src/packager/rsc.rs— FileTooLong — 842 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 342 over it, 1.68× 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: bundler/optimizer.rs crates/parcel/src/bundler/optimizer.rs— FileTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 326 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/parcel-resolver/src/lib.rs— FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: ResolveRequest (2 blocks, 426-1367). The bar is 500 significant lines; this is 291 over it, 1.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/oxvg.rs crates/html/src/oxvg.rs— FileTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 222 over it, 1.44× 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: transformer/collect.rs crates/js/src/transformer/collect.rs— FileTooLong — 721 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: Collect (5 blocks, 62-1105). The bar is 500 significant lines; this is 221 over it, 1.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/html/src/lib.rs— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 209 over it, 1.42× 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 — 703 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 203 over it, 1.41× 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: builtin-src/path-win32.js crates/plugin-js/builtin-src/path-win32.js— FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 191 over it, 1.38× 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/dependencies.rs crates/html/src/dependencies.rs— FileTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: DependencyCollector (2 blocks, 172-886). The bar is 500 significant lines; this is 184 over it, 1.37× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/macros/src/lib.rs— FileTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 161 over it, 1.32× 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/diagnostic.rs crates/core/src/diagnostic.rs— FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 136 over it, 1.27× 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/package_json.rs crates/parcel-resolver/src/package_json.rs— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: PackageJson (2 blocks, 94-812). The bar is 500 significant lines; this is 128 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/server.rs crates/parcel/src/server.rs— FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 101 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/crypto.rs crates/plugin-js/src/crypto.rs— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 68 over it, 1.14× 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/fs.rs crates/plugin-js/src/fs.rs— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 62 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: src/entry.rs crates/core/src/entry.rs— FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 43 over it, 1.09× 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/plugin.rs crates/parcel-plugin-abi/src/plugin.rs— FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: CPlugin (8 blocks, 258-830). The bar is 500 significant lines; this is 19 over it, 1.04× 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.
FunctionTooLong: parcel_js::transformer::transform_to_ast crates/js/src/transformer/mod.rs:459— FunctionTooLong — parcel_js::transformer::transform_to_ast runs 314 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 214 over it, 3.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: parcel_html::optimize::optimize crates/html/src/optimize.rs:68— FunctionTooLong — parcel_html::optimize::optimize runs 292 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× 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: parcel_js::packager::dependencies::asset_dependencies crates/js/src/packager/dependencies.rs:237— FunctionTooLong — parcel_js::packager::dependencies::asset_dependencies runs 224 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel::analyzer::write_report crates/parcel/src/analyzer/mod.rs:117— FunctionTooLong — parcel::analyzer::write_report runs 215 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_js::transformer::plugin::config crates/js/src/transformer/plugin.rs:329— FunctionTooLong — parcel_js::transformer::plugin::config runs 213 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: parcel_css::packager::inline crates/css/src/packager.rs:457— FunctionTooLong — parcel_css::packager::inline runs 202 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_html::jsx::to_component crates/html/src/jsx.rs:712— FunctionTooLong — parcel_html::jsx::to_component runs 198 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× 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: parcel::bundler::style_order::report_conflicts crates/parcel/src/bundler/style_order.rs:580— FunctionTooLong — parcel::bundler::style_order::report_conflicts runs 180 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel::parse_args crates/parcel/src/main.rs:145— FunctionTooLong — parcel::parse_args runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: parcel_core::bundle_and_package crates/core/src/lib.rs:428— FunctionTooLong — parcel_core::bundle_and_package runs 156 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_html::package::insert_bundle_references crates/html/src/package.rs:168— FunctionTooLong — parcel_html::package::insert_bundle_references runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: client.assetPanel crates/parcel/src/analyzer/client.js:1364— FunctionTooLong — assetPanel runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: parcel_js::packager::write_runtime_globals crates/js/src/packager/mod.rs:1022— FunctionTooLong — parcel_js::packager::write_runtime_globals runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel::bundler::style_order::segment crates/parcel/src/bundler/style_order.rs:153— FunctionTooLong — parcel::bundler::style_order::segment runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: parcel_js::hmr::get_hmr_update crates/js/src/hmr.rs:62— FunctionTooLong — parcel_js::hmr::get_hmr_update runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_html::srcset::parse_srcset crates/html/src/srcset.rs:50— FunctionTooLong — parcel_html::srcset::parse_srcset runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_html::serialize_html::can_omit_end_tag crates/html/src/serialize_html.rs:396— FunctionTooLong — parcel_html::serialize_html::can_omit_end_tag runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_js::packager::rsc::write_resources crates/js/src/packager/rsc.rs:940— FunctionTooLong — parcel_js::packager::rsc::write_resources runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_core::packaging::package_bundles crates/core/src/packaging.rs:253— FunctionTooLong — parcel_core::packaging::package_bundles runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parcel_js::packager::rsc::resolve_dependency crates/js/src/packager/rsc.rs:105— FunctionTooLong — parcel_js::packager::rsc::resolve_dependency runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DependencyCollector.visit_element crates/html/src/dependencies.rs:243— MethodTooLong — visit_element runs 326 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 226 over it, 3.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DefaultBundler.bundle crates/parcel/src/bundler.rs:173— MethodTooLong — bundle runs 303 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DependencyCollector.fold_call_expr crates/js/src/transformer/dependency_collector.rs:750— MethodTooLong — fold_call_expr runs 272 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AssetGraphBuilder.build_with_changes crates/core/src/asset_graph.rs:238— MethodTooLong — build_with_changes runs 211 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Evaluator.eval crates/macros/src/lib.rs:398— MethodTooLong — eval runs 196 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Esm2Cjs.visit_mut_module crates/js/src/transformer/modules.rs:335— MethodTooLong — visit_mut_module runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DefaultResolver.resolve crates/parcel/src/resolver.rs:24— MethodTooLong — resolve runs 182 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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.
MethodTooLong: JsTransformer.transform crates/js/src/transformer/plugin.rs:87— MethodTooLong — transform runs 181 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JsContent.package_app crates/js/src/packager/mod.rs:69— MethodTooLong — package_app runs 173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CssContent.package_impl crates/css/src/packager.rs:49— MethodTooLong — package_impl runs 170 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CssTransformer.transform crates/css/src/transformer.rs:110— MethodTooLong — transform runs 167 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ImageTransformer.transform crates/image/src/lib.rs:49— MethodTooLong — transform runs 141 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GlobResolver.resolve crates/parcel/src/glob_resolver.rs:18— MethodTooLong — resolve runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EntryResolver.resolve_file_entry crates/core/src/entry.rs:103— MethodTooLong — resolve_file_entry runs 116 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SyntheticAsset.write_content crates/js/src/packager/synthetic.rs:183— MethodTooLong — write_content runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BundleRoots.from_asset_graph crates/parcel/src/bundler/bundle_roots.rs:36— MethodTooLong — from_asset_graph runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
parcel_js::packager::dependencies::asset_dependencies (cognitive 179) crates/js/src/packager/dependencies.rs:237— parcel_js::packager::dependencies::asset_dependencies has cognitive complexity 179 (threshold 15). Drivers by points: if/else 41 (144 pts), match/switch 4 (15 pts), loops 3 (11 pts), boolean chains 9 (nesting depth added 122). 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.
parcel_js::transformer::plugin::config (cognitive 147) crates/js/src/transformer/plugin.rs:329— parcel_js::transformer::plugin::config has cognitive complexity 147 (threshold 15). Drivers by points: if/else 39 (103 pts), match/switch 8 (27 pts), loops 3 (9 pts), boolean chains 8 (nesting depth added 89). 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.
parcel_js::transformer::transform_to_ast (cognitive 87) crates/js/src/transformer/mod.rs:459— parcel_js::transformer::transform_to_ast has cognitive complexity 87 (threshold 15). Drivers by points: if/else 37 (59 pts), boolean chains 10, loops 5 (10 pts), match/switch 6 (8 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.
parcel_js::hmr::get_hmr_update (cognitive 37) crates/js/src/hmr.rs:62— parcel_js::hmr::get_hmr_update has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 5 (10 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::packager::write_runtime_globals (cognitive 30) crates/js/src/packager/mod.rs:1022— parcel_js::packager::write_runtime_globals has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 5, boolean chains 4, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::packager::rsc::resource_plan (cognitive 30) crates/js/src/packager/rsc.rs:313— parcel_js::packager::rsc::resource_plan has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (28 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.
parcel_js::transformer::dependency_collector::match_worker_type (cognitive 28) crates/js/src/transformer/dependency_collector.rs:1983— parcel_js::transformer::dependency_collector::match_worker_type has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 3 (9 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.
parcel_js::transformer::mdx::transform_js_code_block (cognitive 27) crates/js/src/transformer/mdx.rs:389— parcel_js::transformer::mdx::transform_js_code_block has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 3 (8 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::packager::rsc::write_resources (cognitive 26) crates/js/src/packager/rsc.rs:940— parcel_js::packager::rsc::write_resources has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 3 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::transformer::utils::match_require (cognitive 25) crates/js/src/transformer/utils.rs:126— parcel_js::transformer::utils::match_require has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (18 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
parcel_js::transformer::mdx::parse_code_block (cognitive 24) crates/js/src/transformer/mdx.rs:322— parcel_js::transformer::mdx::parse_code_block has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (24 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.
parcel_js::packager::rsc::resolve_dependency (cognitive 22) crates/js/src/packager/rsc.rs:105— parcel_js::packager::rsc::resolve_dependency has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::packager::rsc::server_actions (cognitive 18) crates/js/src/packager/rsc.rs:550— parcel_js::packager::rsc::server_actions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_js::packager::dependencies::bundle_dependencies (cognitive 17) crates/js/src/packager/dependencies.rs:27— parcel_js::packager::dependencies::bundle_dependencies has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (5 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.
parcel_js::packager::rsc::client_reference_bundles (cognitive 16) crates/js/src/packager/rsc.rs:414— parcel_js::packager::rsc::client_reference_bundles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundler::style_order::segment (cognitive 92) crates/parcel/src/bundler/style_order.rs:153— parcel::bundler::style_order::segment has cognitive complexity 92 (threshold 15). Drivers by points: if/else 16 (48 pts), loops 16 (31 pts), match/switch 2 (8 pts), boolean chains 5 (nesting depth added 53). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundler::style_order::report_conflicts (cognitive 80) crates/parcel/src/bundler/style_order.rs:580— parcel::bundler::style_order::report_conflicts has cognitive complexity 80 (threshold 15). Drivers by points: if/else 20 (48 pts), loops 12 (30 pts), boolean chains 2 (nesting depth added 46). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::analyzer::write_report (cognitive 59) crates/parcel/src/analyzer/mod.rs:117— parcel::analyzer::write_report has cognitive complexity 59 (threshold 15). Drivers by points: if/else 13 (32 pts), loops 12 (20 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundler::optimizer::optimize (cognitive 54) crates/parcel/src/bundler/optimizer.rs:404— parcel::bundler::optimizer::optimize has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 11 (13 pts), boolean chains 12 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::parse_args (cognitive 53) crates/parcel/src/main.rs:145— parcel::parse_args has cognitive complexity 53 (threshold 15). Drivers by points: if/else 22 (33 pts), match/switch 5 (12 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::run (cognitive 39) crates/parcel/src/lib.rs:230— parcel::run has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (30 pts), match/switch 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundler::resolve_bundle_dependencies (cognitive 39) crates/parcel/src/bundler.rs:687— parcel::bundler::resolve_bundle_dependencies has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 3 (7 pts), boolean chains 3 (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.
parcel::serve (cognitive 27) crates/parcel/src/lib.rs:89— parcel::serve has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 5 (11 pts), 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.
parcel::server::serve_file (cognitive 26) crates/parcel/src/server.rs:252— parcel::server::serve_file has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 3, loops 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.
parcel::bundle_report::attribute_bytes (cognitive 25) crates/parcel/src/bundle_report.rs:319— parcel::bundle_report::attribute_bytes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 5 (11 pts), match/switch 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.
parcel::bundle_report::bundle_report (cognitive 21) crates/parcel/src/bundle_report.rs:392— parcel::bundle_report::bundle_report has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::http::serve_connection (cognitive 21) crates/parcel/src/http.rs:154— parcel::http::serve_connection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 4 (9 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundler::optimizer::apply (cognitive 19) crates/parcel/src/bundler/optimizer.rs:670— parcel::bundler::optimizer::apply has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (8 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.
parcel::webmanifest::collect_resources (cognitive 18) crates/parcel/src/webmanifest.rs:70— parcel::webmanifest::collect_resources has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel::bundle_report::display_width (cognitive 16) crates/parcel/src/bundle_report.rs:486— parcel::bundle_report::display_width has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::package::insert_bundle_references (cognitive 164) crates/html/src/package.rs:168— parcel_html::package::insert_bundle_references has cognitive complexity 164 (threshold 15). Drivers by points: if/else 39 (122 pts), loops 8 (28 pts), match/switch 3 (10 pts), boolean chains 4 (nesting depth added 110). 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.
parcel_html::jsx::to_component (cognitive 75) crates/html/src/jsx.rs:712— parcel_html::jsx::to_component has cognitive complexity 75 (threshold 15). Drivers by points: if/else 29 (58 pts), match/switch 4 (9 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::srcset::parse_srcset (cognitive 64) crates/html/src/srcset.rs:50— parcel_html::srcset::parse_srcset has cognitive complexity 64 (threshold 15). Drivers by points: if/else 13 (35 pts), match/switch 5 (18 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::optimize::optimize (cognitive 62) crates/html/src/optimize.rs:68— parcel_html::optimize::optimize has cognitive complexity 62 (threshold 15). Drivers by points: if/else 15 (49 pts), boolean chains 10, match/switch 2 (3 pts) (nesting depth added 35). 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.
parcel_html::prepare_to_package (cognitive 59) crates/html/src/lib.rs:718— parcel_html::prepare_to_package has cognitive complexity 59 (threshold 15). Drivers by points: if/else 12 (45 pts), boolean chains 7, loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 37). 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.
parcel_html::serialize_html::can_omit_start_tag (cognitive 31) crates/html/src/serialize_html.rs:332— parcel_html::serialize_html::can_omit_start_tag has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 5 (11 pts), boolean chains 4 (nesting depth added 14). 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.
parcel_html::serialize_html::can_omit_end_tag (cognitive 29) crates/html/src/serialize_html.rs:396— parcel_html::serialize_html::can_omit_end_tag has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (13 pts), match/switch 2 (3 pts) (nesting depth added 8). 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.
parcel_html::oxvg::remove_unreferenced (cognitive 27) crates/html/src/oxvg.rs:108— parcel_html::oxvg::remove_unreferenced has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 5 (8 pts) (nesting depth added 13). Of this number, 22 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::jsx::jsx_attr_value (cognitive 22) crates/html/src/jsx.rs:495— parcel_html::jsx::jsx_attr_value has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3 (7 pts), boolean chains 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
parcel_html::dependencies::collect_dependencies (cognitive 21) crates/html/src/dependencies.rs:50— parcel_html::dependencies::collect_dependencies has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::oxvg::oxvg_node_to_parcel (cognitive 21) crates/html/src/oxvg.rs:328— parcel_html::oxvg::oxvg_node_to_parcel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::oxvg::parcel_node_to_oxvg (cognitive 20) crates/html/src/oxvg.rs:197— parcel_html::oxvg::parcel_node_to_oxvg has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), boolean chains 3, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
parcel_html::optimize::remove_whitespace (cognitive 17) crates/html/src/optimize.rs:665— parcel_html::optimize::remove_whitespace has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_html::xml::expand_html (cognitive 17) crates/html/src/xml.rs:37— parcel_html::xml::expand_html has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 3 (5 pts), match/switch 1 (3 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.
(anonymous)::resolve (cognitive 108) crates/plugin-js/builtin-src/path-win32.js:179— (anonymous)::resolve has cognitive complexity 108 (threshold 15). Drivers by points: if/else 27 (73 pts), boolean chains 18, loops 4 (16 pts), ternaries 1 (nesting depth added 58). 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.
(anonymous)::normalize (cognitive 92) crates/plugin-js/builtin-src/path-win32.js:339— (anonymous)::normalize has cognitive complexity 92 (threshold 15). Drivers by points: if/else 24 (54 pts), loops 5 (16 pts), boolean chains 15, ternaries 4 (6 pts), other 1 (nesting depth added 43). 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.
(anonymous)::parse (cognitive 71) crates/plugin-js/builtin-src/path-win32.js:1051— (anonymous)::parse has cognitive complexity 71 (threshold 15). Drivers by points: if/else 26 (49 pts), loops 4 (13 pts), boolean chains 9 (nesting depth added 32). 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.
(anonymous)::relative (cognitive 67) crates/plugin-js/builtin-src/path-win32.js:599— (anonymous)::relative has cognitive complexity 67 (threshold 15). Drivers by points: if/else 26 (47 pts), loops 7 (8 pts), boolean chains 6, ternaries 3 (6 pts) (nesting depth added 25). 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.
(anonymous)::dirname (cognitive 56) crates/plugin-js/builtin-src/path-win32.js:792— (anonymous)::dirname has cognitive complexity 56 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 4 (13 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 29). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
(anonymous)::normalizeString (cognitive 49) crates/plugin-js/builtin-src/path-win32.js:81— (anonymous)::normalizeString has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (39 pts), ternaries 1 (5 pts), boolean chains 4, loops 1 (nesting depth added 26). 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.
(anonymous)::basename (cognitive 49) crates/plugin-js/builtin-src/path-win32.js:888— (anonymous)::basename has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (43 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 26). 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.
(anonymous)::join (cognitive 41) crates/plugin-js/builtin-src/path-win32.js:495— (anonymous)::join has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (26 pts), loops 5 (9 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 17). 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.
(anonymous)::extname (cognitive 21) crates/plugin-js/builtin-src/path-win32.js:975— (anonymous)::extname has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, 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.
(anonymous)::injectIntoGlobalHook::onCommitFiberRoot (cognitive 18) crates/js/src/runtime_modules/react-refresh-runtime.development.js:196— (anonymous)::injectIntoGlobalHook::onCommitFiberRoot has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (8 pts), if/else 1 (nesting depth added 4). 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.
(anonymous)::isLikelyComponentType (cognitive 17) crates/js/src/runtime_modules/react-refresh-runtime.development.js:232— (anonymous)::isLikelyComponentType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 8). 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.
(anonymous)::normalize (cyclomatic 48) crates/plugin-js/builtin-src/path-win32.js:339— (anonymous)::normalize has cyclomatic complexity 48 (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.
(anonymous)::resolve (cyclomatic 46) crates/plugin-js/builtin-src/path-win32.js:179— (anonymous)::resolve has cyclomatic complexity 46 (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.
(anonymous)::relative (cyclomatic 42) crates/plugin-js/builtin-src/path-win32.js:599— (anonymous)::relative has cyclomatic complexity 42 (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.
(anonymous)::parse (cyclomatic 40) crates/plugin-js/builtin-src/path-win32.js:1051— (anonymous)::parse has cyclomatic complexity 40 (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.
(anonymous)::dirname (cyclomatic 27) crates/plugin-js/builtin-src/path-win32.js:792— (anonymous)::dirname has cyclomatic complexity 27 (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.
(anonymous)::join (cyclomatic 23) crates/plugin-js/builtin-src/path-win32.js:495— (anonymous)::join has cyclomatic complexity 23 (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.
(anonymous)::basename (cyclomatic 23) crates/plugin-js/builtin-src/path-win32.js:888— (anonymous)::basename has cyclomatic complexity 23 (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.
(anonymous)::normalizeString (cyclomatic 20) crates/plugin-js/builtin-src/path-win32.js:81— (anonymous)::normalizeString has cyclomatic complexity 20 (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.
(anonymous)::extname (cyclomatic 18) crates/plugin-js/builtin-src/path-win32.js:975— (anonymous)::extname has cyclomatic complexity 18 (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.
(anonymous)::injectIntoGlobalHook::onCommitFiberRoot (cyclomatic 16) crates/js/src/runtime_modules/react-refresh-runtime.development.js:196— (anonymous)::injectIntoGlobalHook::onCommitFiberRoot 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.
DependencyCollector::fold_call_expr (cognitive 211) crates/js/src/transformer/dependency_collector.rs:750— DependencyCollector::fold_call_expr has cognitive complexity 211 (threshold 15). Drivers by points: if/else 56 (177 pts), match/switch 6 (27 pts), boolean chains 7 (nesting depth added 142). 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.
DependencyCollector::visit_element (cognitive 188) crates/html/src/dependencies.rs:243— DependencyCollector::visit_element has cognitive complexity 188 (threshold 15). Drivers by points: if/else 61 (163 pts), boolean chains 13, match/switch 4 (9 pts), loops 1 (3 pts) (nesting depth added 109). 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.
DependencyCollector::fold_new_promise (cognitive 51) crates/js/src/transformer/dependency_collector.rs:1368— DependencyCollector::fold_new_promise has cognitive complexity 51 (threshold 15). Drivers by points: if/else 10 (41 pts), match/switch 3 (10 pts) (nesting depth added 38). 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.
DependencyCollector::fold_new_expr (cognitive 44) crates/js/src/transformer/dependency_collector.rs:1189— DependencyCollector::fold_new_expr has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (32 pts), match/switch 3 (10 pts), boolean chains 2 (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DependencyCollector::match_import_meta_prop (cognitive 39) crates/js/src/transformer/dependency_collector.rs:1794— DependencyCollector::match_import_meta_prop has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (35 pts), match/switch 2 (4 pts) (nesting depth added 25). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DependencyCollector::match_new_url (cognitive 38) crates/js/src/transformer/dependency_collector.rs:1659— DependencyCollector::match_new_url has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (33 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DependencyCollector::add_dependency (cognitive 22) crates/js/src/transformer/dependency_collector.rs:352— DependencyCollector::add_dependency has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3, match/switch 2 (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.
DependencyCollector::import_target (cognitive 17) crates/css/src/transformer.rs:365— DependencyCollector::import_target has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, match/switch 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DependencyCollector::fold_expr (cognitive 16) crates/js/src/transformer/dependency_collector.rs:1297— DependencyCollector::fold_expr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×9
Edited copy of a member (13 corresponding lines) crates/parcel-plugin-abi/src/bundle.rs:213— crates/parcel-plugin-abi/src/bundle.rs:213-225 | crates/parcel-plugin-abi/src/bundle.rs:234-246 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/html/src/arena.rs:163— crates/html/src/arena.rs:163-175 | crates/html/src/arena.rs:177-189 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/js/src/packager/dependencies.rs:209— crates/js/src/packager/dependencies.rs:209-223 | crates/js/src/packager/rsc.rs:466-478 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/html/src/serialize_html.rs:95— crates/html/src/serialize_html.rs:95-107 | crates/html/src/serialize_xml.rs:61-73 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/parcel-plugin-abi/src/asset.rs:495— crates/parcel-plugin-abi/src/asset.rs:495-507 | crates/parcel-plugin-abi/src/asset.rs:584-596 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) plugin-swift/Sources/ParcelPlugin/Asset.swift:57— plugin-swift/Sources/ParcelPlugin/Asset.swift:57-69 | plugin-swift/Sources/ParcelPlugin/Asset.swift:74-86 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/html/src/arena.rs:254— crates/html/src/arena.rs:254-269 | crates/html/src/oxvg.rs:516-528 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/plugin-js/src/plugin.rs:1323— crates/plugin-js/src/plugin.rs:1323-1335 | crates/plugin-js/src/plugin.rs:1337-1351 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/js/src/transformer/dependency_collector.rs:1612— crates/js/src/transformer/dependency_collector.rs:1612-1625 | crates/js/src/transformer/dependency_collector.rs:1627-1639 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
parcel_html::optimize::optimize (cyclomatic 69) crates/html/src/optimize.rs:68— parcel_html::optimize::optimize has cyclomatic complexity 69 (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.
parcel_html::package::insert_bundle_references (cyclomatic 53) crates/html/src/package.rs:168— parcel_html::package::insert_bundle_references has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel_html::srcset::parse_srcset (cyclomatic 39) crates/html/src/srcset.rs:50— parcel_html::srcset::parse_srcset has cyclomatic complexity 39 (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.
parcel_html::jsx::to_component (cyclomatic 38) crates/html/src/jsx.rs:712— parcel_html::jsx::to_component has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: parcel_html::jsx::jsx_attr_name (cyclomatic 366) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
parcel_html::serialize_html::can_omit_end_tag (cyclomatic 37) crates/html/src/serialize_html.rs:396— parcel_html::serialize_html::can_omit_end_tag has cyclomatic complexity 37 (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.
parcel_html::prepare_to_package (cyclomatic 22) crates/html/src/lib.rs:718— parcel_html::prepare_to_package 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.
parcel_html::serialize_html::can_omit_start_tag (cyclomatic 18) crates/html/src/serialize_html.rs:332— parcel_html::serialize_html::can_omit_start_tag has cyclomatic complexity 18 (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.
parcel_html::oxvg::oxvg_node_to_parcel (cyclomatic 17) crates/html/src/oxvg.rs:328— parcel_html::oxvg::oxvg_node_to_parcel 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.
parcel::parse_args (cyclomatic 63) crates/parcel/src/main.rs:145— parcel::parse_args has cyclomatic complexity 63 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
parcel::bundler::style_order::segment (cyclomatic 40) crates/parcel/src/bundler/style_order.rs:153— parcel::bundler::style_order::segment has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel::bundler::optimizer::optimize (cyclomatic 39) crates/parcel/src/bundler/optimizer.rs:404— parcel::bundler::optimizer::optimize has cyclomatic complexity 39 (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.
parcel::analyzer::write_report (cyclomatic 29) crates/parcel/src/analyzer/mod.rs:117— parcel::analyzer::write_report has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel::bundler::style_order::report_conflicts (cyclomatic 29) crates/parcel/src/bundler/style_order.rs:580— parcel::bundler::style_order::report_conflicts has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel::run (cyclomatic 20) crates/parcel/src/lib.rs:230— parcel::run 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.
parcel::server::serve_file (cyclomatic 19) crates/parcel/src/server.rs:252— parcel::server::serve_file 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.
parcel::serve (cyclomatic 16) crates/parcel/src/lib.rs:89— parcel::serve has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Duplicated block (9 lines × 2) crates/core/src/fs/memory.rs:135— crates/core/src/fs/memory.rs:135-143 | crates/core/src/fs/memory.rs:303-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/css/src/packager.rs:964— crates/css/src/packager.rs:964-972 | crates/css/src/packager.rs:977-985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/packager.rs:964` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/highlight/src/js.rs:257— crates/highlight/src/js.rs:257-265 | crates/highlight/src/js.rs:293-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/js/src/transformer/collect.rs:359— crates/js/src/transformer/collect.rs:359-367 | crates/js/src/transformer/modules.rs:351-359 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/transformer/collect.rs:359` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) crates/js/src/transformer/dependency_collector.rs:656— crates/js/src/transformer/dependency_collector.rs:656-664 | crates/js/src/transformer/dependency_collector.rs:710-718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/transformer/dependency_collector.rs:656` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/parcel-plugin-abi/src/fs.rs:77— crates/parcel-plugin-abi/src/fs.rs:77-85 | crates/parcel-plugin-abi/src/fs.rs:127-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) crates/parcel/src/lib.rs:193— crates/parcel/src/lib.rs:193-201 | crates/parcel/src/lib.rs:288-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/parcel/src/lib.rs:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/parcel/src/lib.rs:202` calls `build_started` and `crates/parcel/src/lib.rs:297` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/js/src/transformer/dependency_collector.rs:923— crates/js/src/transformer/dependency_collector.rs:923-931 | crates/js/src/transformer/dependency_collector.rs:936-944 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/transformer/dependency_collector.rs:923` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
parcel_css::packager::inline (cognitive 94) crates/css/src/packager.rs:457— parcel_css::packager::inline has cognitive complexity 94 (threshold 15). Drivers by points: if/else 22 (71 pts), match/switch 4 (12 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 62). 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.
parcel_css::packager::collect (cognitive 32) crates/css/src/packager.rs:287— parcel_css::packager::collect has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 3, loops 2, match/switch 1 (2 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.
parcel_css::resolve_css_module_export_inner (cognitive 31) crates/css/src/lib.rs:101— parcel_css::resolve_css_module_export_inner has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (2 pts) (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.
parcel_css::bundling::propagate (cognitive 30) crates/css/src/bundling.rs:194— parcel_css::bundling::propagate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 7 (9 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_css::packager::unused_css_module_symbols (cognitive 20) crates/css/src/packager.rs:408— parcel_css::packager::unused_css_module_symbols has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_css::packager::apply_import_condition (cognitive 19) crates/css/src/packager.rs:1087— parcel_css::packager::apply_import_condition has cognitive complexity 19 (threshold 15). Drivers by points: loops 3 (8 pts), if/else 3 (7 pts), match/switch 3 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_css::packager::check_import_position (cognitive 16) crates/css/src/packager.rs:1186— parcel_css::packager::check_import_position has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_core::bundle_and_package (cognitive 69) crates/core/src/lib.rs:428— parcel_core::bundle_and_package has cognitive complexity 69 (threshold 15). Drivers by points: if/else 14 (31 pts), loops 12 (24 pts), match/switch 3 (9 pts), boolean chains 5 (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.
parcel_core::asset_graph::resolve_symbol (cognitive 37) crates/core/src/asset_graph.rs:968— parcel_core::asset_graph::resolve_symbol has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 6, match/switch 1 (4 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_core::resolver::resolve (cognitive 35) crates/core/src/resolver.rs:23— parcel_core::resolver::resolve has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (27 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_core::packaging::strongly_connected_components (cognitive 28) crates/core/src/packaging.rs:606— parcel_core::packaging::strongly_connected_components has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 3 (7 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_core::packaging::package_bundles (cognitive 23) crates/core/src/packaging.rs:253— parcel_core::packaging::package_bundles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 7 (9 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.
parcel_core::fs::match_dir (cognitive 19) crates/core/src/fs/mod.rs:264— parcel_core::fs::match_dir has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
parcel_core::asset_graph::request_all (cognitive 18) crates/core/src/asset_graph.rs:1118— parcel_core::asset_graph::request_all has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sync-over-async blocking packages-v3/less/src/LessTransformer.ts:118— `fs.readFileSync` in `loadFile` 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-v3/less/src/LessTransformer.ts:134— `fs.readFileSync` in `loadFile` 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-v3/postcss/src/PostCSSTransformer.ts:97— `fs.readFileSync` in `findConfig` 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-v3/postcss/src/PostCSSTransformer.ts:131— `fs.readFileSync` in `loadConfigFile` 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-v3/posthtml/src/PostHTMLTransformer.ts:80— `fs.readFileSync` in `findConfig` 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-v3/posthtml/src/PostHTMLTransformer.ts:114— `fs.readFileSync` in `loadConfigFile` 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-v3/stylus/src/StylusTransformer.ts:167— `nativeFS.readFileSync` in `callback to map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
parcel_js::transformer::plugin::config (cyclomatic 66) crates/js/src/transformer/plugin.rs:329— parcel_js::transformer::plugin::config has cyclomatic complexity 66 (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.
parcel_js::packager::dependencies::asset_dependencies (cyclomatic 58) crates/js/src/packager/dependencies.rs:237— parcel_js::packager::dependencies::asset_dependencies has cyclomatic complexity 58 (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.
parcel_js::transformer::transform_to_ast (cyclomatic 55) crates/js/src/transformer/mod.rs:459— parcel_js::transformer::transform_to_ast has cyclomatic complexity 55 (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.
parcel_js::packager::write_runtime_globals (cyclomatic 20) crates/js/src/packager/mod.rs:1022— parcel_js::packager::write_runtime_globals 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.
parcel_js::hmr::get_hmr_update (cyclomatic 19) crates/js/src/hmr.rs:62— parcel_js::hmr::get_hmr_update 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.
parcel_js::packager::rsc::resolve_dependency (cyclomatic 17) crates/js/src/packager/rsc.rs:105— parcel_js::packager::rsc::resolve_dependency 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.
ResolveRequest::load_file (cognitive 30) crates/parcel-resolver/src/lib.rs:940— ResolveRequest::load_file has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveRequest::resolve (cognitive 29) crates/parcel-resolver/src/lib.rs:553— ResolveRequest::resolve has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ResolveRequest::read_tsconfig (cognitive 29) crates/parcel-resolver/src/lib.rs:1269— ResolveRequest::read_tsconfig has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 3 (8 pts), boolean chains 1, 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.
ResolveRequest::try_file (cognitive 24) crates/parcel-resolver/src/lib.rs:1126— ResolveRequest::try_file has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (24 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.
ResolveRequest::resolve_package (cognitive 23) crates/parcel-resolver/src/lib.rs:769— ResolveRequest::resolve_package has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveRequest::try_suffixes (cognitive 23) crates/parcel-resolver/src/lib.rs:1065— ResolveRequest::try_suffixes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Off the main sequence: browserslist-rs — browserslist-rs: 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: parcel-highlight — parcel-highlight: 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: parcel-macros — parcel-macros: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: parcel-plugin — parcel-plugin: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: parcel-resolver — parcel-resolver: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: parcel-core — parcel-core: abstractness 0.11, instability 0.17, distance 0.73 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Boundary violation [package:third-party-deep-import] crates/plugin-js/builtin-src/assert/index.js:9— crates/plugin-js/builtin-src/assert/index.js:9 imports assert/build/assert.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages-v3/stylus/src/StylusTransformer.ts:6— packages-v3/stylus/src/StylusTransformer.ts:6 imports stylus/lib/parser, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages-v3/stylus/src/StylusTransformer.ts:7— packages-v3/stylus/src/StylusTransformer.ts:7 imports stylus/lib/visitor/deps-resolver, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages-v3/stylus/src/StylusTransformer.ts:8— packages-v3/stylus/src/StylusTransformer.ts:8 imports stylus/lib/nodes/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages-v3/stylus/src/StylusTransformer.ts:9— packages-v3/stylus/src/StylusTransformer.ts:9 imports stylus/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages-v3/stylus/src/StylusTransformer.ts:10— packages-v3/stylus/src/StylusTransformer.ts:10 imports stylus/lib/visitor/evaluator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
DependencyCollector::visit_element (cyclomatic 86) crates/html/src/dependencies.rs:243— DependencyCollector::visit_element has cyclomatic complexity 86 (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.
DependencyCollector::fold_call_expr (cyclomatic 65) crates/js/src/transformer/dependency_collector.rs:750— DependencyCollector::fold_call_expr has cyclomatic complexity 65 (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.
DependencyCollector::add_dependency (cyclomatic 18) crates/js/src/transformer/dependency_collector.rs:352— DependencyCollector::add_dependency 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.
DependencyCollector::fold_new_expr (cyclomatic 18) crates/js/src/transformer/dependency_collector.rs:1189— DependencyCollector::fold_new_expr 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.
DependencyCollector::match_new_url (cyclomatic 16) crates/js/src/transformer/dependency_collector.rs:1659— DependencyCollector::match_new_url 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.
Collect::visit_member_expr (cognitive 45) crates/js/src/transformer/collect.rs:614— Collect::visit_member_expr has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (41 pts), boolean chains 3, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Collect::visit_call_expr (cognitive 32) crates/js/src/transformer/collect.rs:938— Collect::visit_call_expr has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 2 (8 pts), boolean chains 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Collect::visit_module (cognitive 24) crates/js/src/transformer/collect.rs:274— Collect::visit_module has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (10 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.
Collect::into_symbols (cognitive 22) crates/js/src/transformer/collect.rs:148— Collect::into_symbols has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5 (7 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Collect::add_pat_imports (cognitive 21) crates/js/src/transformer/collect.rs:984— Collect::add_pat_imports has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 6 (16 pts), if/else 2 (3 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) crates/parcel-plugin-abi/src/asset.rs:140— crates/parcel-plugin-abi/src/asset.rs:140-150 | crates/parcel-plugin-abi/src/asset.rs:162-173 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/parcel/src/macos.rs:126— crates/parcel/src/macos.rs:126-136 | crates/parcel/src/macos.rs:150-166 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/core/src/path.rs:132— crates/core/src/path.rs:132-142 | crates/core/src/path.rs:324-334 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/parcel/src/plugin_factory.rs:133— crates/parcel/src/plugin_factory.rs:133-143 | crates/parcel/src/plugin_factory.rs:150-161 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/parcel-plugin-abi/src/bundle_graph.rs:86— crates/parcel-plugin-abi/src/bundle_graph.rs:86-97 | crates/parcel-plugin-abi/src/bundle_graph.rs:113-123 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) crates/parcel-plugin/src/lib.rs:240— crates/parcel-plugin/src/lib.rs:240-248 | crates/parcel-plugin/src/lib.rs:268-276 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/parcel-plugin/src/lib.rs:1243— crates/parcel-plugin/src/lib.rs:1243-1251 | crates/parcel-plugin/src/lib.rs:1288-1296 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/core/src/fs/cached.rs:184— crates/core/src/fs/cached.rs:184-192 | crates/core/src/fs/cached.rs:194-202 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/plugin-js/src/bytecode.rs:138— crates/plugin-js/src/bytecode.rs:138-146 | crates/plugin-js/src/bytecode.rs:192-205 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/core/src/asset.rs:61— crates/core/src/asset.rs:61-70 | crates/core/src/dependency.rs:344-352 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) crates/highlight/src/js.rs:244— crates/highlight/src/js.rs:244-254 | crates/highlight/src/js.rs:364-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/highlight/src/js.rs:244` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/highlight/src/js.rs:363` calls `jsx_name` and `crates/highlight/src/js.rs:243` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) crates/js/src/transformer/dependency_collector.rs:652— crates/js/src/transformer/dependency_collector.rs:652-662 | crates/js/src/transformer/dependency_collector.rs:681-691 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/transformer/dependency_collector.rs:652` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/parcel-resolver/src/package_json.rs:164— crates/parcel-resolver/src/package_json.rs:164-174 | crates/parcel-resolver/src/package_json.rs:488-498 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/parcel-resolver/src/package_json.rs:164` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/css/src/packager.rs:248— crates/css/src/packager.rs:248-258 | crates/css/src/transformer.rs:206-216 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/packager.rs:248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/html/src/jsx.rs:798— crates/html/src/jsx.rs:798-808 | crates/html/src/jsx.rs:810-820 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/html/src/jsx.rs:798` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/core/src/fs/memory.rs:71— crates/core/src/fs/memory.rs:71-80 | crates/core/src/fs/memory.rs:282-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/fs/memory.rs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/html/src/dependencies.rs:345— crates/html/src/dependencies.rs:345-354 | crates/html/src/dependencies.rs:427-436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/html/src/dependencies.rs:345` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/js/src/packager/tree_shake.rs:571— crates/js/src/packager/tree_shake.rs:571-580 | crates/js/src/packager/tree_shake.rs:642-651 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/packager/tree_shake.rs:571` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/js/src/transformer/collect.rs:987— crates/js/src/transformer/collect.rs:987-996 | crates/js/src/transformer/collect.rs:1073-1082 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) plugin-swift/Sources/ParcelPlugin/Exports.swift:84— plugin-swift/Sources/ParcelPlugin/Exports.swift:84-93 | plugin-swift/Sources/ParcelPlugin/Exports.swift:170-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugin-swift/Sources/ParcelPlugin/Exports.swift:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/plugin-js/src/cjs.rs:99— crates/plugin-js/src/cjs.rs:99-105 | crates/plugin-js/src/esm.rs:77-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/cjs.rs:99` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) crates/core/src/path.rs:553— crates/core/src/path.rs:553-559 | crates/core/src/path.rs:785-791 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/parcel-plugin-abi/src/bundle.rs:81— crates/parcel-plugin-abi/src/bundle.rs:81-87 | crates/parcel-plugin-abi/src/target.rs:205-211 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/parcel-plugin-abi/src/dependency.rs:509— crates/parcel-plugin-abi/src/dependency.rs:509-515 | crates/parcel-plugin-abi/src/target.rs:169-175 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/js/src/transformer/dependency_collector.rs:875— crates/js/src/transformer/dependency_collector.rs:875-881 | crates/js/src/transformer/dependency_collector.rs:884-890 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/transformer/dependency_collector.rs:875` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) crates/core/src/path.rs:133— crates/core/src/path.rs:133-138 | crates/core/src/path.rs:325-330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/path.rs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/parcel/src/toml.rs:19— crates/parcel/src/toml.rs:19-24 | crates/parcel/src/yaml.rs:19-24 — before extracting anything, compare `crates/parcel/src/toml.rs` and `crates/parcel/src/yaml.rs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/parcel/src/toml.rs:19` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/html/src/optimize.rs:349— crates/html/src/optimize.rs:349-354 | crates/html/src/optimize.rs:366-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/html/src/optimize.rs:349` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) crates/css/src/packager.rs:1040— crates/css/src/packager.rs:1040-1045 | crates/css/src/packager.rs:1116-1121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/packager.rs:1040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) plugin-swift/Sources/ParcelPlugin/Asset.swift:162— plugin-swift/Sources/ParcelPlugin/Asset.swift:162-167 | plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:188-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) crates/parcel-plugin-abi/src/bundle.rs:167— crates/parcel-plugin-abi/src/bundle.rs:167-171 | crates/parcel-plugin-abi/src/bundle.rs:179-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/parcel-plugin-abi/src/bundle.rs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/plugin-js/src/url.rs:141— crates/plugin-js/src/url.rs:141-145 | crates/plugin-js/src/url.rs:353-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/url.rs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/html/src/serialize_html.rs:310— crates/html/src/serialize_html.rs:310-314 | crates/html/src/serialize_xml.rs:210-214 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) crates/html/src/serialize_html.rs:316— crates/html/src/serialize_html.rs:316-320 | crates/html/src/serialize_xml.rs:217-221 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/html/src/serialize_xml.rs:224` calls `write_text`, `write_to_buf_escaped` and `crates/html/src/serialize_html.rs:322` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/parcel/src/lib.rs:68— crates/parcel/src/lib.rs:68-72 | crates/parcel/src/lib.rs:105-109 — 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.
R4 · Test Coverage· This test file cannot be loaded · ×5
This test file cannot be loaded crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1— crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1 imports './dir/*.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 crates/parcel/tests/fixtures/url-imports/import-raw-import-meta-url/local-url.js:7— crates/parcel/tests/fixtures/url-imports/import-raw-import-meta-url/local-url.js:7 imports './invalid.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 crates/parcel/tests/fixtures/workers/service-worker-import-meta-url/missing.js:1— crates/parcel/tests/fixtures/workers/service-worker-import-meta-url/missing.js:1 imports './invalid.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 crates/parcel/tests/fixtures/workers/worker-import-meta-url/local-url.js:7— crates/parcel/tests/fixtures/workers/worker-import-meta-url/local-url.js:7 imports './invalid.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 crates/parcel/tests/fixtures/workers/worker-import-meta-url/missing.js:1— crates/parcel/tests/fixtures/workers/worker-import-meta-url/missing.js:1 imports './invalid.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.
Evaluator::eval (cognitive 62) crates/macros/src/lib.rs:398— Evaluator::eval has cognitive complexity 62 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 8 (21 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 32). 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.
Evaluator::fold_expr (cognitive 39) crates/js/src/transformer/fs.rs:210— Evaluator::fold_expr has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 8 (21 pts), if/else 4 (14 pts), loops 1 (4 pts) (nesting depth added 26). 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.
Evaluator::eval_pat (cognitive 29) crates/macros/src/lib.rs:787— Evaluator::eval_pat has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 3 (8 pts), loops 2 (4 pts) (nesting depth added 19). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Evaluator::eval_object (cognitive 23) crates/macros/src/lib.rs:655— Evaluator::eval_object has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 2 (5 pts), loops 1 (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PackageJson::resolve_package_target (cognitive 37) crates/parcel-resolver/src/package_json.rs:456— PackageJson::resolve_package_target has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 5 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 20). 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.
PackageJson::resolve_alias (cognitive 37) crates/parcel-resolver/src/package_json.rs:633— PackageJson::resolve_alias has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (29 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageJson::resolve_package_exports (cognitive 24) crates/parcel-resolver/src/package_json.rs:368— PackageJson::resolve_package_exports has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (7 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageJson::resolve_package_imports_exports (cognitive 17) crates/parcel-resolver/src/package_json.rs:554— PackageJson::resolve_package_imports_exports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, 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.
parcel_dev_dep_resolver::skip_comments_and_whitespace (cognitive 35) crates/dev-dep-resolver/src/lib.rs:390— parcel_dev_dep_resolver::skip_comments_and_whitespace has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 3 (11 pts), boolean chains 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
parcel_dev_dep_resolver::read_template_string (cognitive 34) crates/dev-dep-resolver/src/lib.rs:313— parcel_dev_dep_resolver::read_template_string has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_dev_dep_resolver::specifier_to_glob (cognitive 30) crates/dev-dep-resolver/src/lib.rs:230— parcel_dev_dep_resolver::specifier_to_glob has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_dev_dep_resolver::skip_expression (cognitive 21) crates/dev-dep-resolver/src/lib.rs:426— parcel_dev_dep_resolver::skip_expression has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_plugin_js::path::parse (cognitive 35) crates/plugin-js/src/path.rs:259— parcel_plugin_js::path::parse has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 4, match/switch 1 (2 pts), 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.
parcel_plugin_js::path::extension_range (cognitive 24) crates/plugin-js/src/path.rs:177— parcel_plugin_js::path::extension_range has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_plugin_js::path::resolve (cognitive 18) crates/plugin-js/src/path.rs:31— parcel_plugin_js::path::resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 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.
parcel_plugin_js::await_promise (cognitive 17) crates/plugin-js/src/lib.rs:461— parcel_plugin_js::await_promise has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 1 (4 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: DependencyCollector crates/js/src/transformer/dependency_collector.rs:334— ClassTooLong — 912 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 6 blocks, lines 334-1980. The bar is 400 significant lines; this is 512 over it, 2.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Collect crates/js/src/transformer/collect.rs:62— ClassTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 5 blocks, lines 62-1105. The bar is 400 significant lines; this is 249 over it, 1.62× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ResolveRequest crates/parcel-resolver/src/lib.rs:426— ClassTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 426-1367. The bar is 400 significant lines; this is 181 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DependencyCollector crates/html/src/dependencies.rs:172— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 172-886. The bar is 400 significant lines; this is 95 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×4
Edited copy of a member (20 corresponding lines) crates/parcel-plugin-abi/src/fs.rs:76— crates/parcel-plugin-abi/src/fs.rs:76-95 | crates/parcel-plugin-abi/src/fs.rs:126-146 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) crates/html/src/lib.rs:520— crates/html/src/lib.rs:520-544 | crates/html/src/xml.rs:143-162 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) crates/plugin-js/src/crypto.rs:753— crates/plugin-js/src/crypto.rs:753-772 | crates/plugin-js/src/path.rs:400-424 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) crates/parcel-plugin-abi/src/bundle.rs:90— crates/parcel-plugin-abi/src/bundle.rs:90-111 | crates/parcel-plugin-abi/src/target.rs:239-258 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×4
Edited copy of a member (18 corresponding lines) crates/core/src/target.rs:57— crates/core/src/target.rs:57-74 | crates/core/src/target.rs:139-156 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/parcel-plugin-abi/src/asset.rs:241— crates/parcel-plugin-abi/src/asset.rs:241-258 | crates/parcel-plugin-abi/src/asset.rs:260-283 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/html/src/lib.rs:315— crates/html/src/lib.rs:315-338 | crates/html/src/lib.rs:404-421 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/parcel-plugin-abi/src/extensible.rs:62— crates/parcel-plugin-abi/src/extensible.rs:62-81 | crates/parcel-plugin-abi/src/extensible.rs:104-121 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) crates/plugin-js/src/fs.rs:224— crates/plugin-js/src/fs.rs:224-230 | crates/plugin-js/src/fs.rs:235-241 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/plugin-js/src/buffer.rs:112— crates/plugin-js/src/buffer.rs:112-127 | crates/plugin-js/src/buffer.rs:132-138 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/html/src/serialize_html.rs:322— crates/html/src/serialize_html.rs:322-328 | crates/html/src/serialize_xml.rs:229-235 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/parcel-plugin-abi/src/asset.rs:551— crates/parcel-plugin-abi/src/asset.rs:551-557 | crates/parcel-plugin-abi/src/dependency.rs:207-213 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) crates/core/src/entry.rs:133— crates/core/src/entry.rs:133-145 | crates/core/src/entry.rs:243-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/entry.rs:133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/core/src/entry.rs:132` calls `default` and `crates/core/src/entry.rs:242` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/html/src/dependencies.rs:460— crates/html/src/dependencies.rs:460-472 | crates/html/src/dependencies.rs:492-504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/html/src/dependencies.rs:491` calls `text_content` and `crates/html/src/dependencies.rs:458` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/js/src/packager/tree_shake.rs:530— crates/js/src/packager/tree_shake.rs:530-542 | crates/js/src/packager/tree_shake.rs:619-631 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) crates/core/src/target.rs:482— crates/core/src/target.rs:482-494 | crates/core/src/target.rs:496-508 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×4
JavaScript dependencies are not locked crates/parcel-resolver/tests/fixture/package.json:18— crates/parcel-resolver/tests/fixture/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked packages-v3/create-parcel/templates/react-client/package.json:10— packages-v3/create-parcel/templates/react-client/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked packages-v3/create-parcel/templates/react-server/package.json:18— packages-v3/create-parcel/templates/react-server/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked packages-v3/create-parcel/templates/vanilla/package.json:11— packages-v3/create-parcel/templates/vanilla/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / 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.
AC3 · Page structure· Page without a main landmark · ×3
Page without a main landmark packages-v3/create-parcel/templates/react-client/src/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-v3/create-parcel/templates/react-server/src/Page.tsx:10— 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-v3/create-parcel/templates/vanilla/src/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>.
Evaluator::eval (cyclomatic 96) crates/macros/src/lib.rs:398— Evaluator::eval has cyclomatic complexity 96 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Evaluator::eval_pat (cyclomatic 19) crates/macros/src/lib.rs:787— Evaluator::eval_pat has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Evaluator::fold_expr (cyclomatic 16) crates/js/src/transformer/fs.rs:210— Evaluator::fold_expr has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
parcel_core::bundle_and_package (cyclomatic 35) crates/core/src/lib.rs:428— parcel_core::bundle_and_package has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel_core::asset_graph::resolve_symbol (cyclomatic 25) crates/core/src/asset_graph.rs:968— parcel_core::asset_graph::resolve_symbol 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.
parcel_core::packaging::package_bundles (cyclomatic 18) crates/core/src/packaging.rs:253— parcel_core::packaging::package_bundles 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.
parcel_css::packager::inline (cyclomatic 32) crates/css/src/packager.rs:457— parcel_css::packager::inline has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parcel_css::bundling::propagate (cyclomatic 17) crates/css/src/bundling.rs:194— parcel_css::bundling::propagate 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.
parcel_css::packager::collect (cyclomatic 17) crates/css/src/packager.rs:287— parcel_css::packager::collect has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: ReferenceReplacer::visit_rule (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
parcel_highlight::js::classify (cyclomatic 25) crates/highlight/src/js.rs:381— parcel_highlight::js::classify has cyclomatic complexity 25 (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.
parcel_highlight::html::tag_attrs (cyclomatic 20) crates/highlight/src/html.rs:88— parcel_highlight::html::tag_attrs has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
parcel_highlight::html::highlight_html (cyclomatic 16) crates/highlight/src/html.rs:10— parcel_highlight::html::highlight_html 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.
TreeShake::visit_mut_stmt (cyclomatic 23) crates/js/src/packager/tree_shake.rs:319— TreeShake::visit_mut_stmt 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.
TreeShake::visit_mut_module_items (cyclomatic 22) crates/js/src/packager/tree_shake.rs:565— TreeShake::visit_mut_module_items 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.
TreeShake::visit_mut_expr (cyclomatic 19) crates/js/src/packager/tree_shake.rs:426— TreeShake::visit_mut_expr 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.
TreeShake::visit_mut_stmt (cognitive 52) crates/js/src/packager/tree_shake.rs:319— TreeShake::visit_mut_stmt has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (46 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeShake::visit_mut_module_items (cognitive 45) crates/js/src/packager/tree_shake.rs:565— TreeShake::visit_mut_module_items has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (33 pts), match/switch 4 (11 pts), loops 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeShake::visit_mut_expr (cognitive 32) crates/js/src/packager/tree_shake.rs:426— TreeShake::visit_mut_expr has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (26 pts), match/switch 3 (6 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AssetGraph::dfs (cognitive 43) crates/core/src/asset_graph.rs:1266— AssetGraph::dfs has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (34 pts), loops 4 (9 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetGraph::get_exports::get_exports (cognitive 38) crates/core/src/asset_graph.rs:1400— AssetGraph::get_exports::get_exports has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 4 (6 pts), match/switch 1 (5 pts), boolean chains 2 (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.
AssetGraph::resolved_dependencies_with_indices (cognitive 23) crates/core/src/asset_graph.rs:1333— AssetGraph::resolved_dependencies_with_indices has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 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.
EntryResolver::resolve_file_entry (cognitive 39) crates/core/src/entry.rs:103— EntryResolver::resolve_file_entry has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (27 pts), match/switch 3 (8 pts), boolean chains 3, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntryResolver::extract_exports (cognitive 38) crates/core/src/entry.rs:358— EntryResolver::extract_exports has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EntryResolver::resolve_package_entries (cognitive 20) crates/core/src/entry.rs:261— EntryResolver::resolve_package_entries has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (6 pts), match/switch 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_highlight::html::tag_attrs (cognitive 36) crates/highlight/src/html.rs:88— parcel_highlight::html::tag_attrs has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (13 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_highlight::html::highlight_html (cognitive 30) crates/highlight/src/html.rs:10— parcel_highlight::html::highlight_html has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcel_highlight::js::classify (cognitive 16) crates/highlight/src/js.rs:381— parcel_highlight::js::classify has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), match/switch 1 (nesting depth added 1). 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.
Driver::jsx_element_inner (cognitive 34) crates/highlight/src/js.rs:213— Driver::jsx_element_inner has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 2 (6 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Driver::jsx_children (cognitive 18) crates/highlight/src/js.rs:336— Driver::jsx_children has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Driver::run (cognitive 17) crates/highlight/src/js.rs:140— Driver::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InlineFS::evaluate_fs_arg (cognitive 27) crates/js/src/transformer/fs.rs:118— InlineFS::evaluate_fs_arg has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 5 (10 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
InlineFS::fold_expr (cognitive 22) crates/js/src/transformer/fs.rs:54— InlineFS::fold_expr has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (21 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.
InlineFS::match_module_reference (cognitive 21) crates/js/src/transformer/fs.rs:74— InlineFS::match_module_reference has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Duplicated block (8 lines × 2) crates/plugin-js/src/cjs.rs:165— crates/plugin-js/src/cjs.rs:165-172 | crates/plugin-js/src/cjs.rs:293-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) crates/macros/src/lib.rs:212— crates/macros/src/lib.rs:212-219 | crates/macros/src/lib.rs:240-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/lib.rs:212` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/parcel-plugin-abi/src/bundle.rs:214— crates/parcel-plugin-abi/src/bundle.rs:214-221 | crates/parcel-plugin-abi/src/bundle.rs:235-242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Low cohesion: Sink (LCOM4 6) crates/html/src/arena.rs:26— Sink's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: HmrServer (LCOM4 5) crates/parcel/src/server.rs:63— HmrServer's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Resolver (LCOM4 4) crates/parcel-resolver/src/lib.rs:125— Resolver's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Collect::visit_member_expr (cyclomatic 26) crates/js/src/transformer/collect.rs:614— Collect::visit_member_expr 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.
Collect::add_pat_imports (cyclomatic 23) crates/js/src/transformer/collect.rs:984— Collect::add_pat_imports has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ResolveRequest::resolve (cyclomatic 20) crates/parcel-resolver/src/lib.rs:553— ResolveRequest::resolve has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResolveRequest::load_file (cyclomatic 19) crates/parcel-resolver/src/lib.rs:940— ResolveRequest::load_file 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.
Driver::jsx_element_inner (cyclomatic 17) crates/highlight/src/js.rs:213— Driver::jsx_element_inner 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.
Driver::run (cyclomatic 16) crates/highlight/src/js.rs:140— Driver::run has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Internalization::new (cyclomatic 16) crates/parcel/src/bundler/internalization.rs:45— Internalization::new 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.
Internalization::run (cyclomatic 16) crates/parcel/src/bundler/internalization.rs:140— Internalization::run 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.
EnvReplacer::visit_mut_expr (cognitive 80) crates/js/src/transformer/env_replacer.rs:30— EnvReplacer::visit_mut_expr has cognitive complexity 80 (threshold 15). Drivers by points: if/else 24 (65 pts), match/switch 4 (13 pts), boolean chains 2 (nesting depth added 50). 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.
EnvReplacer::collect_pat_bindings (cognitive 24) crates/js/src/transformer/env_replacer.rs:266— EnvReplacer::collect_pat_bindings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsContent::package_library (cognitive 42) crates/js/src/library_packager.rs:26— JsContent::package_library has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 1 (2 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
JsContent::package_app (cognitive 39) crates/js/src/packager/mod.rs:69— JsContent::package_app has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (29 pts), match/switch 3 (5 pts), loops 4, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Internalization::new (cognitive 26) crates/parcel/src/bundler/internalization.rs:45— Internalization::new has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Internalization::run (cognitive 26) crates/parcel/src/bundler/internalization.rs:140— Internalization::run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AvailabilityGraph::new (cognitive 21) crates/parcel/src/bundler/availability.rs:241— AvailabilityGraph::new has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (12 pts), if/else 3 (9 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AvailabilityGraph::from_asset_graph (cognitive 20) crates/parcel/src/bundler/availability.rs:172— AvailabilityGraph::from_asset_graph has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CjsLoader::resolve (cognitive 21) crates/plugin-js/src/cjs.rs:57— CjsLoader::resolve has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (3 pts), match/switch 2 (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.
CjsLoader::load (cognitive 17) crates/plugin-js/src/cjs.rs:164— CjsLoader::load has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: ParcelApi crates/parcel-plugin-abi/src/api.rs:106— TooManyFields — 88 stored fields. The bar is 30 stored fields; this is 58 over it, 2.93× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: OxvgConfig crates/html/src/oxvg.rs:594— TooManyFields — 53 stored fields beside 2 methods. The bar is 30 stored fields; this is 23 over it, 1.77× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×2
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×2
Edited copy of a member (40 corresponding lines) crates/js/src/transformer/collect.rs:358— crates/js/src/transformer/collect.rs:358-397 | crates/macros/src/lib.rs:86-126 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) crates/html/src/lib.rs:579— crates/html/src/lib.rs:579-618 | crates/html/src/lib.rs:978-1017 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) crates/js/src/transformer/modules.rs:134— crates/js/src/transformer/modules.rs:134-156 | crates/js/src/transformer/modules.rs:158-184 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) crates/parcel-plugin-abi/src/dependency.rs:453— crates/parcel-plugin-abi/src/dependency.rs:453-475 | crates/parcel-plugin-abi/src/dependency.rs:480-506 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) plugin-swift/Sources/ParcelPlugin/Options.swift:102— plugin-swift/Sources/ParcelPlugin/Options.swift:102-109 | plugin-swift/Sources/ParcelPlugin/Options.swift:132-139 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) plugin-swift/Sources/ParcelPlugin/Asset.swift:289— plugin-swift/Sources/ParcelPlugin/Asset.swift:289-296 | plugin-swift/Sources/ParcelPlugin/Asset.swift:300-307 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×2
Edited copy of a member (3 corresponding lines) plugin-swift/Sources/ParcelPlugin/Asset.swift:47— plugin-swift/Sources/ParcelPlugin/Asset.swift:47-49 | plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:137-139 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) plugin-swift/Sources/ParcelPlugin/Asset.swift:41— plugin-swift/Sources/ParcelPlugin/Asset.swift:41-43 | plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:132-134 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16 lines × 2) crates/html/src/jsx.rs:910— crates/html/src/jsx.rs:910-925 | crates/html/src/jsx.rs:929-944 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/html/src/jsx.rs:910` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/parcel-plugin/src/lib.rs:1185— crates/parcel-plugin/src/lib.rs:1185-1200 | crates/parcel-plugin/src/lib.rs:1666-1681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
End-of-life runtime: Node.js 16 package.json:69— package.json declares Node.js 16 as this project's engines.node, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: Node.js 18 packages-v3/create-parcel/package.json:19— packages-v3/create-parcel/package.json declares Node.js 18 as this project's engines.node, and Node.js 18, support ended 2025-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
No authorization crates/parcel/src/server.rs:210— This repository serves requests — a server (Server::new(listener) (crates/parcel/src/server.rs:210) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
DefaultResolver::resolve (cyclomatic 53) crates/parcel/src/resolver.rs:24— DefaultResolver::resolve has cyclomatic complexity 53 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DefaultBundler::bundle (cyclomatic 52) crates/parcel/src/bundler.rs:173— DefaultBundler::bundle has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetGraphBuilder::build_with_changes (cyclomatic 46) crates/core/src/asset_graph.rs:238— AssetGraphBuilder::build_with_changes has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
assetPanel (cyclomatic 46) crates/parcel/src/analyzer/client.js:1364— assetPanel has cyclomatic complexity 46 (threshold 15). Of this number, 31 points are the body's own statements and 15 belong to 13 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.
Esm2Cjs::visit_mut_module (cyclomatic 39) crates/js/src/transformer/modules.rs:335— Esm2Cjs::visit_mut_module has cyclomatic complexity 39 (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.
ImageTransformer::transform (cyclomatic 35) crates/image/src/lib.rs:49— ImageTransformer::transform has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
State::rebuild (cyclomatic 35) crates/parcel/src/bundler/optimizer.rs:222— State::rebuild has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EnvReplacer::visit_mut_expr (cyclomatic 32) crates/js/src/transformer/env_replacer.rs:30— EnvReplacer::visit_mut_expr has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Engines::supports (cyclomatic 28) crates/core/src/target.rs:540— Engines::supports has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BundleRoots::from_asset_graph (cyclomatic 27) crates/parcel/src/bundler/bundle_roots.rs:36— BundleRoots::from_asset_graph has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsContent::package_app (cyclomatic 26) crates/js/src/packager/mod.rs:69— JsContent::package_app 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.
JsTransformer::transform (cyclomatic 26) crates/js/src/transformer/plugin.rs:87— JsTransformer::transform has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dev-runtime.parcelRequire (cyclomatic 26) REDACTED:34— dev-runtime.parcelRequire has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (localRequire, a function literal at line 103, a function literal at line 109, …). 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.
GlobResolver::resolve (cyclomatic 25) crates/parcel/src/glob_resolver.rs:18— GlobResolver::resolve 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.
Specifier::parse (cyclomatic 25) crates/parcel-resolver/src/specifier.rs:77— Specifier::parse 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.
EntryResolver::resolve_file_entry (cyclomatic 23) crates/core/src/entry.rs:103— EntryResolver::resolve_file_entry 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.
PackageJson::resolve_package_target (cyclomatic 23) crates/parcel-resolver/src/package_json.rs:456— PackageJson::resolve_package_target 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.
ReactLazy::visit_call_expr (cyclomatic 22) crates/js/src/transformer/react_lazy.rs:28— ReactLazy::visit_call_expr 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.
DefaultPluginFactory::transformer (cyclomatic 22) crates/parcel/src/plugin_factory.rs:58— DefaultPluginFactory::transformer has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OxvgConfig::into_jobs (cyclomatic 21) crates/html/src/oxvg.rs:773— OxvgConfig::into_jobs has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CjsLoader::load (cyclomatic 21) crates/plugin-js/src/cjs.rs:164— CjsLoader::load has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: CjsLoader::resolve_builtin (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
CssContent::package_impl (cyclomatic 20) crates/css/src/packager.rs:49— CssContent::package_impl 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. This is NOT this file's highest cyclomatic complexity: ReferenceReplacer::visit_rule (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
HtmlSerializer::start_elem (cyclomatic 20) crates/html/src/serialize_html.rs:154— HtmlSerializer::start_elem has cyclomatic complexity 20 (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.
SyntheticAsset::write_content (cyclomatic 20) crates/js/src/packager/synthetic.rs:183— SyntheticAsset::write_content has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
parcel_plugin_js::path::parse (cyclomatic 20) crates/plugin-js/src/path.rs:259— parcel_plugin_js::path::parse 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.
dev-runtime.handleMessage (cyclomatic 20) REDACTED:545— dev-runtime.handleMessage 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.
CodeFrame::render_code (cyclomatic 19) crates/core/src/diagnostic.rs:580— CodeFrame::render_code has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExportsContext::to_env (cyclomatic 19) crates/core/src/entry.rs:563— ExportsContext::to_env 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.
Browsers::fmt (cyclomatic 19) crates/core/src/target.rs:305— Browsers::fmt 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.
client.showTooltip (cyclomatic 19) crates/parcel/src/analyzer/client.js:747— client.showTooltip 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.
parcel_dev_dep_resolver::read_template_string (cyclomatic 18) crates/dev-dep-resolver/src/lib.rs:313— parcel_dev_dep_resolver::read_template_string 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.
Search::verdict (cyclomatic 18) crates/parcel/src/bundler/optimizer.rs:1147— Search::verdict 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.
ModuleLoader::load (cyclomatic 18) crates/plugin-js/src/esm.rs:127— ModuleLoader::load 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.
CodecOptions::from_js (cyclomatic 18) crates/plugin-js/src/zlib.rs:35— CodecOptions::from_js 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.
BuiltinGraph.readPackage (cyclomatic 18) crates/plugin-js/buildBuiltins.cjs:254— BuiltinGraph.readPackage 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.
Reachability::from_bundle_roots (cyclomatic 17) crates/parcel/src/bundler/reachability.rs:21— Reachability::from_bundle_roots 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.
CLIReporter::report (cyclomatic 17) crates/parcel/src/main.rs:487— CLIReporter::report 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.
DefaultNamer::name (cyclomatic 17) crates/parcel/src/namer.rs:14— DefaultNamer::name 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.
StylusTransformer.getDependencies (cyclomatic 17) packages-v3/stylus/src/StylusTransformer.ts:92— StylusTransformer.getDependencies 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 literal inside it that branches (line 127). 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.
InvalidationMap::invalidate (cyclomatic 16) crates/core/src/invalidations.rs:185— InvalidationMap::invalidate 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.
CssTransformer::transform (cyclomatic 16) crates/css/src/transformer.rs:110— CssTransformer::transform 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.
parcel_plugin_abi::dependency::parcel_asset_resolve (cyclomatic 16) crates/parcel-plugin-abi/src/dependency.rs:311— parcel_plugin_abi::dependency::parcel_asset_resolve 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.
AssetGraphBuilder::build_with_changes (cognitive 161) crates/core/src/asset_graph.rs:238— AssetGraphBuilder::build_with_changes has cognitive complexity 161 (threshold 15). Drivers by points: if/else 30 (112 pts), loops 16 (39 pts), match/switch 2 (7 pts), boolean chains 3 (nesting depth added 110). 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.
DefaultBundler::bundle (cognitive 130) crates/parcel/src/bundler.rs:173— DefaultBundler::bundle has cognitive complexity 130 (threshold 15). Drivers by points: if/else 42 (92 pts), loops 13 (27 pts), match/switch 3 (7 pts), boolean chains 4 (nesting depth added 68). 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.
Esm2Cjs::visit_mut_module (cognitive 115) crates/js/src/transformer/modules.rs:335— Esm2Cjs::visit_mut_module has cognitive complexity 115 (threshold 15). Drivers by points: if/else 16 (53 pts), match/switch 10 (41 pts), loops 6 (21 pts) (nesting depth added 83). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State::rebuild (cognitive 84) crates/parcel/src/bundler/optimizer.rs:222— State::rebuild has cognitive complexity 84 (threshold 15). Drivers by points: if/else 18 (46 pts), loops 17 (37 pts), match/switch 1 (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
assetPanel (cognitive 77) crates/parcel/src/analyzer/client.js:1364— assetPanel has cognitive complexity 77 (threshold 15). Drivers by points: ternaries 22 (46 pts), if/else 13 (19 pts), boolean chains 7, other 4, loops 1 (nesting depth added 30). Of this number, 45 points are the body's own statements and 32 belong to 13 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.
BundleRoots::from_asset_graph (cognitive 58) crates/parcel/src/bundler/bundle_roots.rs:36— BundleRoots::from_asset_graph has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (46 pts), loops 6 (8 pts), boolean chains 4 (nesting depth added 31). 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.
Specifier::parse (cognitive 57) crates/parcel-resolver/src/specifier.rs:77— Specifier::parse has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (48 pts), match/switch 3 (7 pts), boolean chains 2 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeFrame::render_code (cognitive 51) crates/core/src/diagnostic.rs:580— CodeFrame::render_code has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (40 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Reachability::from_bundle_roots (cognitive 45) crates/parcel/src/bundler/reachability.rs:21— Reachability::from_bundle_roots has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 7 (15 pts), boolean chains 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parcelRequire (cognitive 45) REDACTED:34— parcelRequire has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (33 pts), boolean chains 7, ternaries 2 (5 pts) (nesting depth added 20). Of this number, 23 points are the body's own statements and 22 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.
ReactLazy::visit_call_expr (cognitive 40) crates/js/src/transformer/react_lazy.rs:28— ReactLazy::visit_call_expr has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 5, loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Macros::fold_expr (cognitive 38) crates/macros/src/lib.rs:203— Macros::fold_expr has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (29 pts), match/switch 2 (9 pts) (nesting depth added 28). 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.
AvailabilityState::solve_with (cognitive 38) crates/parcel/src/bundler/availability.rs:93— AvailabilityState::solve_with has cognitive complexity 38 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 5 (11 pts), match/switch 1 (5 pts), boolean chains 2 (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.
CssContent::package_impl (cognitive 35) crates/css/src/packager.rs:49— CssContent::package_impl has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 6 (7 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CssTransformer::transform (cognitive 35) crates/css/src/transformer.rs:110— CssTransformer::transform has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3 (10 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlobResolver::resolve (cognitive 35) crates/parcel/src/glob_resolver.rs:18— GlobResolver::resolve has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (22 pts), match/switch 5 (8 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultResolver::resolve (cognitive 35) crates/parcel/src/resolver.rs:24— DefaultResolver::resolve has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (21 pts), match/switch 7 (12 pts), boolean chains 2 (nesting depth added 8). 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.
handleMessage (cognitive 35) REDACTED:545— handleMessage has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 2 (5 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 16). Of this number, 30 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InvalidationMap::invalidate (cognitive 34) crates/core/src/invalidations.rs:185— InvalidationMap::invalidate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 6 (12 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageTransformer::transform (cognitive 31) crates/image/src/lib.rs:49— ImageTransformer::transform has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 4 (10 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsTransformer::transform (cognitive 31) crates/js/src/transformer/plugin.rs:87— JsTransformer::transform has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (22 pts), match/switch 2 (4 pts), boolean chains 3, loops 2 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SyntheticAsset::write_content (cognitive 29) crates/js/src/packager/synthetic.rs:183— SyntheticAsset::write_content has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (6 pts), match/switch 3 (6 pts) (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
dev-runtime.hmrApply (cognitive 29) REDACTED:912— dev-runtime.hmrApply has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BuiltinGraph.readPackage (cognitive 29) crates/plugin-js/buildBuiltins.cjs:254— BuiltinGraph.readPackage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 2 (9 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LibraryBundler::bundle (cognitive 28) crates/parcel/src/library_bundler.rs:14— LibraryBundler::bundle has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (5 pts), match/switch 1 (2 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.
buildBuiltins.validateOutput (cognitive 28) crates/plugin-js/buildBuiltins.cjs:486— buildBuiltins.validateOutput has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (4 pts), error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 15). Of this number, 24 points are the body's own statements and 4 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.
Engines::supports (cognitive 27) crates/core/src/target.rs:540— Engines::supports has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 9 (18 pts), if/else 9 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Browsers::fmt (cognitive 27) crates/core/src/target.rs:305— Browsers::fmt has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (27 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.
HtmlSerializer::start_elem (cognitive 26) crates/html/src/serialize_html.rs:154— HtmlSerializer::start_elem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, match/switch 2 (3 pts), 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.
CodecOptions::from_js (cognitive 26) crates/plugin-js/src/zlib.rs:35— CodecOptions::from_js has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExportsContext::to_env (cognitive 25) crates/core/src/entry.rs:563— ExportsContext::to_env has cognitive complexity 25 (threshold 15). Drivers by points: if/else 21 (23 pts), boolean chains 1, match/switch 1 (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, 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.
DefaultNamer::name (cognitive 25) crates/parcel/src/namer.rs:14— DefaultNamer::name has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 6 (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.
client.finalize (cognitive 25) crates/parcel/src/analyzer/client.js:168— client.finalize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (10 pts), boolean chains 4 (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.
LessFileManager.loadFile (cognitive 25) packages-v3/less/src/LessTransformer.ts:79— LessFileManager.loadFile has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1, ternaries 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. This shape REPEATS in the file: one other method here (LessTransformer.resolvePathPlugin.install) 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.
LessTransformer.resolvePathPlugin.install (cognitive 25) packages-v3/less/src/LessTransformer.ts:69— LessTransformer.resolvePathPlugin.install has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1, ternaries 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. This shape REPEATS in the file: one other method here (LessFileManager.loadFile) 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.
Search::verdict (cognitive 24) crates/parcel/src/bundler/optimizer.rs:1147— Search::verdict has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 5 (6 pts), boolean chains 4 (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.
(anonymous) (cognitive 24) crates/parcel/src/analyzer/client.js:2— (anonymous) has cognitive complexity 24 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (7 pts), ternaries 2 (4 pts), boolean chains 2, other 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Walk::visit (cognitive 23) crates/css/src/bundling.rs:370— Walk::visit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StylusTransformer.getDependencies (cognitive 23) packages-v3/stylus/src/StylusTransformer.ts:92— StylusTransformer.getDependencies has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (6 pts), boolean chains 5, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 127). 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.
MemoryFileSystem::create_dir_all (cognitive 22) crates/core/src/fs/memory.rs:271— MemoryFileSystem::create_dir_all has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (7 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.
createResourcesValueProxy (cognitive 22) packages-v3/rsc/src/runtime-helpers.js:49— createResourcesValueProxy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (get, get, apply, …). 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.
SerializableHandle::serialize (cognitive 21) crates/html/src/arena.rs:578— SerializableHandle::serialize has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (11 pts), match/switch 3 (6 pts), if/else 1 (4 pts) (nesting depth added 13). 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.
CLIReporter::report (cognitive 21) crates/parcel/src/main.rs:487— CLIReporter::report has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EntryIter::next (cognitive 21) crates/parcel-resolver/src/package_json.rs:881— EntryIter::next has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::process (cognitive 20) crates/core/src/packaging.rs:439— Scheduler::process has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 5 (6 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.
BundleReference::create_element (cognitive 20) crates/html/src/package.rs:39— BundleReference::create_element has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TsConfig::paths (cognitive 20) crates/parcel-resolver/src/tsconfig.rs:193— TsConfig::paths has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CPlugin::optimize (cognitive 19) crates/parcel-plugin-abi/src/plugin.rs:754— CPlugin::optimize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 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.
parcel_plugin_abi::dependency::parcel_asset_resolve (cognitive 19) crates/parcel-plugin-abi/src/dependency.rs:311— parcel_plugin_abi::dependency::parcel_asset_resolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExportsField::convert_paths (cognitive 19) crates/parcel-resolver/src/package_json.rs:157— ExportsField::convert_paths has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ModuleLoader::load (cognitive 19) crates/plugin-js/src/esm.rs:127— ModuleLoader::load has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2 (3 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.
JsPlugin::resolve (cognitive 19) crates/plugin-js/src/plugin.rs:487— JsPlugin::resolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2 (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.
ParcelImporter::canonicalize (cognitive 19) crates/sass/src/lib.rs:90— ParcelImporter::canonicalize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuiltinGraph.packageForFile (cognitive 19) crates/plugin-js/buildBuiltins.cjs:227— BuiltinGraph.packageForFile has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
buildBuiltins.buildBuiltins (cognitive 19) crates/plugin-js/buildBuiltins.cjs:526— buildBuiltins.buildBuiltins has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EsmGraphBuilder::build (cognitive 18) crates/dev-dep-resolver/src/lib.rs:79— EsmGraphBuilder::build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (2 pts), match/switch 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runtime.require (cognitive 18) crates/js/src/runtime.js:34— runtime.require has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuiltinGraph.add (cognitive 18) crates/plugin-js/buildBuiltins.cjs:367— BuiltinGraph.add has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 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.
render (cognitive 18) crates/parcel/src/analyzer/client.js:464— render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 2 (4 pts), 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.
D2 · Cognitive Complexity· link (cognitive 18) · ×1
link (cognitive 18) crates/js/src/tla-runtime.js:148— link has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 2, ternaries 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.
BundleGraph::async_assets (cognitive 17) crates/core/src/bundle_graph.rs:383— BundleGraph::async_assets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (4 pts), match/switch 1 (3 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.
client.squarify (cognitive 17) crates/parcel/src/analyzer/client.js:335— client.squarify has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
showTooltip (cognitive 17) crates/parcel/src/analyzer/client.js:747— showTooltip has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 4, if/else 4 (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.
client.layout (cognitive 16) crates/parcel/src/analyzer/client.js:390— client.layout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, loops 3 (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.
nodePanel (cognitive 16) crates/parcel/src/analyzer/client.js:1563— nodePanel has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 2, if/else 2, other 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 4 belong to 10 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.
Module (cognitive 16) REDACTED:324— Module has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (accept, a function literal at line 362, a function literal at line 361, …). 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×1
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/plugin-js/src/fs.rs:393— crates/plugin-js/src/fs.rs:393-408 | crates/plugin-js/src/fs.rs:418-433 | crates/plugin-js/src/fs.rs:454-468 | crates/plugin-js/src/fs.rs:485-499 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) crates/html/src/lib.rs:276— crates/html/src/lib.rs:276-313 | crates/html/src/lib.rs:361-388 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) crates/html/src/lib.rs:126— crates/html/src/lib.rs:126-158 | crates/html/src/xml.rs:103-134 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/core/src/resolver.rs:122— crates/core/src/resolver.rs:122-147 | crates/parcel-resolver/src/specifier.rs:242-270 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) crates/core/src/fs/memory.rs:168— crates/core/src/fs/memory.rs:168-189 | crates/core/src/fs/memory.rs:228-241 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) crates/html/src/optimize.rs:545— crates/html/src/optimize.rs:545-566 | crates/html/src/optimize.rs:572-592 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) crates/core/src/path.rs:575— crates/core/src/path.rs:575-599 | crates/core/src/path.rs:614-644 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) crates/js/src/transformer/dependency_collector.rs:651— crates/js/src/transformer/dependency_collector.rs:651-677 | crates/js/src/transformer/dependency_collector.rs:679-707 | crates/js/src/transformer/dependency_collector.rs:709-731 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) crates/plugin-js/src/fs.rs:132— crates/plugin-js/src/fs.rs:132-146 | crates/plugin-js/src/fs.rs:151-165 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) crates/parcel/src/trust/windows.rs:100— crates/parcel/src/trust/windows.rs:100-127 | crates/parcel/src/trust/windows.rs:129-150 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) crates/parcel/src/json.rs:13— crates/parcel/src/json.rs:13-27 | crates/parcel/src/toml.rs:14-24 | crates/parcel/src/yaml.rs:14-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) crates/parcel-plugin-abi/src/asset.rs:72— crates/parcel-plugin-abi/src/asset.rs:72-87 | crates/parcel-plugin-abi/src/asset.rs:97-112 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) crates/html/src/optimize.rs:474— crates/html/src/optimize.rs:474-487 | crates/html/src/optimize.rs:494-509 | crates/html/src/optimize.rs:512-525 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) crates/parcel-plugin-abi/src/asset.rs:451— crates/parcel-plugin-abi/src/asset.rs:451-472 | crates/parcel-plugin-abi/src/asset.rs:478-487 | crates/parcel-plugin-abi/src/asset.rs:514-523 | crates/parcel-plugin-abi/src/asset.rs:572-581 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) crates/parcel-resolver/src/lib.rs:195— crates/parcel-resolver/src/lib.rs:195-206 | crates/parcel-resolver/src/lib.rs:209-220 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) crates/parcel-plugin-abi/src/diagnostics.rs:87— crates/parcel-plugin-abi/src/diagnostics.rs:87-94 | crates/parcel-plugin-abi/src/diagnostics.rs:111-118 | crates/parcel-plugin-abi/src/diagnostics.rs:127-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) crates/parcel-plugin-abi/src/bundle.rs:54— crates/parcel-plugin-abi/src/bundle.rs:54-60 | crates/parcel-plugin-abi/src/bundle.rs:166-174 | crates/parcel-plugin-abi/src/bundle.rs:178-186 | crates/parcel-plugin-abi/src/bundle.rs:191-199 | crates/parcel-plugin-abi/src/target.rs:229-235 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) crates/parcel/src/bundler/bit_matrix.rs:107— crates/parcel/src/bundler/bit_matrix.rs:107-110 | crates/parcel/src/bundler/bit_matrix.rs:158-166 | crates/parcel/src/bundler/bit_matrix.rs:168-176 | crates/parcel/src/bundler/bit_matrix.rs:178-186 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) crates/plugin-js/src/cjs.rs:50— crates/plugin-js/src/cjs.rs:50-55 | crates/plugin-js/src/esm.rs:43-52 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:120— plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:120-123 | plugin-swift/Sources/ParcelPlugin/Dependency.swift:155-158 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) plugin-swift/Sources/ParcelPlugin/Asset.swift:31— plugin-swift/Sources/ParcelPlugin/Asset.swift:31-34 | plugin-swift/Sources/ParcelPlugin/BundleGraph.swift:18-21 | plugin-swift/Sources/ParcelPlugin/Dependency.swift:97-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (43 lines × 2) crates/html/src/serialize_html.rs:110— crates/html/src/serialize_html.rs:110-152 | crates/html/src/serialize_xml.rs:127-169 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 2) crates/plugin-js/src/path.rs:185— crates/plugin-js/src/path.rs:185-213 | crates/plugin-js/src/path.rs:271-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/path.rs:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) crates/js/src/transformer/collect.rs:502— crates/js/src/transformer/collect.rs:502-523 | crates/js/src/transformer/collect.rs:525-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20–21 lines × 2) crates/css/src/packager.rs:494— crates/css/src/packager.rs:494-513 | crates/css/src/packager.rs:531-551 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/packager.rs:494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) crates/css/src/packager.rs:570— crates/css/src/packager.rs:570-586 | crates/css/src/packager.rs:879-895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 3) crates/css/src/packager.rs:206— crates/css/src/packager.rs:206-221 | crates/css/src/transformer.rs:147-162 | crates/css/src/transformer.rs:622-637 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (14 lines × 2) crates/parcel-plugin-abi/src/asset.rs:242— crates/parcel-plugin-abi/src/asset.rs:242-255 | crates/parcel-plugin-abi/src/asset.rs:261-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–14 lines × 2) crates/plugin-js/src/url.rs:144— crates/plugin-js/src/url.rs:144-156 | crates/plugin-js/src/url.rs:167-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/url.rs:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/plugin-js/src/fs.rs:135— crates/plugin-js/src/fs.rs:135-146 | crates/plugin-js/src/fs.rs:154-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/fs.rs:135` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–11 lines × 2) crates/css/src/transformer.rs:134— crates/css/src/transformer.rs:134-144 | crates/css/src/transformer.rs:302-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/transformer.rs:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/css/src/transformer.rs:132` calls `clone` and `crates/css/src/transformer.rs:301` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) crates/plugin-js/src/url.rs:356— crates/plugin-js/src/url.rs:356-365 | crates/plugin-js/src/url.rs:373-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/url.rs:373` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/plugin-js/src/url.rs:367` calls `Err` and `crates/plugin-js/src/url.rs:384` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) crates/html/src/lib.rs:79— crates/html/src/lib.rs:79-88 | crates/html/src/lib.rs:277-286 | crates/html/src/lib.rs:362-371 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `TransformOptions` in one and `PackageOptions` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–10 lines × 3) crates/plugin-js/src/plugin.rs:132— crates/plugin-js/src/plugin.rs:132-141 | crates/plugin-js/src/plugin.rs:506-515 | crates/plugin-js/src/plugin.rs:606-614 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) crates/plugin-js/src/fs.rs:396— crates/plugin-js/src/fs.rs:396-405 | crates/plugin-js/src/fs.rs:421-430 | crates/plugin-js/src/fs.rs:457-465 | crates/plugin-js/src/fs.rs:488-496 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/plugin-js/src/fs.rs:396` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) crates/css/src/transformer.rs:230— crates/css/src/transformer.rs:230-247 | crates/css/src/transformer.rs:267-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/css/src/transformer.rs:287` calls `insert` and `crates/css/src/transformer.rs:249` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) crates/highlight/src/js.rs:256— crates/highlight/src/js.rs:256-263 | crates/highlight/src/js.rs:292-299 | crates/highlight/src/js.rs:348-355 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/highlight/src/js.rs:256` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) crates/css/src/packager.rs:378— crates/css/src/packager.rs:378-383 | crates/css/src/packager.rs:488-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/css/src/packager.rs:378` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) crates/js/src/packager/tree_shake.rs:581— crates/js/src/packager/tree_shake.rs:581-586 | crates/js/src/packager/tree_shake.rs:591-596 | crates/js/src/packager/tree_shake.rs:601-606 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/js/src/packager/tree_shake.rs:581` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–6 lines × 3) crates/html/src/lib.rs:666— crates/html/src/lib.rs:666-669 | crates/js/src/packager/dependencies.rs:217-222 | crates/js/src/packager/rsc.rs:471-475 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/html/src/lib.rs:666` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/js/src/packager/rsc.rs:475` calls `sort_unstable`, `dedup` and `crates/js/src/packager/dependencies.rs:222` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Type Safety — 21 typed · 23 plain JS — the untyped files are REDACTED, crates/js/src/runtime.js, crates/js/src/runtime_modules/esmodule-helpers.js, crates/js/src/runtime_modules/mdx-components.jsx, crates/js/src/runtime_modules/react-refresh-runtime.development.js, crates/js/src/runtime_modules/react-refresh.js (+17 more). 0 production file(s) opt out entirely with @ts-nocheck · 6 @ts-ignore suppression(s).
R10 · Code Duplication· Duplicated block with local edits (111 matched lines × 2 locations) · ×1
Duplicated block with local edits (111 matched lines × 2 locations) REDACTED:25— REDACTED:25 · crates/js/src/runtime.js:6 — the two spans are one implementation copied and then locally edited — 710 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 (69 matched lines × 2 locations) · ×1
Duplicated block with local edits (69 matched lines × 2 locations) packages-v3/postcss/src/PostCSSTransformer.ts:21— packages-v3/postcss/src/PostCSSTransformer.ts:21 · packages-v3/posthtml/src/PostHTMLTransformer.ts:22 — the two spans are one implementation copied and then locally edited — 419 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 (24 lines × 2 locations) crates/plugin-js/builtin-src/path-win32.js:235— crates/plugin-js/builtin-src/path-win32.js:235 · crates/plugin-js/builtin-src/path-win32.js:355 — 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 (22 lines × 2 locations) crates/plugin-js/builtin-src/path-win32.js:997— crates/plugin-js/builtin-src/path-win32.js:997 · crates/plugin-js/builtin-src/path-win32.js:1147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2 locations) crates/plugin-js/builtin-src/path-win32.js:811— crates/plugin-js/builtin-src/path-win32.js:811 · crates/plugin-js/builtin-src/path-win32.js:1076 — 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 (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) gulpfile.js:54— gulpfile.js:54 · gulpfile.js:77 — the two spans are one implementation copied and then locally edited — 110 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 (16 lines × 2 locations) REDACTED:108— REDACTED:108 · crates/js/src/runtime_modules/esmodule-helpers.js:9 — 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 (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) crates/js/src/runtime_modules/react-refresh-runtime.development.js:310— crates/js/src/runtime_modules/react-refresh-runtime.development.js:310 · crates/js/src/runtime_modules/react-refresh-runtime.development.js:326 — the two spans are one implementation copied and then locally edited — 66 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 (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) crates/js/src/runtime_modules/react-refresh.js:173— crates/js/src/runtime_modules/react-refresh.js:173 · crates/js/src/runtime_modules/react-refresh.js:191 — the two spans are one implementation copied and then locally edited — 76 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 (11 lines × 2 locations) crates/plugin-js/builtin-src/path-win32.js:655— crates/plugin-js/builtin-src/path-win32.js:655 · crates/plugin-js/builtin-src/path-win32.js:671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2 locations) packages-v3/rsc/src/node.tsx:59— packages-v3/rsc/src/node.tsx:59 · packages-v3/rsc/src/server.tsx:101 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (8 lines × 2 locations) REDACTED:611— REDACTED:611 · REDACTED:1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2 locations) crates/plugin-js/builtin-src/native-zlib/index.js:198— crates/plugin-js/builtin-src/native-zlib/index.js:198 · crates/plugin-js/builtin-src/native-zlib/index.js:205 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (5 lines × 2 locations) crates/plugin-js/buildBuiltins.cjs:437— crates/plugin-js/buildBuiltins.cjs:437 · crates/plugin-js/buildBuiltins.cjs:450 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function normalize (cyclomatic 48, cognitive 92) crates/plugin-js/builtin-src/path-win32.js:339— normalize has cyclomatic complexity 48 and cognitive complexity 92; 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 resolve (cyclomatic 46, cognitive 108) crates/plugin-js/builtin-src/path-win32.js:179— resolve has cyclomatic complexity 46 and cognitive complexity 108; 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 relative (cyclomatic 42, cognitive 67) crates/plugin-js/builtin-src/path-win32.js:599— relative has cyclomatic complexity 42 and cognitive complexity 67; 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 parse (cyclomatic 40, cognitive 71) crates/plugin-js/builtin-src/path-win32.js:1051— parse has cyclomatic complexity 40 and cognitive complexity 71; 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 assetPanel (cyclomatic 31, cognitive 45) crates/parcel/src/analyzer/client.js:1364— assetPanel has cyclomatic complexity 31 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 dirname (cyclomatic 27, cognitive 56) crates/plugin-js/builtin-src/path-win32.js:792— dirname has cyclomatic complexity 27 and cognitive complexity 56; 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 basename (cyclomatic 23, cognitive 49) crates/plugin-js/builtin-src/path-win32.js:888— basename has cyclomatic complexity 23 and cognitive complexity 49; 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 join (cyclomatic 23, cognitive 41) crates/plugin-js/builtin-src/path-win32.js:495— join has cyclomatic complexity 23 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 normalizeString (cyclomatic 20, cognitive 49) crates/plugin-js/builtin-src/path-win32.js:81— normalizeString has cyclomatic complexity 20 and cognitive complexity 49; 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 evaluate (cyclomatic 19, cognitive 21) scripts/bundle-optimizer-prototype/model.mjs:115— evaluate has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 17) crates/js/src/runtime_modules/react-refresh-runtime.development.js:267— (anonymous) has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function showTooltip (cyclomatic 19, cognitive 17) crates/parcel/src/analyzer/client.js:747— showTooltip has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function readPackage (cyclomatic 18, cognitive 28) crates/plugin-js/buildBuiltins.cjs:254— readPackage has cyclomatic complexity 18 and cognitive complexity 28; 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 validate (cyclomatic 18, cognitive 27) scripts/bundle-optimizer-prototype/model.mjs:282— validate has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function extname (cyclomatic 18, cognitive 21) crates/plugin-js/builtin-src/path-win32.js:975— extname has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function bestCandidate (cyclomatic 17, cognitive 32) scripts/bundle-optimizer-prototype/model.mjs:245— bestCandidate has cyclomatic complexity 17 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 handleMessage (cyclomatic 17, cognitive 30) REDACTED:545— handleMessage has cyclomatic complexity 17 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onCommitFiberRoot (cyclomatic 16, cognitive 18) crates/js/src/runtime_modules/react-refresh-runtime.development.js:196— onCommitFiberRoot has cyclomatic complexity 16 and cognitive complexity 18; 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 finalize (cyclomatic 15, cognitive 25) crates/parcel/src/analyzer/client.js:168— finalize has cyclomatic complexity 15 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 prepare (cyclomatic 15, cognitive 17) scripts/bundle-optimizer-prototype/model.mjs:24— prepare has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 20) packages-v3/stylus/src/StylusTransformer.ts:127— (anonymous) has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function add (cyclomatic 14, cognitive 18) crates/plugin-js/buildBuiltins.cjs:367— add has cyclomatic complexity 14 and cognitive complexity 18; 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 layout (cyclomatic 14, cognitive 16) crates/parcel/src/analyzer/client.js:390— layout has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadFile (cyclomatic 13, cognitive 25) packages-v3/less/src/LessTransformer.ts:79— loadFile has cyclomatic complexity 13 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 (anonymous) (cyclomatic 13, cognitive 24) crates/parcel/src/analyzer/client.js:2— (anonymous) has cyclomatic complexity 13 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildBuiltins (cyclomatic 13, cognitive 19) crates/plugin-js/buildBuiltins.cjs:526— buildBuiltins has cyclomatic complexity 13 and cognitive complexity 19; 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 render (cyclomatic 13, cognitive 18) crates/parcel/src/analyzer/client.js:464— render has cyclomatic complexity 13 and cognitive complexity 18; 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 isLikelyComponentType (cyclomatic 13, cognitive 17) crates/js/src/runtime_modules/react-refresh-runtime.development.js:232— isLikelyComponentType has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fixtures (cyclomatic 13, cognitive 17) scripts/bundle-optimizer-prototype/graphs.mjs:34— fixtures has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function visit (cyclomatic 13, cognitive 12) crates/plugin-js/buildBuiltins.cjs:172— visit has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function hmrApply (cyclomatic 12, cognitive 29) REDACTED:912— hmrApply has cyclomatic complexity 12 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 parcelRequire (cyclomatic 12, cognitive 23) REDACTED:34— parcelRequire has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function link (cyclomatic 12, cognitive 18) · ×1
Complex function link (cyclomatic 12, cognitive 18) crates/js/src/tla-runtime.js:148— link has cyclomatic complexity 12 and cognitive complexity 18; 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 evaluate (cyclomatic 12, cognitive 15) crates/js/src/tla-runtime.js:38— evaluate has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 12, cognitive 13) packages-v3/postcss/src/PostCSSTransformer.ts:25— transform has cyclomatic complexity 12 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 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 validateOutput (cyclomatic 11, cognitive 24) crates/plugin-js/buildBuiltins.cjs:486— validateOutput has cyclomatic complexity 11 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generated (cyclomatic 11, cognitive 17) scripts/bundle-optimizer-prototype/graphs.mjs:108— generated has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fitModels (cyclomatic 11, cognitive 15) scripts/compression-measurement/measure.mjs:144— fitModels has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 toNamespacedPath (cyclomatic 11, cognitive 13) crates/plugin-js/builtin-src/path-win32.js:757— toNamespacedPath has cyclomatic complexity 11 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 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 isReactRefreshBoundary (cyclomatic 11, cognitive 12) crates/js/src/runtime_modules/react-refresh.js:128— isReactRefreshBoundary has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· crates/parcel/src/analyzer/client.js · ×1
crates/parcel/src/analyzer/client.js: 1623 lines of code crates/parcel/src/analyzer/client.js:1— crates/parcel/src/analyzer/client.js has 1623 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· crates/plugin-js/builtin-src/path-win32.js · ×1
crates/plugin-js/builtin-src/path-win32.js: 1115 lines of code crates/plugin-js/builtin-src/path-win32.js:1— crates/plugin-js/builtin-src/path-win32.js has 1115 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: 1056 lines of code REDACTED:1— REDACTED has 1056 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-v3/plugin/src/types.ts · ×1
packages-v3/plugin/src/types.ts: 796 lines of code packages-v3/plugin/src/types.ts:1— packages-v3/plugin/src/types.ts has 796 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· crates/plugin-js/buildBuiltins.cjs · ×1
crates/plugin-js/buildBuiltins.cjs: 547 lines of code crates/plugin-js/buildBuiltins.cjs:1— crates/plugin-js/buildBuiltins.cjs has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
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 crates/parcel/tests/fixtures/glob/glob-esm-library/index.js:1— This repository declares test tooling, and the ✓ above records that declaration — but crates/parcel/tests/fixtures/glob/glob-esm-library/index.js 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 (~1727 LoC) crates/parcel/src/analyzer/client.js— no import path from any entry point (344 application, 10 tooling, 775 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
Duplicated predicate REDACTED:14— `!previousRequire && typeof document !== 'undefined' && typeof document.querySelectorAll === 'function'` appears character-identically in 2 files — REDACTED, crates/js/src/runtime.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:239— `existing[i].href === link.href && existing[i].relList.contains('stylesheet')` appears character-identically in 2 files — REDACTED, crates/js/src/runtime.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:297— `typeof define === 'function' && define.amd` appears character-identically in 2 files — REDACTED, crates/js/src/runtime.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:5— `typeof globalThis[parcelRequireName] === 'function' && globalThis[parcelRequireName]` appears character-identically in 2 files — REDACTED, crates/js/src/runtime.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 crates/parcel/src/plugin_factory.rs:281— `cfg!(windows) && Path::new(name).is_absolute()` appears character-identically in 2 files — crates/parcel/src/plugin_factory.rs, crates/plugin-js/src/esm.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/css/src/packager.rs:624— `dep.bundle_behavior == BundleBehavior::Inline || referenced_bundle.bundle_behavior == BundleBehavior::Inline` appears character-identically in 2 files — crates/css/src/packager.rs, crates/html/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/core/src/resolver.rs:128— `input.is_empty() || !input.starts_with(ascii_alpha)` appears character-identically in 2 files — crates/core/src/resolver.rs, crates/parcel-resolver/src/specifier.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file crates/js/src/transformer/typeof_replacer.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/js/src/transformer/test_utils.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/parcel-resolver/src/url_to_path.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
redundant comment crates/parcel/src/analyzer/client.js:1087— "The bundles each bundle loads, the reverse of `loaded_by`." repeats the code it sits on: 4 of its 5 words (bundles, bundle, loads, loaded) are already in `const loads = data.bundles.map(() => []);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment crates/plugin-js/builtin-src/path-win32.js:326— "Normalize the tail path" repeats the code it sits on: 3 of its 3 words (normalize, tail, path) are already in `resolvedTail = normalizeString(resolvedTail, !resolvedAbsolute, '\\',`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 145 significant file(s) lose their only recent owner: crates/parcel-resolver/src/lib.rs, crates/js/src/transformer/dependency_collector.rs, crates/parcel-plugin/src/lib.rs, crates/parcel-plugin-abi/src/tests.rs, crates/plugin-js/src/plugin.rs, REDACTED, crates/core/src/entry.rs, crates/parcel-resolver/src/package_json.rs (+137 more). Pair on, review, or document these before any departure.
Documentation: no build, run or usage example packages-v3/babel/README.md:1— `babel` is a published package (`package.json` without `"private": true`) and neither `packages-v3/babel/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
No ADRs found crates/parcel/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `crates/parcel/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 30 project(s) overshoot their size bounds, lowering Project Cohesion to 9.3/10. The most over is `crates/core` (14215 LoC, 130 module-visible types across 2 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 — 3 of 185 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; 185 of the 210 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: crates/js/src/transformer/typeof_replacer.rs, crates/js/src/transformer/test_utils.rs, crates/parcel-resolver/src/url_to_path.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift README.md:31— README.md names Parcel 2, but the manifest declares `parcel` ^3.0.0-alpha.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/dev-dep-resolver`, `crates/parcel`, `packages-v3/create-parcel`, `packages-v3/create-parcel/templates/react-server`, `plugin-swift`.
No SAST REDACTED:7— No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch github-actions/npm/cargo/gomod · ×1
Dependabot does not watch github-actions/npm/cargo/gomod REDACTED:8— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, `cargo`, `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
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 — 3/15 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 — ~0.4 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 2623 source line(s) of the 21 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages-v3/create-parcel/templates/react-client/src/index.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default on Err crates/parcel/src/launch_editor.rs:540— `process_names` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Outdated: bitflags — `bitflags` is locked at 2.13.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.7.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: cc — `cc` is locked at 1.4.3 but 1.11.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/plugin-js/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cc` and commit the updated REDACTED.
Outdated: crossbeam-channel — `crossbeam-channel` is locked at 0.5.16 but 0.5.17 is the current stable release on crates.io, and it already satisfies the `"0.5.6"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-channel` and commit the updated REDACTED.
Outdated: either — `either` is locked at 1.17.0 but 1.19.0 is the current stable release on crates.io, and it already satisfies the `"1.15.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p either` and commit the updated REDACTED.
Outdated: fixedbitset — `fixedbitset` is locked at 0.5.7 but 0.5.9 is the current stable release on crates.io, and it already satisfies the `"0.5.7"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fixedbitset` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1.1.9"` requirement declared in crates/parcel/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.14.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2.11.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: json5 — `json5` is locked at 1.3.4 but 1.3.7 is the current stable release on crates.io, and it already satisfies the `"1.3.4"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p json5` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/parcel/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.33 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/parcel/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: papaya — `papaya` is locked at 0.2.4 but 0.2.5 is the current stable release on crates.io, and it already satisfies the `"0.2.4"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p papaya` and commit the updated REDACTED.
Outdated: ref-cast — `ref-cast` is locked at 1.0.26 but 1.0.27 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/html/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ref-cast` and commit the updated REDACTED.
Outdated: rustls — `rustls` is locked at 0.23.45 but 0.23.46 is the current stable release on crates.io, and it already satisfies the `"0.23"` requirement declared in crates/parcel/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustls` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.149"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.15.2 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1.13.2"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: swc_core — `swc_core` is locked at 84.0.3 but 84.1.0 is the current stable release on crates.io, and it already satisfies the `"84.0.3"` requirement declared in crates/html/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p swc_core` and commit the updated REDACTED.
Outdated: swc_ecma_parser — `swc_ecma_parser` is locked at 47.0.1 but 47.0.2 is the current stable release on crates.io, and it already satisfies the `"47"` requirement declared in crates/highlight/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p swc_ecma_parser` and commit the updated REDACTED.
Outdated: unicode-width — `unicode-width` is locked at 0.2.2 but 0.2.3 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/parcel/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p unicode-width` and commit the updated REDACTED.
Outdated: xxhash-rust — `xxhash-rust` is locked at 0.8.18 but 0.8.19 is the current stable release on crates.io, and it already satisfies the `"0.8.2"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p xxhash-rust` and commit the updated REDACTED.
doc comments repeat the names packages-v3/plugin/src/types.ts:871— 0 of 0 documented parameters and 1 of 150 summaries in `@parcel/plugin` only repeat the member or parameter name (e.g. "The build just started." for `BuildStartEvent`). 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 14 file(s) — `packages-v3/rsc/src/server.tsx`, `plugin-swift/Examples/Sources/AsyncPlugin/AsyncPlugin.swift`, `plugin-swift/Examples/Sources/CustomContentTransformer/CustomContentTransformer.swift`, `plugin-swift/Examples/Sources/CustomNamer/CustomNamer.swift`, `plugin-swift/Examples/Sources/CustomOptimizer/CustomOptimizer.swift`, … (+9 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d5e8-c41e-73a2-869e-b160c6ae6443 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 82 · Warnings: 736 · Recommendations: 92 · Info: 20 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 17:16 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.