Public report of ZyFou/ProceduralTerrains, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 19:01 UTC · Survey ID cd_f254e2e7b0ae4f4e93bb5e8544b8974b
ZyFou/ProceduralTerrains
Measured 17 November 2026, 18:58 UTC, at code version 8349b2c
First survey, so nothing to compare with yet
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 107,421 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Code Health, 39.2
Findings by how serious they are
98 critical1071 serious66 minor
14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 18:58 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 ▸
59of 59 dimensions measured by tools.
1226of 1235 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
59dimensions across 7 lenses, read from 107,421 lines of product code in 5 projects.
ZyFou/ProceduralTerrains is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 43.4 out of 100, which the At risk rating leaves unchanged.
Code Health, at 39.2, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is adding type checking, worth about 3.0 points. Fixing focus, motion and contrast comes next, worth about 2.6 points.
Twenty-four known security holes in the packages the code depends on can be used by attackers. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-six form fields can't be read by a screen reader. Updating the vulnerable packages, pinning each tool to an exact version and labelling the form fields would close these risks. Fixing the weaknesses the scanner points to would fix the eight security weaknesses in the code. The 14 sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 107,421 lines, about €140,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.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Business logic 11%Supporting code 7%Tests 81%
Rebuild cost: about €140,000 · Estimate
Cost to rebuild
€47,000 to €240,000, for 786 to 2,505 hours of work, about 1.0 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 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 107,421 lines of product code
Comment lines
The estimate prices 107,382 lines. Comment lines count towards the size of 107,421 lines but aren't priced as work.
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.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 finding(s) in Type Safety.
Raises the score by about 3.0 points · Medium effort · Type Safety
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 2.0 points · Medium effort · Keyboard semantics
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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Code Health, at 39.2 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 finding(s) in Type Safety. Of all the actions in this report, it raises the score most for the work it takes: about 3.0 points for medium effort, because it clears the 1 Type Safety findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 99,011 lines over the last 90 days, which is about 401,545 lines a year. At that pace, the extra work comes to an estimated 50.7 to 304.1 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.
182 modules, with 8 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 142 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.
plugins.blender.procedural_terrains uses plugins.blender.procedural_terrains.builder, so a change to plugins.blender.procedural_terrains.builder can break plugins.blender.procedural_terrains, while a change to plugins.blender.procedural_terrains can't break plugins.blender.procedural_terrains.builder.
Position
Below the diagonal: plugins.blender.procedural_terrains uses a module listed above it, which is the healthy direction.
plugins.blender.procedural_terrains uses plugins.blender.procedural_terrains.generation, so a change to plugins.blender.procedural_terrains.generation can break plugins.blender.procedural_terrains, while a change to plugins.blender.procedural_terrains can't break plugins.blender.procedural_terrains.generation.
Position
Below the diagonal: plugins.blender.procedural_terrains uses a module listed above it, which is the healthy direction.
plugins.blender.procedural_terrains uses plugins.blender.procedural_terrains.generation_builder, so a change to plugins.blender.procedural_terrains.generation_builder can break plugins.blender.procedural_terrains, while a change to plugins.blender.procedural_terrains can't break plugins.blender.procedural_terrains.generation_builder.
Position
Below the diagonal: plugins.blender.procedural_terrains uses a module listed above it, which is the healthy direction.
plugins.blender.procedural_terrains uses plugins.blender.procedural_terrains.heightfield, so a change to plugins.blender.procedural_terrains.heightfield can break plugins.blender.procedural_terrains, while a change to plugins.blender.procedural_terrains can't break plugins.blender.procedural_terrains.heightfield.
Position
Below the diagonal: plugins.blender.procedural_terrains uses a module listed above it, which is the healthy direction.
plugins.blender.procedural_terrains uses plugins.blender.procedural_terrains.transforms, so a change to plugins.blender.procedural_terrains.transforms can break plugins.blender.procedural_terrains, while a change to plugins.blender.procedural_terrains can't break plugins.blender.procedural_terrains.transforms.
Position
Below the diagonal: plugins.blender.procedural_terrains uses a module listed above it, which is the healthy direction.
src.engine.sky.InfiniteCloudLayer uses src.engine.sky.CloudSlabLayer, so a change to src.engine.sky.CloudSlabLayer can break src.engine.sky.InfiniteCloudLayer, while a change to src.engine.sky.InfiniteCloudLayer can't break src.engine.sky.CloudSlabLayer.
Position
Below the diagonal: src.engine.sky.InfiniteCloudLayer uses a module listed above it, which is the healthy direction.
src.engine.sky.realistic.RealisticCloudLayers uses src.engine.sky.CloudSlabLayer, so a change to src.engine.sky.CloudSlabLayer can break src.engine.sky.realistic.RealisticCloudLayers, while a change to src.engine.sky.realistic.RealisticCloudLayers can't break src.engine.sky.CloudSlabLayer.
Position
Below the diagonal: src.engine.sky.realistic.RealisticCloudLayers uses a module listed above it, which is the healthy direction.
src.engine.sky.realistic.RealisticCloudLayers uses src.engine.sky.PlanetCloudLayer, so a change to src.engine.sky.PlanetCloudLayer can break src.engine.sky.realistic.RealisticCloudLayers, while a change to src.engine.sky.realistic.RealisticCloudLayers can't break src.engine.sky.PlanetCloudLayer.
Position
Below the diagonal: src.engine.sky.realistic.RealisticCloudLayers uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 39.2 · Weak · gated by D1, D2, R1 ·
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
58
High / Critical
A03:2025 — Software Supply Chain Failures
36
High / Critical
Roadmap
Top priorities: Resolve the 1 finding(s) in Type Safety; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
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 — 98
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 — 1071
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 — 66
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
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 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 59 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, 1226 of 1235 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.
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 25 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 144 test source file(s) (.py, .jsx, .mjs, .js, .ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/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.
D12 Dependency Hygiene — 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. Not scored — 2 UPM declaration(s) across 2 manifest(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal needs packages.unity.com, and no committed packages-lock.json resolves a registry dependency to ask about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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 Unity UPM manifest (Packages/manifest.json or a package's package.json), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Upm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 457 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 2 hold 3.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
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 — 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. Tracing effort is measured over resolved call sites, and all 1147 sampled here came from .cjs/.js files. This repository's .jsx source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
D28 Secrets (history) — 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. `gitleaks` TIMED OUT after 75s against a 75s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
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/procedural-terrains/types/index.d.ts`, `packages/procedural-terrains/types/render.d.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 54 further occurrence(s) are not listed individually; the score already reflects all 94.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> terrain-studio@2.0.5 dev / > vite / VITE v5.4.21 ready in 208 ms / ➜ Local: http://localhost:6061/ / ➜ Network: http://172.31.7.9:6061/" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> terrain-studio@2.0.5 dev / > vite / VITE v5.4.21 ready in 208 ms / ➜ Local: http://localhost:6061/ / ➜ Network: http://172.31.7.9:6061/" No runtime evidence was gathered.
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'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.
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.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 342 further occurrence(s) are not listed individually; the score already reflects all 382.
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. 373 further occurrence(s) are not listed individually; the score already reflects all 413.
R3 Large Files — 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. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 92 further occurrence(s) are not listed individually; the score already reflects all 132.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
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.
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.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — 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 repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X5 Nullable reference types — 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
404 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App.App at 777. A further 1 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 RuntimeTerrainDocumentValidator.ValidateSplat at 16 — they are counted neither in the figure above nor in this dimension's score.
+ 246 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with App.App (cyclomatic 777), build (cyclomatic 195), NodeWorkspace.NodeWorkspace (cyclomatic 180). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 2.0 to about 2.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.
+ 290 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 31 bodies over 60 down to 60 or less in Cognitive Complexity — start with App.App (cognitive 592), build (cognitive 369), NodeWorkspace.NodeWorkspace (cognitive 219). — 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 31 together lifts Cognitive Complexity from 2.0 to about 3.9/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.2 / 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 46 FunctionTooLong finding(s) in God Classes — start with GraphCompiler.js (3), REDACTED (2), PropsAssetLibrary.jsx (2). — One of this dimension's main actionable groups (46 warning-level).
Resolve the 23 MethodTooLong finding(s) in God Classes — start with Engine.js (17), TerrainExportBuilder.js, TerrainGenerationSceneBuilder.cs. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 19 FileTooLong finding(s) in God Classes — start with Engine.js, App.jsx, TerrainMaterial.js. — One of this dimension's main actionable groups (19 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
5 duplicated block group(s) detected. 0.2 % of the production lines (209 of 107,421) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .js, .jsx (86% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (10 corresponding lines) · ×2plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411
Edited copy of a member (17 corresponding lines)plugins/blender/procedural_terrains/generation.py:428
Edited copy of a member (14 corresponding lines)plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:466
Edited copy of a member (8 corresponding lines)plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:597
Edited copy of a member (9 corresponding lines)plugins/blender/procedural_terrains/operators.py:443
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with TerrainGenerationSceneBuilder.cs, TerrainGenerator.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with generation.py. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with TerrainGenerator.cs. — One of this dimension's main actionable groups (1 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.
5 production modules (npm+Unity), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 3 of the 5 (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: Zyfou.ProceduralTerrains
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 81.4%. Measured from the JavaScript/TypeScript suite (node:test via `npm ci --ignore-scripts` in api/, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.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 25 tests. Measured on the C# suite only — at least 144 test source file(s) (.py, .jsx, .mjs, .js, .ts) went unread, so its test quality is unmeasured and is not in these counts.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root (994 tests); node:test via `npm ci --ignore-scripts` in api/ (18 tests)): measured (0 flaky).
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 100 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 100 package(s) this repository's committed lockfile installs for a consumer — its 15 production, optional and peer dependency(ies), across 3 product package.json manifest(s), and everything those install in turn. Its 16 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. Third-party code that ships WITHOUT a manifest entry was read too: 1 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 1 use a banned licence. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Unity UPM manifest (Packages/manifest.json or a package's package.json), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
Resolve the 1 Banned license finding(s) in License Compliance — start with LICENSE.txt. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: src/App.jsx (40×777=31080); src/engine/Engine.js (59×99=5841); src/landing/Landing.jsx (24×198=4752) Repeated repair below the complexity floor: src/engine/terrain/TerrainHeightBaker.js (4 of 6 changes were fixes); src/engine/sky/realistic/RealisticCloudLayers.js (3 of 5 changes were fixes); src/engine/sky/PlanetCloudLayer.js (3 of 5 changes were fixes)
Resolve the 52 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.jsx, Engine.js, Landing.jsx. — One of this dimension's main actionable groups (52 warning-level).
Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with TerrainHeightBaker.js, RealisticCloudLayers.js, PlanetCloudLayer.js. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 deducted task-comment markers across 6834 LoC (0.0/KLoC) → score 10.0. 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.
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. 45 document(s) read across 4 unit(s).
Documentation: no build, run or usage exampleplugins/unity/Packages/com.zyfou.procedural-terrains/README.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 64 declarations measured against a convention their peers follow.
`blendGlslStmt` spells `Glsl` where 62 names in the project spell it `GLSL`src/engine/terrain/noise/blendModes.js:61
`evalMaskGlsl` spells `Glsl` where 62 names in the project spell it `GLSL`src/engine/terrain/noise/masks.js:67
What to do
Resolve the 1 `blendGlslStmt` spells `Glsl` where 62 names in the project spell it… finding(s) in Naming Consistency — start with blendModes.js. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `evalMaskGlsl` spells `Glsl` where 62 names in the project spell it… finding(s) in Naming Consistency — start with masks.js. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
6 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .cjs/.js source only — this repository's .jsx was not sampled for call sites, so this score covers part of the tree, not all of it.
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).
58 finding(s): 0 critical, 21 high, 37 medium, 0 low. 13 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 6 file(s) — `packages/procedural-terrains/types/index.d.ts` (line 247, line 276, line 290), `packages/procedural-terrains/types/render.d.ts` (line 7), `src/App.jsx`, `REDACTED`, `src/engine/Engine.js`, … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 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 13 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 (13 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.
Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 368 of the 569 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 14 Boundary-crossing change coupling finding(s) in Change Coupling — start with settingsSearch.js (3), PerfSettings.jsx (2), ManualTerrainPanel.jsx (2). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with TerrainHeightSampler.js, index.jsx, InfiniteHUD.jsx. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with Engine.js, App.jsx, TerrainMaterial.js. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 9 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.6 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×6) — src/App.jsx:2791, src/components/RightPanels.jsx:44, src/components/RightPanels.jsx:288, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels6.5 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×21) — src/auth/ProfilePage.jsx:156, src/components/ColorPalettePanel.jsx:305, src/components/ColorPalettePanel.jsx:373, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×5) — src/components/ColorPalettePanel.jsx:328, REDACTED:1008, src/components/panels/QualitySettingsContent.jsx:378, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×4) — src/components/InfiniteHUD.jsx:176, src/components/NoiseLayersPanel.jsx:236, src/components/TopBar.jsx:315, …
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×4) — src/components/LeftPanel.jsx:69, src/components/NoiseLayersPanel.jsx:130, src/components/NoisePresetPanel.jsx:8, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure7.6 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — src/components/NoiseLayersPanel.jsx:106, src/landing/Landing.jsx:506
This <section role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — src/components/support/SupportDownloadModal.jsx:39, src/components/ui/RealWorldMapPicker.jsx:356
This <form role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/components/ui/ManualTerrainImportDialog.jsx:62
This <form role="alertdialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/components/ui/PopupProvider.jsx:60
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — src/components/ui/Toast.jsx:75, src/components/ui/UiSettingsPanel.jsx:27
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — src/docs/DocsPage.jsx:232
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.visuals-search-wrap` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:1651
`.prop-search-field` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:1766
`.spline-name-field > div` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:2238
`.settings-tab.active` sets color: #2563eb on background-color: #141414 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:3231
`.settings-search-item-value` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:3549
`#fps-controls-hint` sets color: #737373 on background-color: #0d0d0d — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:3919
`.minimap-fab` sets color: #2563eb on background-color: #141414 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:4770
`.minimap-fab:hover` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:4785
`.node-graph-resizer` sets color: #737373 on background-color: #0d0d0d — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5061
`.node-graph-dock .react-flow__controls-button:hover` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5103
`.node-palette-filter` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5276
`.node-inspector-search-wrap` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5356
`.node-inspector-section-toggle small` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5370
`.manual-dock-section-title span` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/styles.css:5821
`.blender-option-preview svg` sets color: white on background-color: #d36b29 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/landing/landing.css:591
`.admin-search` sets color: #60708c on background-color: #080d16 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/landing/landing.css:889
`.admin-change-chips span` sets color: #6f7889 on background-color: #090c12 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/landing/landing.css:948
`.realworld-map-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1127
`.realworld-map-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1242
`.visuals-search-wrap input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1668
`.prop-search-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1768
`.row input[type="number"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:2010
`.spline-name-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:2240
`.settings-search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:3180
`.node-template-picker select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:4954
`.node-color-preset select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5001
`.node-palette-filter input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5290
`.node-search-input input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5329
`.node-inspector-search-wrap input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5358
`.node-inspector-field > input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5379
`.manual-shape-layer-title select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:6073
`.manual-import-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:7933
`.support-download-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:648
`.admin-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:891
`.admin-filters select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:895
`.cloud-sync-bar select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:1248
`.community-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:1276
`.community-select-wrap select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:1319
`.lp-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:1373
`.lp-node-color-select select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/landing/landing.css:1665
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
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 · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to as a CI step. What was searched, so you can tell an absence from a miss: the 3 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:4
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:43
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
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.
`unzipSync` in `decodePortableProject` 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. — src/project/PortableProject.js:30
`fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×31) — tools/perf-harness/experiments/bake-blend.mjs:9, tools/perf-harness/experiments/bake-quality.mjs:21, tools/perf-harness/experiments/bake-threshold.mjs:9, …
`unzipSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — tools/perf-harness/experiments/mini-export.mjs:31
`fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — tools/perf-harness/experiments/mini-export.mjs:35, tools/perf-harness/experiments/mini-export.mjs:36, tools/perf-harness/experiments/node-project.mjs:92, …
`fs.writeFileSync` in `callback to urls.forEach` 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. — tools/perf-harness/experiments/mini-export.mjs:50
`fs.writeFileSync` in `callback to shots.forEach` 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. — tools/perf-harness/experiments/motion-frames.mjs:60
`existsSync` in `callback to middlewares.use` 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. — vite-plugins/surfaceMaterialsApi.js:79
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 Safety0.0 / 10Critical✓ 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.
1 typed · 657 plain JS — the untyped files are api/scripts/migrate.js, api/src/activity.js, REDACTED, api/src/admin-utils.js, REDACTED, api/src/auth-utils.js (+651 more).
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
41 duplicated blocks under src/ have copies in at least two of the sibling directories admin, auth, components, creator, engine, export (+7 more sibling(s) not listed) — 28 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 41 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/engine/destruction/DestructionField.js:4
21 duplicated blocks under src/engine/ have copies in at least two of the sibling directories boot, destruction, mini, mode, player, props (+4 more sibling(s) not listed) — 14 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/engine/boot/FinalFrameBootPipeline.js:22
12 duplicated blocks under src/components/ have copies in at least two of the sibling directories manual, nodes, panels, support, ui — 10 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/panels/QualitySettingsContent.jsx:374
src/engine/boot/FinalFrameBootPipeline.js:22 · src/engine/mode/ModeTransitionCoordinator.js:11 — the two spans are one implementation copied and then locally edited — 971 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. — src/engine/boot/FinalFrameBootPipeline.js:22
src/components/ui/LeftToolbar.jsx:44 · src/components/ui/SideDrawer.jsx:41 — the two spans are one implementation copied and then locally edited — 811 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. — src/components/ui/LeftToolbar.jsx:44
src/engine/terrain/MergeQuadtree.js:83 · src/engine/terrain/TerrainBoard.js:630 — the two spans are one implementation copied and then locally edited — 1069 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. — src/engine/terrain/MergeQuadtree.js:83
src/engine/sky/CloudSlabLayer.js:479 · src/engine/sky/PlanetCloudLayer.js:325 — the two spans are one implementation copied and then locally edited — 869 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. — src/engine/sky/CloudSlabLayer.js:479
src/components/ui/CloudPanel.jsx:159 · src/components/ui/CloudPanel.jsx:290 — the two spans are one implementation copied and then locally edited — 597 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. — src/components/ui/CloudPanel.jsx:159
src/engine/sky/realistic/RealisticCloudLayers.js:140 · src/engine/sky/realistic/RealisticCloudLayers.js:342 — the two spans are one implementation copied and then locally edited — 742 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. — src/engine/sky/realistic/RealisticCloudLayers.js:140
src/engine/sky/CloudSlabLayer.js:344 · src/engine/sky/PlanetCloudLayer.js:235 — the two spans are one implementation copied and then locally edited — 529 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. — src/engine/sky/CloudSlabLayer.js:344
src/engine/sky/CloudSlabShader.js:1 · src/engine/sky/CloudVolumeShader.js:1 — these 2 files are line-for-line copies of one another — 57 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/engine/sky/CloudSlabShader.js:1
src/engine/sky/realistic/RealisticCloudResources.js:241 · src/engine/sky/realistic/RealisticCloudResources.js:309 — the two spans are one implementation copied and then locally edited — 294 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. — src/engine/sky/realistic/RealisticCloudResources.js:241
src/engine/terrain/InfiniteWorld.js:246 · src/engine/terrain/PlanetWorld.js:326 — the two spans are one implementation copied and then locally edited — 352 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. — src/engine/terrain/InfiniteWorld.js:246
src/components/ui/WaterPanel.jsx:676 · src/components/ui/WaterPanel.jsx:770 — the two spans are one implementation copied and then locally edited — 237 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. — src/components/ui/WaterPanel.jsx:676
src/engine/player/PlaneController.js:66 · src/engine/player/PlanetController.js:66 — the two spans are one implementation copied and then locally edited — 357 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. — src/engine/player/PlaneController.js:66
src/manual/ManualPropPaintField.js:1 · src/manual/ManualSurfacePaintField.js:4 — 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. — src/manual/ManualPropPaintField.js:1
src/manual/ManualTerrainModeManager.js:360 · src/manual/ManualTerrainModeManager.js:409 — 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. — src/manual/ManualTerrainModeManager.js:360
src/engine/destruction/DestructionField.js:4 · src/manual/ManualSurfacePaintField.js:4 — the two spans are one implementation copied and then locally edited — 278 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. — src/engine/destruction/DestructionField.js:4
src/engine/sky/PlanetCloudChunks.js:227 · src/engine/sky/PlanetCloudLayer.js:119 — 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. — src/engine/sky/PlanetCloudChunks.js:227
tools/perf-harness/experiments/compile-attribution2.mjs:2 · tools/perf-harness/experiments/compile-attribution3.mjs:3 — 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. — tools/perf-harness/experiments/compile-attribution2.mjs:2
tools/perf-harness/experiments/mini-props-ui.mjs:18 · tools/perf-harness/experiments/mini-ui-smoke.mjs:17 — the two spans are one implementation copied and then locally edited — 346 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. — tools/perf-harness/experiments/mini-props-ui.mjs:18
REDACTED:338 · REDACTED:371 — 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. — REDACTED:338
tools/perf-harness/experiments/cloud-loops.mjs:7 · tools/perf-harness/experiments/water-loop.mjs:8 — the two spans are one implementation copied and then locally edited — 308 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. — tools/perf-harness/experiments/cloud-loops.mjs:7
src/engine/terrain/PlanetHeightSampler.js:18 · src/engine/terrain/TerrainHeightSampler.js:21 — 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. — src/engine/terrain/PlanetHeightSampler.js:18
REDACTED:307 · REDACTED:338 — 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:307
src/engine/EditorControls.js:280 · src/engine/PlanetOrbitControls.js:87 — 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. — src/engine/EditorControls.js:280
src/engine/EditorControls.js:317 · src/engine/PlanetOrbitControls.js:120 — 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. — src/engine/EditorControls.js:317
REDACTED:134 · REDACTED:154 — 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. — REDACTED:134
tools/perf-harness/experiments/planet-climate-ablation.mjs:2 · tools/perf-harness/experiments/shade-ablation.mjs:3 — the two spans are one implementation copied and then locally edited — 293 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. — tools/perf-harness/experiments/planet-climate-ablation.mjs:2
src/App.jsx:1698 · src/App.jsx:1728 — 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. — src/App.jsx:1698
src/engine/sky/CloudSlabLayer.js:174 · src/engine/sky/realistic/RealisticCloudLayers.js:184 — the two spans are one implementation copied and then locally edited — 217 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. — src/engine/sky/CloudSlabLayer.js:174
src/engine/sky/CloudSlabLayer.js:304 · src/engine/sky/PlanetCloudLayer.js:214 — 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. — src/engine/sky/CloudSlabLayer.js:304
REDACTED:100 · REDACTED:129 — 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. — REDACTED:100
tools/perf-harness/experiments/mini-circle.mjs:57 · tools/perf-harness/experiments/mini-terrain.mjs:53 — 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. — tools/perf-harness/experiments/mini-circle.mjs:57
src/engine/sky/InfiniteCloudLayer.js:13 · src/engine/sky/realistic/RealisticCloudLayers.js:309 — the two spans are one implementation copied and then locally edited — 229 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. — src/engine/sky/InfiniteCloudLayer.js:13
src/engine/Engine.js:8475 · src/engine/Engine.js:8507 — 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. — src/engine/Engine.js:8475
src/engine/sky/CloudSlabLayer.js:82 · src/engine/sky/PlanetCloudLayer.js:75 — 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. — src/engine/sky/CloudSlabLayer.js:82
src/runtime/resources/TerrainCompute.js:23 · src/runtime/resources/TerrainSurfaceWorker.js:12 — the two spans are one implementation copied and then locally edited — 129 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. — src/runtime/resources/TerrainCompute.js:23
src/components/TouchControls.jsx:52 · src/components/TouchControls.jsx:112 — 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. — src/components/TouchControls.jsx:52
src/engine/terrain/surface/SurfaceAtlasBridge.js:103 · src/engine/terrain/surface/SurfaceAtlasBridge.js:123 — the two spans are one implementation copied and then locally edited — 106 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. — src/engine/terrain/surface/SurfaceAtlasBridge.js:103
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/procedural-terrains/assets.js:1 reaches into another package with a relative path (../../src/runtime/resources/TerrainResources.js) — import the package by name instead. — packages/procedural-terrains/assets.js:1
packages/procedural-terrains/assets.js:2 reaches into another package with a relative path (../../src/runtime/resources/TerrainCompute.js) — import the package by name instead. — packages/procedural-terrains/assets.js:2
packages/procedural-terrains/assets.js:3 reaches into another package with a relative path (../../src/runtime/resources/SurfaceAssets.js) — import the package by name instead. — packages/procedural-terrains/assets.js:3
packages/procedural-terrains/assets.js:4 reaches into another package with a relative path (../../src/engine/terrain/surface/SurfaceDocument.js) — import the package by name instead. — packages/procedural-terrains/assets.js:4
packages/procedural-terrains/assets.js:5 reaches into another package with a relative path (../../src/runtime/resources/TerrainSurfaceWorker.js) — import the package by name instead. — packages/procedural-terrains/assets.js:5
packages/procedural-terrains/clouds.js:1 reaches into another package with a relative path (../../REDACTED) — import the package by name instead. — packages/procedural-terrains/clouds.js:1
packages/procedural-terrains/clouds.js:2 reaches into another package with a relative path (../../src/engine/sky/CloudSettings.js) — import the package by name instead. — packages/procedural-terrains/clouds.js:2
packages/procedural-terrains/documents.js:1 reaches into another package with a relative path (../../src/runtime/TerrainDocument.js) — import the package by name instead. — packages/procedural-terrains/documents.js:1
packages/procedural-terrains/export.js:1 reaches into another package with a relative path (../../src/runtime/export/TerrainExport.js) — import the package by name instead. — packages/procedural-terrains/export.js:1
packages/procedural-terrains/generation.js:1 reaches into another package with a relative path (../../src/engine/terrain/noise/NoiseStack.js) — import the package by name instead. — packages/procedural-terrains/generation.js:1
packages/procedural-terrains/generation.js:2 reaches into another package with a relative path (../../src/engine/terrain/graph/GraphCompiler.js) — import the package by name instead. — packages/procedural-terrains/generation.js:2
packages/procedural-terrains/generation.js:3 reaches into another package with a relative path (../../src/manual/ManualShapeCatalog.js) — import the package by name instead. — packages/procedural-terrains/generation.js:3
packages/procedural-terrains/generation.js:4 reaches into another package with a relative path (../../src/engine/terrain/graph/GraphDocument.js) — import the package by name instead. — packages/procedural-terrains/generation.js:4
packages/procedural-terrains/index.js:4 reaches into another package with a relative path (../../src/runtime/FiniteTerrain.js) — import the package by name instead. — packages/procedural-terrains/index.js:4
packages/procedural-terrains/infinite.js:1 reaches into another package with a relative path (../../src/runtime/worlds/InfiniteTerrain.js) — import the package by name instead. — packages/procedural-terrains/infinite.js:1
packages/procedural-terrains/mini.js:1 reaches into another package with a relative path (../../src/runtime/worlds/MiniTerrain.js) — import the package by name instead. — packages/procedural-terrains/mini.js:1
packages/procedural-terrains/mini.js:2 reaches into another package with a relative path (../../src/engine/mini/MiniTerrainSettings.js) — import the package by name instead. — packages/procedural-terrains/mini.js:2
packages/procedural-terrains/planet.js:1 reaches into another package with a relative path (../../src/runtime/worlds/PlanetTerrain.js) — import the package by name instead. — packages/procedural-terrains/planet.js:1
packages/procedural-terrains/real-world.js:1 reaches into another package with a relative path (../../src/runtime/providers/RealWorldTerrain.js) — import the package by name instead. — packages/procedural-terrains/real-world.js:1
packages/procedural-terrains/render.js:1 reaches into another package with a relative path (../../src/runtime/effects/TerrainRenderPipeline.js) — import the package by name instead. — packages/procedural-terrains/render.js:1
packages/procedural-terrains/render.js:2 reaches into another package with a relative path (../../src/runtime/effects/TerrainHeightCache.js) — import the package by name instead. — packages/procedural-terrains/render.js:2
packages/procedural-terrains/render.js:3 reaches into another package with a relative path (../../src/runtime/effects/TerrainDetailCache.js) — import the package by name instead. — packages/procedural-terrains/render.js:3
packages/procedural-terrains/viewer.js:1 reaches into another package with a relative path (../../src/runtime/viewer/TerrainViewer.js) — import the package by name instead. — packages/procedural-terrains/viewer.js:1
packages/procedural-terrains/water.js:1 reaches into another package with a relative path (../../REDACTED) — import the package by name instead. — packages/procedural-terrains/water.js:1
packages/procedural-terrains/water.js:2 reaches into another package with a relative path (../../src/engine/water/WaterSettings.js) — import the package by name instead. — packages/procedural-terrains/water.js:2
src/export/TerrainCodeExporter.js:9 reaches into another package with a relative path (../../packages/procedural-terrains/package.json) — import the package by name instead. — src/export/TerrainCodeExporter.js:9
tests/FiniteTerrain.test.js:3 reaches past another workspace package's public entry into its internals with a relative path (../packages/procedural-terrains/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/FiniteTerrain.test.js:3
tests/TerrainPackage.test.js:3 reaches past another workspace package's public entry into its internals with a relative path (../packages/procedural-terrains/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/TerrainPackage.test.js:3
tools/check-terrain-code-browser.mjs:20 reaches into another package with a relative path (../packages/procedural-terrains/package.json) — import the package by name instead. — tools/check-terrain-code-browser.mjs:20
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.
(anonymous) has cyclomatic complexity 225 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/App.jsx:1988
build has cyclomatic complexity 159 and cognitive complexity 301; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/terrain/TerrainExportBuilder.js:201
App has cyclomatic complexity 115 and cognitive complexity 88; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/App.jsx:147
_rebuildStackMaterialsAsync has cyclomatic complexity 100 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:4059
validateRuntimeTerrainDocument has cyclomatic complexity 94 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. — src/export/runtime/RuntimeTerrainValidator.js:18
_tickStudio has cyclomatic complexity 78 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/Engine.js:13534
PerformanceOverlay has cyclomatic complexity 73 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/components/perf/PerformanceOverlay.jsx:65
WaterPanelInner has cyclomatic complexity 70 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/components/ui/WaterPanel.jsx:244
loadSeedJSON has cyclomatic complexity 68 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/Engine.js:11742
Landing has cyclomatic complexity 67 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/landing/Landing.jsx:120
getPerfDiagnostics has cyclomatic complexity 66 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:13915
restoreState has cyclomatic complexity 58 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:12049
computeWarnings has cyclomatic complexity 57 and cognitive complexity 91; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/perf/warnings.js:23
_tickBody has cyclomatic complexity 57 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:13177
compileSurfaceGraph has cyclomatic complexity 54 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/terrain/surface/SurfaceGraph.js:23
_compileShaderBenchmarkCandidate has cyclomatic complexity 53 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:6937
applyMiniWaterLook has cyclomatic complexity 52 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/mini/MiniWaterMaterial.js:806
dispose has cyclomatic complexity 52 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:14100
_updateFlat has cyclomatic complexity 51 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/props/ProceduralPropsManager.js:319
sanitizePerfSettings has cyclomatic complexity 49 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/render/PerformanceSettings.js:265
ManualTerrainPanel has cyclomatic complexity 49 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/components/manual/ManualTerrainPanel.jsx:188
_compileMaterialVariants has cyclomatic complexity 48 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:5832
_warmDeferredWaterImpl has cyclomatic complexity 48 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. — src/engine/Engine.js:8044
_setDebugFreeCam has cyclomatic complexity 47 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/Engine.js:8633
applyRealisticWaterUniforms has cyclomatic complexity 47 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/water/RealisticWaterMaterial.js:1210
applyParams has cyclomatic complexity 46 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/sky/CloudSlabLayer.js:186
NodeWorkspace has cyclomatic complexity 44 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:460
setParam has cyclomatic complexity 41 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. — src/engine/Engine.js:2776
update has cyclomatic complexity 40 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/sky/PlanetCloudChunks.js:351
validateExport has cyclomatic complexity 40 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/export/ExportValidator.js:7
createTerrainCodeDocument has cyclomatic complexity 40 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/export/TerrainCodeExporter.js:17
_sceneRevisionKey has cyclomatic complexity 39 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:5465
TopBar has cyclomatic complexity 39 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/components/TopBar.jsx:44
_completeBootIfQualityReady has cyclomatic complexity 39 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:7359
_setWorldModeImmediate has cyclomatic complexity 38 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/Engine.js:9681
_warmupPlanetShaders has cyclomatic complexity 38 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. — src/engine/Engine.js:10838
newProject has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/engine/Engine.js:2952
_ensureTerrainShaderVariantAsync has cyclomatic complexity 37 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/Engine.js:11251
applyParams has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/engine/sky/PlanetCloudLayer.js:128
erode has cyclomatic complexity 36 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/engine/terrain/erosion/erosionSim.js:85
Do you agree with this assessment?
R3 · Large Files5.7 / 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.
src/engine/Engine.js has 13464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/Engine.js:1
src/App.jsx has 2916 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/App.jsx:1
src/engine/terrain/TerrainMaterial.js has 1600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/TerrainMaterial.js:1
src/engine/water/RealisticWaterMaterial.js has 1220 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/water/RealisticWaterMaterial.js:1
src/engine/terrain/graph/GraphCompiler.js has 1147 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/graph/GraphCompiler.js:1
src/manual/ManualTerrainModeManager.js has 1138 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/manual/ManualTerrainModeManager.js:1
src/engine/water/WaterSystem.js has 1126 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/water/WaterSystem.js:1
src/components/panels/index.jsx has 1092 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/panels/index.jsx:1
REDACTED has 1015 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
src/engine/terrain/terrainGLSL.js has 946 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/terrainGLSL.js:1
src/engine/props/ProceduralPropsManager.js has 935 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/props/ProceduralPropsManager.js:1
src/engine/mini/MiniWaterMaterial.js has 895 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/mini/MiniWaterMaterial.js:1
src/engine/terrain/TerrainExportBuilder.js has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/TerrainExportBuilder.js:1
src/components/manual/ManualTerrainPanel.jsx has 867 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/manual/ManualTerrainPanel.jsx:1
src/components/ui/WaterPanel.jsx has 820 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/ui/WaterPanel.jsx:1
src/engine/terrain/TerrainBoard.js has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/TerrainBoard.js:1
src/landing/Landing.jsx has 781 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/landing/Landing.jsx:1
src/engine/mini/MiniTerrainSettings.js has 702 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/mini/MiniTerrainSettings.js:1
src/engine/terrain/PlanetWorld.js has 670 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/PlanetWorld.js:1
src/engine/terrain/RealWorldHeightmap.js has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/RealWorldHeightmap.js:1
src/engine/sky/CloudSlabLayer.js has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/sky/CloudSlabLayer.js:1
src/engine/sky/realistic/realisticCloudGLSL.js has 619 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/sky/realistic/realisticCloudGLSL.js:1
tools/perf-harness/harness-entry.js has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/perf-harness/harness-entry.js:1
REDACTED has 587 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
src/engine/mini/MiniTerrainController.js has 576 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/mini/MiniTerrainController.js:1
src/engine/render/VisualPostProcess.js has 572 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/render/VisualPostProcess.js:1
src/engine/terrain/PlanetMaterial.js has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/PlanetMaterial.js:1
src/manual/ManualTerrainField.js has 554 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/manual/ManualTerrainField.js:1
src/runtime/FiniteTerrain.js has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/runtime/FiniteTerrain.js:1
src/components/panels/QualitySettingsContent.jsx has 538 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/panels/QualitySettingsContent.jsx:1
src/components/ui/ImportMapsContent.jsx has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/ui/ImportMapsContent.jsx:1
src/engine/terrain/surface/terrainSurfaceTextureGLSL.js has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/surface/terrainSurfaceTextureGLSL.js:1
src/engine/sky/PlanetCloudChunks.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/sky/PlanetCloudChunks.js:1
src/engine/terrain/noise/noiseTypes.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/noise/noiseTypes.js:1
src/engine/terrain/graph/GraphRegistry.js has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/graph/GraphRegistry.js:1
src/engine/terrain/InfiniteWorld.js has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/terrain/InfiniteWorld.js:1
src/engine/EngineProxy.js has 480 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/EngineProxy.js:1
src/components/ui/RealWorldMapPicker.jsx has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/ui/RealWorldMapPicker.jsx:1
src/engine/destruction/DestructionField.js has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/engine/destruction/DestructionField.js:1
src/components/NoiseLayersPanel.jsx has 471 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/NoiseLayersPanel.jsx: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 Coverage9.7 / 10Exemplary✓ 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.
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. (×13) — REDACTED:1, REDACTED:1, REDACTED:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ 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.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code6.3 / 10Adequate✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 88 application, 18 tooling and 138 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (88 application, 18 tooling, 138 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 (×39) — tools/perf-harness/harness-entry.js, src/project/CloudProjectsPanel.jsx, tools/perf-harness/experiments/mini-light-cost.mjs, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — tests/Playground.test.js:3
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — package.json:48
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 11 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 — 67 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
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 — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> terrain-studio@2.0.5 dev / > vite / VITE v5.4.21 ready in 208 ms / ➜ Local: http://localhost:6061/ / ➜ Network: http://172.31.7.9:6061/" 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D12 Dependency Hygiene — Not scored — 2 UPM declaration(s) across 2 manifest(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal needs packages.unity.com, and no committed packages-lock.json resolves a registry dependency to ask about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 0 exposed C# types.
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
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D28 Secrets (history) — gitleaks killed before it finished — this repository's working tree not scanned
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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (10 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — IC1 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 measured — the application kind could not be determined for this repo
P9 Domain vs controller coverage — coverage data present for 11 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 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 — no async method does work a token could cancel
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — X25 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — X29 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X3 Exception handling — X3 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — X4 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X5 Nullable reference types — X5 reached only 4% of this repository's production lines — javascript (100,562 lines), python (2,760 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×17
<input> without a programmatic label src/auth/ProfilePage.jsx:156— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/ColorPalettePanel.jsx:328— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/InfiniteHUD.jsx:147— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/LeftPanel.jsx:78— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/NoiseLayersPanel.jsx:131— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/RightPanels.jsx:94— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/RightPanels.jsx:121— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/RightPanels.jsx:138— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label REDACTED:308— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label REDACTED:1008— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/panels/QualitySettingsContent.jsx:378— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/panels/index.jsx:559— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/ui/ImportMapsContent.jsx:53— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/ui/ImportMapsContent.jsx:257— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/ui/SettingsSearchOverlay.jsx:72— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:166— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/docs/Markdown.jsx:172— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
Boundary-crossing change coupling: InfiniteHUD.jsx ↔ Engine.js src/components/InfiniteHUD.jsx:1— `src/components/InfiniteHUD.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `f5991806` phase 1; `b232e1e1` free cam; `ebf484f7` Enhance performance settings with GPU and renderer options — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ GraphCompiler.js REDACTED:1— `REDACTED` (context components) and `src/engine/terrain/graph/GraphCompiler.js` (context engine) sit in DIFFERENT parts of the tree yet change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7184f082` fixed water in node mode and improved lake; `a7747622` better node compiling; `bca60a74` Update terrain rendering and interaction flows — run `git show` on any of them.
Boundary-crossing change coupling: PerfSettings.jsx ↔ Engine.js src/components/panels/PerfSettings.jsx:1— `src/components/panels/PerfSettings.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 74% of the time (14 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `36ecfd91` visual filters; `c8948c55` Replace chunk group merges with quadtree folding; `e9190483` chunk merging — run `git show` on any of them.
Boundary-crossing change coupling: settingsSearch.js ↔ panelResets.js src/components/panels/settingsSearch.js:1— `src/components/panels/settingsSearch.js` (context components) and `src/engine/panelResets.js` (context engine) sit in DIFFERENT parts of the tree yet change together 71% of the time (12 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `b378e0e2` props tab changes; `241ecb3d` Add shared water lighting system and UI controls; `2de61669` ground shadows and godrays — run `git show` on any of them.
Boundary-crossing change coupling: ManualTerrainPanel.jsx ↔ ManualTerrainModeManager.js src/components/manual/ManualTerrainPanel.jsx:1— `src/components/manual/ManualTerrainPanel.jsx` (context components) and `src/manual/ManualTerrainModeManager.js` (context manual) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8882276b` Add procedural shape modifier layers to manual terrain; `d651c3d0` terrain painter fixes; `7d5eb53b` Add direct texture painting for manual terrain surfaces — run `git show` on any of them.
Boundary-crossing change coupling: StatusBar.jsx ↔ Engine.js src/components/StatusBar.jsx:1— `src/components/StatusBar.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f5991806` phase 1; `0ee917c6` performanace fixes and animation; `5ca43d58` plane mode prototype — run `git show` on any of them.
Boundary-crossing change coupling: settingsSearch.js ↔ Engine.js src/components/panels/settingsSearch.js:1— `src/components/panels/settingsSearch.js` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 68% of the time (21 of the 31 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 21 shared commits counted here, the most recent 3 are `6b4954c5` Add non-destructive reference images for Tile authoring; `27b68af9` fixed real terrains issues, missing resolutions fixes and improved re…; `d6b33230` new clouds :O — run `git show` on any of them.
Boundary-crossing change coupling: PerfSettings.jsx ↔ PerformanceSettings.js src/components/panels/PerfSettings.jsx:1— `src/components/panels/PerfSettings.jsx` (context components) and `src/engine/render/PerformanceSettings.js` (context engine) sit in DIFFERENT parts of the tree yet change together 67% of the time (12 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `f4ee42b4` feat: add opt-in spatial upscaler and reconstruction comparison controls; `36ecfd91` visual filters; `c8948c55` Replace chunk group merges with quadtree folding — run `git show` on any of them.
Boundary-crossing change coupling: ImportMapsContent.jsx ↔ Engine.js src/components/ui/ImportMapsContent.jsx:1— `src/components/ui/ImportMapsContent.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `6b4954c5` Add non-destructive reference images for Tile authoring; `27b68af9` fixed real terrains issues, missing resolutions fixes and improved re…; `b176396e` fixes — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ Engine.js REDACTED:1— `REDACTED` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `79179464` Constrain surface texture scale to 0.1x through 5x; `f14a8299` Keep surface texture colors clean and extend scale to 20x; `322800d4` Improve PBR snow, sand, slope blending, and texture scale — run `git show` on any of them.
Boundary-crossing change coupling: TopBar.jsx ↔ Engine.js src/components/TopBar.jsx:1— `src/components/TopBar.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 56% of the time (14 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `8a7bda2d` standalon windows app; `784bfa58` small tweaks and fixes; `7e82d4c5` Add hybrid Manual Terrain imports — run `git show` on any of them.
Boundary-crossing change coupling: index.jsx ↔ panelResets.js src/components/panels/index.jsx:1— `src/components/panels/index.jsx` (context components) and `src/engine/panelResets.js` (context engine) sit in DIFFERENT parts of the tree yet change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `b378e0e2` props tab changes; `2de61669` ground shadows and godrays; `b232e1e1` free cam — run `git show` on any of them.
Boundary-crossing change coupling: settingsSearch.js ↔ PerformanceSettings.js src/components/panels/settingsSearch.js:1— `src/components/panels/settingsSearch.js` (context components) and `src/engine/render/PerformanceSettings.js` (context engine) sit in DIFFERENT parts of the tree yet change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `d6b33230` new clouds :O; `36ecfd91` visual filters; `c8948c55` Replace chunk group merges with quadtree folding — run `git show` on any of them.
Boundary-crossing change coupling: ManualTerrainPanel.jsx ↔ Engine.js src/components/manual/ManualTerrainPanel.jsx:1— `src/components/manual/ManualTerrainPanel.jsx` (context components) and `src/engine/Engine.js` (context engine) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `8882276b` Add procedural shape modifier layers to manual terrain; `d651c3d0` terrain painter fixes; `7d5eb53b` Add direct texture painting for manual terrain surfaces — run `git show` on any of them.
AC2 · Forms & labels· <select> without a programmatic label · ×9
<select> without a programmatic label src/components/ColorPalettePanel.jsx:305— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/ColorPalettePanel.jsx:373— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/InfiniteHUD.jsx:129— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/InfiniteHUD.jsx:160— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/LeftPanel.jsx:70— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/NoiseLayersPanel.jsx:215— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/NoisePresetPanel.jsx:9— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/PlanetPresetPanel.jsx:24— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label src/components/RightPanels.jsx:74— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×4
<button> with no accessible text src/components/InfiniteHUD.jsx:176— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/components/NoiseLayersPanel.jsx:236— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/components/TopBar.jsx:315— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text REDACTED:1013— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control src/components/LeftPanel.jsx:69— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/components/NoiseLayersPanel.jsx:130— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/components/NoisePresetPanel.jsx:8— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/components/panels/QualitySettingsContent.jsx:121— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×3
Click handler on a non-interactive <div> src/components/NoiseLayersPanel.jsx:106— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/docs/DocsPage.jsx:232— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> src/landing/Landing.jsx:506— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Banned license: procedural_terrains plugins/blender/procedural_terrains/LICENSE.txt:1— `procedural_terrains` ships inside this repository without a manifest entry: it is a copy of another project's code in a directory of this repository that carries its own licence, and its licence is stated in its licence file `plugins/blender/procedural_terrains/LICENSE.txt`. It carries `GPL-3.0`, which this policy bans. Code copied or bundled into a product ships under its upstream licence just as a declared dependency does; no manifest names it, so this line is its site. A licence offering SEVERAL options is a choice and is charged only when every one of them is banned. Replace it, or record an accepted exception.
Unlisted import 'esbuild' tests/Playground.test.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Hotspot: src/App.jsx src/App.jsx:147— src/App.jsx changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 777 in App.App at line 147. 12 of those changes were fix/bug commits, and the other 28 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/App.jsx`: 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: src/engine/Engine.js src/engine/Engine.js:4059— src/engine/Engine.js changed 59 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 99 in Engine._rebuildStackMaterialsAsync at line 4059. 22 of those changes were fix/bug commits, and the other 37 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/Engine.js`: 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: src/landing/Landing.jsx src/landing/Landing.jsx:120— src/landing/Landing.jsx changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 198 in Landing.Landing at line 120. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/landing/Landing.jsx`: 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:460— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 180 in NodeWorkspace.NodeWorkspace at line 460. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01: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: src/engine/terrain/TerrainMaterial.js src/engine/terrain/TerrainMaterial.js:499— src/engine/terrain/TerrainMaterial.js changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TerrainMaterial.buildFragmentSource at line 499. 12 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/terrain/TerrainMaterial.js`: 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: src/components/panels/index.jsx src/components/panels/index.jsx:105— src/components/panels/index.jsx changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in index.TerrainPanel at line 105. 4 of those changes were fix/bug commits, and the other 15 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/panels/index.jsx`: 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: src/components/ui/WaterPanel.jsx src/components/ui/WaterPanel.jsx:244— src/components/ui/WaterPanel.jsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 80 in WaterPanel.WaterPanelInner at line 244. 2 of those changes were fix/bug commits, and the other 5 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/WaterPanel.jsx`: 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: src/components/manual/ManualTerrainPanel.jsx src/components/manual/ManualTerrainPanel.jsx:188— src/components/manual/ManualTerrainPanel.jsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 92 in ManualTerrainPanel.ManualTerrainPanel at line 188. 1 of those changes was a fix/bug commit, and the other 4 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/manual/ManualTerrainPanel.jsx`: 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: src/engine/water/WaterSystem.js src/engine/water/WaterSystem.js:612— src/engine/water/WaterSystem.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in WaterSystem._swapMaterials at line 612. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/water/WaterSystem.js`: 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: src/engine/props/ProceduralPropsManager.js src/engine/props/ProceduralPropsManager.js:319— src/engine/props/ProceduralPropsManager.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in ProceduralPropsManager._updateFlat at line 319. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/props/ProceduralPropsManager.js`: 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: src/engine/EngineProxy.js src/engine/EngineProxy.js:472— src/engine/EngineProxy.js changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in EngineProxy.createEngineProxy at line 472. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/EngineProxy.js`: 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: src/components/ui/ImportMapsContent.jsx src/components/ui/ImportMapsContent.jsx:323— src/components/ui/ImportMapsContent.jsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ImportMapsContent.CustomAreaPicker at line 323. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/ImportMapsContent.jsx`: 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: src/project/ProjectLibrary.jsx src/project/ProjectLibrary.jsx:40— src/project/ProjectLibrary.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 88 in ProjectLibrary.ProjectLibrary at line 40. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/project/ProjectLibrary.jsx`: 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:498— REDACTED changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in SurfaceLibraryPanel.SurfaceLibraryPanel at line 498. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01: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: src/components/ui/RealWorldMapPicker.jsx src/components/ui/RealWorldMapPicker.jsx:70— src/components/ui/RealWorldMapPicker.jsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in RealWorldMapPicker.RealWorldMapPicker at line 70. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/RealWorldMapPicker.jsx`: 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: src/components/TopBar.jsx src/components/TopBar.jsx:44— src/components/TopBar.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in TopBar.TopBar at line 44. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/TopBar.jsx`: 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: src/engine/mini/MiniTerrainController.js src/engine/mini/MiniTerrainController.js:276— src/engine/mini/MiniTerrainController.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in MiniTerrainController.beforeRender at line 276. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/mini/MiniTerrainController.js`: 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: src/engine/render/PerformanceSettings.js src/engine/render/PerformanceSettings.js:265— src/engine/render/PerformanceSettings.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in PerformanceSettings.sanitizePerfSettings at line 265. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/render/PerformanceSettings.js`: 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:65— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in CommunityPage.CommunityPage at line 65. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01: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: src/engine/sky/CloudSlabLayer.js src/engine/sky/CloudSlabLayer.js:186— src/engine/sky/CloudSlabLayer.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CloudSlabLayer.applyParams at line 186. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/sky/CloudSlabLayer.js`: 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: src/manual/ManualTerrainModeManager.js src/manual/ManualTerrainModeManager.js:442— src/manual/ManualTerrainModeManager.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in ManualTerrainModeManager.setTexturePaintSetting at line 442. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/manual/ManualTerrainModeManager.js`: 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: src/engine/mini/MiniWaterMaterial.js src/engine/mini/MiniWaterMaterial.js:806— src/engine/mini/MiniWaterMaterial.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in MiniWaterMaterial.applyMiniWaterLook at line 806. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/mini/MiniWaterMaterial.js`: 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: src/components/perf/PerformanceOverlay.jsx src/components/perf/PerformanceOverlay.jsx:65— src/components/perf/PerformanceOverlay.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in PerformanceOverlay.PerformanceOverlay at line 65. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/perf/PerformanceOverlay.jsx`: 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: src/components/ui/PropsAssetLibrary.jsx src/components/ui/PropsAssetLibrary.jsx:238— src/components/ui/PropsAssetLibrary.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in PropsAssetLibrary.PropsAssetLibrary at line 238. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/PropsAssetLibrary.jsx`: 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: src/components/ui/CloudPanel.jsx src/components/ui/CloudPanel.jsx:102— src/components/ui/CloudPanel.jsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in CloudPanel.CloudPanel at line 102. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/CloudPanel.jsx`: 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.
FunctionTooLong: App.App src/App.jsx:147— FunctionTooLong — App runs 2374 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2274 over it, 23.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ManualTerrainPanel.ManualTerrainPanel src/components/manual/ManualTerrainPanel.jsx:188— FunctionTooLong — ManualTerrainPanel runs 655 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 555 over it, 6.55× 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: Landing.Landing src/landing/Landing.jsx:120— FunctionTooLong — Landing runs 604 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 504 over it, 6.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: WaterPanel.WaterPanelInner src/components/ui/WaterPanel.jsx:244— FunctionTooLong — WaterPanelInner runs 544 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 444 over it, 5.44× 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: NodeWorkspace.NodeWorkspace REDACTED:460— FunctionTooLong — NodeWorkspace runs 517 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 417 over it, 5.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: RealWorldMapPicker.RealWorldMapPicker src/components/ui/RealWorldMapPicker.jsx:70— FunctionTooLong — RealWorldMapPicker runs 373 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 273 over it, 3.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.
FunctionTooLong: GraphCompiler.nodeFunction src/engine/terrain/graph/GraphCompiler.js:187— FunctionTooLong — nodeFunction runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TopBar.TopBar src/components/TopBar.jsx:44— FunctionTooLong — TopBar runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: admin-routes.registerAdminRoutes REDACTED:45— FunctionTooLong — registerAdminRoutes runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× 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: GraphCompiler.cpuEvaluator src/engine/terrain/graph/GraphCompiler.js:796— FunctionTooLong — cpuEvaluator runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× 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: BlenderPluginPage.BlenderPluginPage REDACTED:85— FunctionTooLong — BlenderPluginPage runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.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: UnityPluginPage.UnityPluginPage REDACTED:114— FunctionTooLong — UnityPluginPage runs 293 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 193 over it, 2.93× 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: CloudPanel.CloudPanel src/components/ui/CloudPanel.jsx:102— FunctionTooLong — CloudPanel runs 291 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 191 over it, 2.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ProjectLibrary.ProjectLibrary src/project/ProjectLibrary.jsx:40— FunctionTooLong — ProjectLibrary runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.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.
FunctionTooLong: ColorPalettePanel.ColorPalettePanel src/components/ColorPalettePanel.jsx:148— FunctionTooLong — ColorPalettePanel runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.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: PropsAssetLibrary.PropsAssetLibrary src/components/ui/PropsAssetLibrary.jsx:238— FunctionTooLong — PropsAssetLibrary runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: project-routes.registerProjectRoutes REDACTED:55— FunctionTooLong — registerProjectRoutes runs 205 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 105 over it, 2.05× 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: InfiniteHUD.InfiniteHUD src/components/InfiniteHUD.jsx:38— FunctionTooLong — InfiniteHUD runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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: SideDrawer.SideDrawer src/components/ui/SideDrawer.jsx:14— FunctionTooLong — SideDrawer runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.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: CommunityPage.CommunityPage REDACTED:65— FunctionTooLong — CommunityPage runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: auth-routes.registerAuthRoutes REDACTED:103— FunctionTooLong — registerAuthRoutes runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: LeftToolbar.LeftToolbar src/components/ui/LeftToolbar.jsx:25— FunctionTooLong — LeftToolbar runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MinimapOverlay.MinimapOverlay src/components/MinimapOverlay.jsx:38— FunctionTooLong — MinimapOverlay runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: QualitySettingsContent.renderSettings src/components/panels/QualitySettingsContent.jsx:415— FunctionTooLong — renderSettings runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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: ImportMapsContent.CustomAreaPicker src/components/ui/ImportMapsContent.jsx:323— FunctionTooLong — CustomAreaPicker runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Sync-over-async blocking src/project/PortableProject.js:30— `unzipSync` in `decodePortableProject` 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 tools/perf-harness/experiments/bake-blend.mjs:9— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/bake-quality.mjs:21— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/bake-threshold.mjs:9— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/capture-views.mjs:7— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/classic-regression.mjs:16— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/cloud-edge-skip.mjs:8— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/cloud-loops.mjs:7— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/cloud-loops.mjs:8— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/depth-prepass.mjs:12— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/lod-density.mjs:9— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/lod-restore.mjs:13— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-circle.mjs:16— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-clouds.mjs:8— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-export.mjs:11— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-export.mjs:31— `unzipSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-export.mjs:35— `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-export.mjs:36— `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-export.mjs:50— `fs.writeFileSync` in `callback to urls.forEach` 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 tools/perf-harness/experiments/mini-first-frames.mjs:10— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-light-cost.mjs:11— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-live-edit.mjs:13— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-props-instant.mjs:14— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-terrain.mjs:17— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking tools/perf-harness/experiments/mini-water-modes.mjs:13— `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/assets.js:1— packages/procedural-terrains/assets.js:1 reaches into another package with a relative path (../../src/runtime/resources/TerrainResources.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/assets.js:2— packages/procedural-terrains/assets.js:2 reaches into another package with a relative path (../../src/runtime/resources/TerrainCompute.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/assets.js:3— packages/procedural-terrains/assets.js:3 reaches into another package with a relative path (../../src/runtime/resources/SurfaceAssets.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/assets.js:4— packages/procedural-terrains/assets.js:4 reaches into another package with a relative path (../../src/engine/terrain/surface/SurfaceDocument.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/assets.js:5— packages/procedural-terrains/assets.js:5 reaches into another package with a relative path (../../src/runtime/resources/TerrainSurfaceWorker.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/clouds.js:1— packages/procedural-terrains/clouds.js:1 reaches into another package with a relative path (../../REDACTED) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/clouds.js:2— packages/procedural-terrains/clouds.js:2 reaches into another package with a relative path (../../src/engine/sky/CloudSettings.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/documents.js:1— packages/procedural-terrains/documents.js:1 reaches into another package with a relative path (../../src/runtime/TerrainDocument.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/export.js:1— packages/procedural-terrains/export.js:1 reaches into another package with a relative path (../../src/runtime/export/TerrainExport.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/generation.js:1— packages/procedural-terrains/generation.js:1 reaches into another package with a relative path (../../src/engine/terrain/noise/NoiseStack.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/generation.js:2— packages/procedural-terrains/generation.js:2 reaches into another package with a relative path (../../src/engine/terrain/graph/GraphCompiler.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/generation.js:3— packages/procedural-terrains/generation.js:3 reaches into another package with a relative path (../../src/manual/ManualShapeCatalog.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/generation.js:4— packages/procedural-terrains/generation.js:4 reaches into another package with a relative path (../../src/engine/terrain/graph/GraphDocument.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/index.js:4— packages/procedural-terrains/index.js:4 reaches into another package with a relative path (../../src/runtime/FiniteTerrain.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/infinite.js:1— packages/procedural-terrains/infinite.js:1 reaches into another package with a relative path (../../src/runtime/worlds/InfiniteTerrain.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/mini.js:1— packages/procedural-terrains/mini.js:1 reaches into another package with a relative path (../../src/runtime/worlds/MiniTerrain.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/mini.js:2— packages/procedural-terrains/mini.js:2 reaches into another package with a relative path (../../src/engine/mini/MiniTerrainSettings.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/planet.js:1— packages/procedural-terrains/planet.js:1 reaches into another package with a relative path (../../src/runtime/worlds/PlanetTerrain.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/real-world.js:1— packages/procedural-terrains/real-world.js:1 reaches into another package with a relative path (../../src/runtime/providers/RealWorldTerrain.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/render.js:1— packages/procedural-terrains/render.js:1 reaches into another package with a relative path (../../src/runtime/effects/TerrainRenderPipeline.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/render.js:2— packages/procedural-terrains/render.js:2 reaches into another package with a relative path (../../src/runtime/effects/TerrainHeightCache.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/render.js:3— packages/procedural-terrains/render.js:3 reaches into another package with a relative path (../../src/runtime/effects/TerrainDetailCache.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/viewer.js:1— packages/procedural-terrains/viewer.js:1 reaches into another package with a relative path (../../src/runtime/viewer/TerrainViewer.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/water.js:1— packages/procedural-terrains/water.js:1 reaches into another package with a relative path (../../REDACTED) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/procedural-terrains/water.js:2— packages/procedural-terrains/water.js:2 reaches into another package with a relative path (../../src/engine/water/WaterSettings.js) — import the package by name instead.
+ 4 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×23
Focus outline removed in CSS without a :focus replacement src/styles.css:1127— `.realworld-map-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:1242— `.realworld-map-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:1668— `.visuals-search-wrap input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:1768— `.prop-search-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:2010— `.row input[type="number"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:2240— `.spline-name-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:3180— `.settings-search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:4954— `.node-template-picker select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5001— `.node-color-preset select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5290— `.node-palette-filter input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5329— `.node-search-input input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5358— `.node-inspector-search-wrap input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5379— `.node-inspector-field > input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:6073— `.manual-shape-layer-title select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:7933— `.manual-import-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:648— `.support-download-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:891— `.admin-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:895— `.admin-filters select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:1248— `.cloud-sync-bar select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:1276— `.community-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:1319— `.community-select-wrap select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:1373— `.lp-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/landing/landing.css:1665— `.lp-node-color-select select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
MethodTooLong: TerrainExportBuilder.build src/engine/terrain/TerrainExportBuilder.js:201— MethodTooLong — build runs 533 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 433 over it, 5.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.constructor src/engine/Engine.js:277— MethodTooLong — constructor runs 364 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 264 over it, 3.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._rebuildStackMaterialsAsync src/engine/Engine.js:4059— MethodTooLong — _rebuildStackMaterialsAsync runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._compileMaterialVariants src/engine/Engine.js:5832— MethodTooLong — _compileMaterialVariants runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.loadSeedJSON src/engine/Engine.js:11742— MethodTooLong — loadSeedJSON runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) 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: TerrainGenerationSceneBuilder.Build plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:35— MethodTooLong — Build runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.getPerfDiagnostics src/engine/Engine.js:13915— MethodTooLong — getPerfDiagnostics runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.restoreState src/engine/Engine.js:12049— MethodTooLong — restoreState runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._syncRealWorldNeighborTiles src/engine/Engine.js:2238— MethodTooLong — _syncRealWorldNeighborTiles runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.dispose src/engine/Engine.js:14100— MethodTooLong — dispose runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) 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: WaterSystem._swapMaterials src/engine/water/WaterSystem.js:612— MethodTooLong — _swapMaterials runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._warmDeferredWaterImpl src/engine/Engine.js:8044— MethodTooLong — _warmDeferredWaterImpl runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._tickStudio src/engine/Engine.js:13534— MethodTooLong — _tickStudio runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
MethodTooLong: TerrainProjectImporter.OnImportAsset plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainProjectImporter.cs:14— MethodTooLong — OnImportAsset runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._tickBody src/engine/Engine.js:13177— MethodTooLong — _tickBody runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PlanetExportBuilder.build src/engine/terrain/PlanetExportBuilder.js:138— MethodTooLong — build runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.newProject src/engine/Engine.js:2952— MethodTooLong — newProject runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: Engine._rebuildPlanetStackMaterialsAsync src/engine/Engine.js:4343— MethodTooLong — _rebuildPlanetStackMaterialsAsync runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) 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: Engine._compileShaderBenchmarkCandidate src/engine/Engine.js:6937— MethodTooLong — _compileShaderBenchmarkCandidate runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ManualTerrainField.stamp src/manual/ManualTerrainField.js:416— MethodTooLong — stamp runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine._loadRealWorldHeightmap src/engine/Engine.js:1991— MethodTooLong — _loadRealWorldHeightmap runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: Engine.setNoiseStack src/engine/Engine.js:3567— MethodTooLong — setNoiseStack runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
MethodTooLong: Engine.setTerrainGraph src/engine/Engine.js:3763— MethodTooLong — setTerrainGraph runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
FileTooLong: engine/Engine.js src/engine/Engine.js— FileTooLong — 10465 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), about 98% of them inside a single declaration: Engine (276-14259). The bar is 500 significant lines; this is 9965 over it, 20.93× 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/App.jsx src/App.jsx— FileTooLong — 2504 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: App (147-3064). The bar is 500 significant lines; this is 2004 over it, 5.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: terrain/TerrainMaterial.js src/engine/terrain/TerrainMaterial.js— FileTooLong — 1242 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 742 over it, 2.48× 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: graph/GraphCompiler.js src/engine/terrain/graph/GraphCompiler.js— FileTooLong — 1040 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 540 over it, 2.08× 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: manual/ManualTerrainModeManager.js src/manual/ManualTerrainModeManager.js— FileTooLong — 991 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: ManualTerrainModeManager (93-1217). The bar is 500 significant lines; this is 491 over it, 1.98× 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: panels/index.jsx src/components/panels/index.jsx— FileTooLong — 954 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 454 over it, 1.91× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 929 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 429 over it, 1.86× 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: water/WaterSystem.js src/engine/water/WaterSystem.js— FileTooLong — 863 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: WaterSystem (35-1218). The bar is 500 significant lines; this is 363 over it, 1.73× 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: manual/ManualTerrainPanel.jsx src/components/manual/ManualTerrainPanel.jsx— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: ManualTerrainPanel (188-889). The bar is 500 significant lines; this is 317 over it, 1.63× 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: props/ProceduralPropsManager.js src/engine/props/ProceduralPropsManager.js— FileTooLong — 772 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), about 87% of them inside a single declaration: ProceduralPropsManager (132-980). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/WaterPanel.jsx src/components/ui/WaterPanel.jsx— FileTooLong — 727 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: WaterPanelInner (244-870). The bar is 500 significant lines; this is 227 over it, 1.45× 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: landing/Landing.jsx src/landing/Landing.jsx— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: Landing (120-812). The bar is 500 significant lines; this is 206 over it, 1.41× 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: mini/MiniWaterMaterial.js src/engine/mini/MiniWaterMaterial.js— FileTooLong — 694 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 194 over it, 1.39× 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: terrain/TerrainExportBuilder.js src/engine/terrain/TerrainExportBuilder.js— FileTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: TerrainExportBuilder (200-938). 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: procedural_terrains/generation.py plugins/blender/procedural_terrains/generation.py— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 180 over it, 1.36× 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: terrain/TerrainBoard.js src/engine/terrain/TerrainBoard.js— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: TerrainBoard (21-887). The bar is 500 significant lines; this is 106 over it, 1.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× 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: Editor/TerrainGenerator.cs plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: terrain/PlanetWorld.js src/engine/terrain/PlanetWorld.js— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: PlanetWorld (33-732). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
R4 · Test Coverage· No test reaches this file · ×13
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 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 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 src/project/CloudProjectsPanel.jsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/components/LeftPanel.jsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file 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 vite-plugins/surfaceMaterialsApi.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 api/scripts/migrate.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 api/src/activity.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 vite-plugins/playgroundRuntime.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 api/src/db.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 electron/preload.cjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/components/NoisePresetPanel.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.
ClassTooLong: App src/App.jsx:1— ClassTooLong — 2374 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 1974 over it, 5.94× 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: WaterSystem src/engine/water/WaterSystem.js:35— ClassTooLong — 835 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 400 significant lines; this is 435 over it, 2.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ManualTerrainPanel src/components/manual/ManualTerrainPanel.jsx:1— ClassTooLong — 655 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 255 over it, 1.64× 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: Landing src/landing/Landing.jsx:1— ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 204 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TerrainBoard src/engine/terrain/TerrainBoard.js:21— ClassTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 200 over it, 1.50× 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: NodeWorkspace REDACTED:1— ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 117 over it, 1.29× 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: PlanetWorld src/engine/terrain/PlanetWorld.js:33— ClassTooLong — 494 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 94 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.
ClassTooLong: TerrainGenerator plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs— ClassTooLong — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 86 over it, 1.22× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: ProceduralTerrainsWindow plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/ProceduralTerrainsWindow.cs— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low contrast colour pair in CSS (3.7:1) src/styles.css:1651— `.visuals-search-wrap` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:1766— `.prop-search-field` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:2238— `.spline-name-field > div` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:5276— `.node-palette-filter` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:5356— `.node-inspector-search-wrap` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:5370— `.node-inspector-section-toggle small` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) src/styles.css:5821— `.manual-dock-section-title span` sets color: #737373 on background-color: #1a1a1a — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
TooManyMethods: Engine src/engine/Engine.js:276— TooManyMethods — 496 methods. The bar is 30 methods; this is 466 over it, 16.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WaterSystem src/engine/water/WaterSystem.js:35— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ManualTerrainModeManager src/manual/ManualTerrainModeManager.js:93— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TerrainBoard src/engine/terrain/TerrainBoard.js:21— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PlanetWorld src/engine/terrain/PlanetWorld.js:33— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MiniTerrainController src/engine/mini/MiniTerrainController.js:43— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SplineManager src/creator/splines/SplineManager.js:17— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AC1 · Text alternatives· <canvas> without a text alternative · ×6
<canvas> without a text alternative src/App.jsx:2791— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative src/components/RightPanels.jsx:44— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative src/components/RightPanels.jsx:288— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative src/components/RightPanels.jsx:289— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative src/components/ui/SurfaceMaterialPreviewSphere.jsx:120— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative src/runtime/export/ExportCanvas.js:4— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×6
Modal dialog does not manage focus src/components/support/SupportDownloadModal.jsx:39— This <section role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/ui/ManualTerrainImportDialog.jsx:62— This <form role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/ui/PopupProvider.jsx:60— This <form role="alertdialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/ui/RealWorldMapPicker.jsx:356— This <section role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/ui/Toast.jsx:75— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/ui/UiSettingsPanel.jsx:27— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Repeated repair: src/engine/terrain/TerrainHeightBaker.js src/engine/terrain/TerrainHeightBaker.js:364— src/engine/terrain/TerrainHeightBaker.js changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is TerrainHeightBaker.step at line 364), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: preserve terrain bake texel coordinates on HiDPI screens”; “Fix terrain and water render stability”; “fixes”; “Fix terrain water and loading stability”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/terrain/TerrainHeightBaker.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/engine/sky/realistic/RealisticCloudLayers.js src/engine/sky/realistic/RealisticCloudLayers.js:186— src/engine/sky/realistic/RealisticCloudLayers.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is RealisticCloudSlabLayer.applyParams at line 186), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix terrain”; “Fix portable imports and cloud rendering for 2.0.1”; “clouds fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/sky/realistic/RealisticCloudLayers.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/engine/sky/PlanetCloudLayer.js src/engine/sky/PlanetCloudLayer.js:128— src/engine/sky/PlanetCloudLayer.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is PlanetCloudLayer.applyParams at line 128), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix portable imports and cloud rendering for 2.0.1”; “clouds fixes”; “fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/sky/PlanetCloudLayer.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/engine/terrain/WaterMaterial.js src/engine/terrain/WaterMaterial.js:34— src/engine/terrain/WaterMaterial.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is WaterMaterial.buildFragmentSource at line 34), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “better perfs and bug fixes”; “Fix terrain and water render stability”; “fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/engine/terrain/WaterMaterial.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/components/ui/LoadingOverlay.jsx src/components/ui/LoadingOverlay.jsx:29— src/components/ui/LoadingOverlay.jsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is LoadingOverlay.LoadingOverlay at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “general fixes of the terrain exporter”; “small fixes”; “general fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 11:45:42 +01:00' --until='2026-10-27 11:45:42 +01:00' --full-history --no-merges -- src/components/ui/LoadingOverlay.jsx`: 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.
Change coupling: TerrainHeightSampler.js ↔ terrainGLSL.js src/engine/terrain/TerrainHeightSampler.js:1— `src/engine/terrain/TerrainHeightSampler.js` and `src/engine/terrain/terrainGLSL.js` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `27b68af9` fixed real terrains issues, missing resolutions fixes and improved re…; `24307794` new explode tool; `38e4e7c4` first start of the nodes mode — run `git show` on any of them.
Change coupling: index.jsx ↔ settingsSearch.js src/components/panels/index.jsx:1— `src/components/panels/index.jsx` and `src/components/panels/settingsSearch.js` change together 61% of the time (19 of the 31 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `6b4954c5` Add non-destructive reference images for Tile authoring; `27b68af9` fixed real terrains issues, missing resolutions fixes and improved re…; `f520399b` Add imported 3D props and streamline panel controls — run `git show` on any of them.
Change coupling: InfiniteHUD.jsx ↔ StatusBar.jsx src/components/InfiniteHUD.jsx:1— `src/components/InfiniteHUD.jsx` and `src/components/StatusBar.jsx` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f5991806` phase 1; `5ca43d58` plane mode prototype; `77379c25` spherical mode — run `git show` on any of them.
Change coupling: PerfSettings.jsx ↔ settingsSearch.js src/components/panels/PerfSettings.jsx:1— `src/components/panels/PerfSettings.jsx` and `src/components/panels/settingsSearch.js` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `36ecfd91` visual filters; `65d57312` terrain surface settings; `c8948c55` Replace chunk group merges with quadtree folding — run `git show` on any of them.
Change coupling: PerformanceSettings.js ↔ TerrainBoard.js src/engine/render/PerformanceSettings.js:1— `src/engine/render/PerformanceSettings.js` and `src/engine/terrain/TerrainBoard.js` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `f5991806` phase 1; `c8948c55` Replace chunk group merges with quadtree folding; `e9190483` chunk merging — run `git show` on any of them.
Low contrast colour pair in CSS (3.6:1) src/styles.css:3231— `.settings-tab.active` sets color: #2563eb on background-color: #141414 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) src/styles.css:4770— `.minimap-fab` sets color: #2563eb on background-color: #141414 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) src/landing/landing.css:591— `.blender-option-preview svg` sets color: white on background-color: #d36b29 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) src/styles.css:3549— `.settings-search-item-value` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) src/styles.css:4785— `.minimap-fab:hover` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) src/styles.css:5103— `.node-graph-dock .react-flow__controls-button:hover` sets color: #2563eb on background-color: #1a1a1a — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Change-coupling hub: Engine.js → TerrainBoard.js, terrainGLSL.js, RealisticWaterMaterial.js src/engine/Engine.js— `src/engine/Engine.js` changes together with 3 other files — `src/engine/terrain/TerrainBoard.js`, `src/engine/terrain/terrainGLSL.js`, `src/engine/water/RealisticWaterMaterial.js` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: App.jsx → PerfSettings.jsx, index.jsx, ImportMapsContent.jsx, EditorControls.js, Engine.js, PerformanceSettings.js, TerrainBoard.js, TerrainExporter.js, TerrainHeightSampler.js, GraphCompiler.js, ManualTerrainModeManager.js src/App.jsx— `src/App.jsx` changes together with 11 other files — `src/components/panels/PerfSettings.jsx`, `src/components/panels/index.jsx`, `src/components/ui/ImportMapsContent.jsx`, `src/engine/EditorControls.js`, `src/engine/Engine.js`, `src/engine/render/PerformanceSettings.js`, `src/engine/terrain/TerrainBoard.js`, `src/engine/terrain/TerrainExporter.js`, `src/engine/terrain/TerrainHeightSampler.js`, `src/engine/terrain/graph/GraphCompiler.js`, `src/manual/ManualTerrainModeManager.js` — none of which declares a dependency on it: one file is the hub of 11 separate couplings, not 11 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 11.
Change-coupling hub: TerrainMaterial.js → panelResets.js, presets.js, PlanetMaterial.js, TerrainExporter.js, TerrainHeightSampler.js, WaterMaterial.js, RealisticWaterMaterial.js src/engine/terrain/TerrainMaterial.js— `src/engine/terrain/TerrainMaterial.js` changes together with 7 other files — `src/engine/panelResets.js`, `src/engine/presets.js`, `src/engine/terrain/PlanetMaterial.js`, `src/engine/terrain/TerrainExporter.js`, `src/engine/terrain/TerrainHeightSampler.js`, `src/engine/terrain/WaterMaterial.js`, `src/engine/water/RealisticWaterMaterial.js` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Duplicated block (24 lines × 2 locations) src/engine/EditorControls.js:280— src/engine/EditorControls.js:280 · src/engine/PlanetOrbitControls.js:87 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) src/engine/EditorControls.js:317— src/engine/EditorControls.js:317 · src/engine/PlanetOrbitControls.js:120 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) REDACTED:134— REDACTED:134 · REDACTED:154 — 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 (21 lines × 2 locations) src/engine/sky/CloudSlabLayer.js:304— src/engine/sky/CloudSlabLayer.js:304 · src/engine/sky/PlanetCloudLayer.js:214 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) REDACTED:100— REDACTED:100 · REDACTED:129 — 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 (21 lines × 2 locations) tools/perf-harness/experiments/mini-circle.mjs:57— tools/perf-harness/experiments/mini-circle.mjs:57 · tools/perf-harness/experiments/mini-terrain.mjs:53 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~52 LoC) tools/perf-harness/experiments/classic-regression.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~52 LoC) tools/perf-harness/experiments/compile-attribution3.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~52 LoC) tools/perf-harness/experiments/mini-water-modes.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~49 LoC) tools/perf-harness/experiments/cloud-edge-skip.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~49 LoC) tools/perf-harness/experiments/morph-sensitivity.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~49 LoC) tools/perf-harness/experiments/terrain-detail.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Low contrast colour pair in CSS (4.1:1) src/styles.css:3919— `#fps-controls-hint` sets color: #737373 on background-color: #0d0d0d — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) src/styles.css:5061— `.node-graph-resizer` sets color: #737373 on background-color: #0d0d0d — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
update (cognitive 17) src/engine/props/ProceduralPropsManager.js:218— update has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 6, other 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cognitive 17) src/engine/sky/CloudSlabLayer.js:542— update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411-420 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainZipImportService.cs:212-224 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:649— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:649-659 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:672-681 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×2
Duplicated block with local edits (40 matched lines × 2 locations) src/engine/sky/realistic/RealisticCloudResources.js:241— src/engine/sky/realistic/RealisticCloudResources.js:241 · src/engine/sky/realistic/RealisticCloudResources.js:309 — the two spans are one implementation copied and then locally edited — 294 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (40 matched lines × 2 locations) src/engine/terrain/InfiniteWorld.js:246— src/engine/terrain/InfiniteWorld.js:246 · src/engine/terrain/PlanetWorld.js:326 — the two spans are one implementation copied and then locally edited — 352 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 (37 matched lines × 2 locations) · ×2
Duplicated block with local edits (37 matched lines × 2 locations) src/components/ui/WaterPanel.jsx:676— src/components/ui/WaterPanel.jsx:676 · src/components/ui/WaterPanel.jsx:770 — the two spans are one implementation copied and then locally edited — 237 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (37 matched lines × 2 locations) src/engine/player/PlaneController.js:66— src/engine/player/PlaneController.js:66 · src/engine/player/PlanetController.js:66 — the two spans are one implementation copied and then locally edited — 357 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (33 lines × 2 locations) src/manual/ManualPropPaintField.js:1— src/manual/ManualPropPaintField.js:1 · src/manual/ManualSurfacePaintField.js:4 — 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 (33 lines × 2 locations) src/manual/ManualTerrainModeManager.js:360— src/manual/ManualTerrainModeManager.js:360 · src/manual/ManualTerrainModeManager.js:409 — 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 (27 lines × 2 locations) src/engine/sky/PlanetCloudChunks.js:227— src/engine/sky/PlanetCloudChunks.js:227 · src/engine/sky/PlanetCloudLayer.js:119 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (27 lines × 2 locations) tools/perf-harness/experiments/compile-attribution2.mjs:2— tools/perf-harness/experiments/compile-attribution2.mjs:2 · tools/perf-harness/experiments/compile-attribution3.mjs:3 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) src/engine/terrain/PlanetHeightSampler.js:18— src/engine/terrain/PlanetHeightSampler.js:18 · src/engine/terrain/TerrainHeightSampler.js:21 — 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 (25 lines × 2 locations) REDACTED:307— REDACTED:307 · REDACTED:338 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) src/engine/Engine.js:8475— src/engine/Engine.js:8475 · src/engine/Engine.js:8507 — 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 (19 lines × 2 locations) src/engine/sky/CloudSlabLayer.js:82— src/engine/sky/CloudSlabLayer.js:82 · src/engine/sky/PlanetCloudLayer.js:75 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~154 LoC) src/components/LeftPanel.jsx— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~154 LoC) tools/gen-placeholder-textures.cjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~99 LoC) tools/perf-harness/experiments/node-project.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~99 LoC) tools/perf-harness/experiments/zoom-lag.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~81 LoC) tools/perf-harness/experiments/depth-prepass.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~81 LoC) tools/perf-harness/experiments/mini-live-edit.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~51 LoC) tools/perf-harness/experiments/mini-export.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~51 LoC) tools/perf-harness/experiments/water-loop.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~47 LoC) tools/detail-page-browser-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~47 LoC) tools/perf-harness/experiments/dynamic-loops.mjs— no import path from any entry point (88 application, 18 tooling, 138 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
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (3.9:1) src/landing/landing.css:889— `.admin-search` sets color: #60708c on background-color: #080d16 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) src/landing/landing.css:948— `.admin-change-chips span` sets color: #6f7889 on background-color: #090c12 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
App.App (cyclomatic 777) src/App.jsx:147— App.App has cyclomatic complexity 777 (threshold 15). Of this number, 109 points are the body's own statements and 668 belong to 148 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
build (cyclomatic 195) src/engine/terrain/TerrainExportBuilder.js:201— build has cyclomatic complexity 195 (threshold 15). Of this number, 159 points are the body's own statements and 36 belong to 32 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.
NodeWorkspace.NodeWorkspace (cyclomatic 180) REDACTED:460— NodeWorkspace.NodeWorkspace has cyclomatic complexity 180 (threshold 15). Of this number, 44 points are the body's own statements and 136 belong to 47 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_rebuildStackMaterialsAsync (cyclomatic 104) src/engine/Engine.js:4059— _rebuildStackMaterialsAsync has cyclomatic complexity 104 (threshold 15). Of this number, 100 points are the body's own statements and 4 belong to 5 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.
validateRuntimeTerrainDocument (cyclomatic 94) src/export/runtime/RuntimeTerrainValidator.js:18— validateRuntimeTerrainDocument has cyclomatic complexity 94 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ManualTerrainPanel.ManualTerrainPanel (cyclomatic 92) src/components/manual/ManualTerrainPanel.jsx:188— ManualTerrainPanel.ManualTerrainPanel has cyclomatic complexity 92 (threshold 15). Of this number, 46 points are the body's own statements and 46 belong to 24 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.
ProjectLibrary.ProjectLibrary (cyclomatic 88) src/project/ProjectLibrary.jsx:40— ProjectLibrary.ProjectLibrary has cyclomatic complexity 88 (threshold 15). Most of this is not in the body itself: 15 of the 88 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 296, 186, 120, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WaterPanel.WaterPanelInner (cyclomatic 80) src/components/ui/WaterPanel.jsx:244— WaterPanel.WaterPanelInner has cyclomatic complexity 80 (threshold 15). Of this number, 66 points are the body's own statements and 14 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_tickStudio (cyclomatic 78) src/engine/Engine.js:13534— _tickStudio has cyclomatic complexity 78 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TerrainGenerator.Validate (cyclomatic 74) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:42— TerrainGenerator.Validate has cyclomatic complexity 74 (threshold 15). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Landing.Landing (cyclomatic 74) src/landing/Landing.jsx:120— Landing.Landing has cyclomatic complexity 74 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Landing.Landing::renderProjectCard) 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.
loadSeedJSON (cyclomatic 73) src/engine/Engine.js:11742— loadSeedJSON has cyclomatic complexity 73 (threshold 15). Of this number, 68 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
registerAdminRoutes (cyclomatic 72) REDACTED:45— registerAdminRoutes has cyclomatic complexity 72 (threshold 15). Most of this is not in the body itself: 1 of the 72 points is its own statement and the rest belongs to 25 function literals inside it that branch (lines 153, 214, 48, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
getPerfDiagnostics (cyclomatic 66) src/engine/Engine.js:13915— getPerfDiagnostics 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.
compileSurfaceGraph (cyclomatic 66) src/engine/terrain/surface/SurfaceGraph.js:23— compileSurfaceGraph has cyclomatic complexity 66 (threshold 15). Of this number, 54 points are the body's own statements and 12 belong to 11 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.
_warmDeferredWaterImpl (cyclomatic 62) src/engine/Engine.js:8044— _warmDeferredWaterImpl has cyclomatic complexity 62 (threshold 15). Of this number, 48 points are the body's own statements and 14 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RuntimeTerrainDocumentValidator.Validate (cyclomatic 61) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:164— RuntimeTerrainDocumentValidator.Validate has cyclomatic complexity 61 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_syncRealWorldNeighborTiles (cyclomatic 60) src/engine/Engine.js:2238— _syncRealWorldNeighborTiles has cyclomatic complexity 60 (threshold 15). Of this number, 24 points are the body's own statements and 36 belong to 20 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.
restoreState (cyclomatic 58) src/engine/Engine.js:12049— restoreState has cyclomatic complexity 58 (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.
TopBar.TopBar (cyclomatic 57) src/components/TopBar.jsx:44— TopBar.TopBar has cyclomatic complexity 57 (threshold 15). Of this number, 39 points are the body's own statements and 18 belong to 13 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_tickBody (cyclomatic 57) src/engine/Engine.js:13177— _tickBody has cyclomatic complexity 57 (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.
Engine._compileMaterialVariants (cyclomatic 54) src/engine/Engine.js:5832— Engine._compileMaterialVariants has cyclomatic complexity 54 (threshold 15). Of this number, 48 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CommunityPage.CommunityPage (cyclomatic 54) REDACTED:65— CommunityPage.CommunityPage has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 13 of the 54 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 241, a function literal at line 85, a function literal at line 112, …). 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.
TerrainGenerationSceneBuilder.Build (cyclomatic 53) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:35— TerrainGenerationSceneBuilder.Build 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.
_compileShaderBenchmarkCandidate (cyclomatic 53) src/engine/Engine.js:6937— _compileShaderBenchmarkCandidate has cyclomatic complexity 53 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dispose (cyclomatic 52) src/engine/Engine.js:14100— dispose has cyclomatic complexity 52 (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.
applyMiniWaterLook (cyclomatic 52) src/engine/mini/MiniWaterMaterial.js:806— applyMiniWaterLook 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.
ProceduralPropsManager._updateFlat (cyclomatic 51) src/engine/props/ProceduralPropsManager.js:319— ProceduralPropsManager._updateFlat has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrateGraphDocument (cyclomatic 51) src/engine/terrain/graph/GraphDocument.js:65— migrateGraphDocument has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 9 of the 51 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 91, 71, 115, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
sanitizePerfSettings (cyclomatic 51) src/engine/render/PerformanceSettings.js:265— sanitizePerfSettings has cyclomatic complexity 51 (threshold 15). Of this number, 49 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
registerProjectRoutes (cyclomatic 51) REDACTED:55— registerProjectRoutes has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 125, 223, 200, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
withEnergySaving.withEnergySaving (cyclomatic 50) src/engine/render/withEnergySaving.js:8— withEnergySaving.withEnergySaving has cyclomatic complexity 50 (threshold 15). Of this number, 39 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PropsAssetLibrary.PropsAssetLibrary (cyclomatic 48) src/components/ui/PropsAssetLibrary.jsx:238— PropsAssetLibrary.PropsAssetLibrary has cyclomatic complexity 48 (threshold 15). Of this number, 20 points are the body's own statements and 28 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_swapMaterials (cyclomatic 48) src/engine/water/WaterSystem.js:612— _swapMaterials has cyclomatic complexity 48 (threshold 15). Of this number, 18 points are the body's own statements and 30 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RealWorldMapPicker.RealWorldMapPicker (cyclomatic 47) src/components/ui/RealWorldMapPicker.jsx:70— RealWorldMapPicker.RealWorldMapPicker has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 13 of the 47 points are its own statements and the rest belongs to 11 function items inside it that branch (searchPlaces, commitSelectionCenter, changeCoordinateFormat, …). 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.
_setDebugFreeCam (cyclomatic 47) src/engine/Engine.js:8633— _setDebugFreeCam has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
applyRealisticWaterUniforms (cyclomatic 47) src/engine/water/RealisticWaterMaterial.js:1210— applyRealisticWaterUniforms has cyclomatic complexity 47 (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.
applyParams (cyclomatic 46) src/engine/sky/CloudSlabLayer.js:186— applyParams has cyclomatic complexity 46 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SideDrawer.SideDrawer (cyclomatic 45) src/components/ui/SideDrawer.jsx:14— SideDrawer.SideDrawer has cyclomatic complexity 45 (threshold 15). Of this number, 20 points are the body's own statements and 25 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MarkersPanel.MarkersPanel (cyclomatic 43) src/components/panels/MarkersPanel.jsx:8— MarkersPanel.MarkersPanel has cyclomatic complexity 43 (threshold 15). Of this number, 21 points are the body's own statements and 22 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodeWorkspace.NodeInspector (cyclomatic 43) REDACTED:318— NodeWorkspace.NodeInspector has cyclomatic complexity 43 (threshold 15). Of this number, 35 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_sceneRevisionKey (cyclomatic 42) src/engine/Engine.js:5465— _sceneRevisionKey has cyclomatic complexity 42 (threshold 15). Of this number, 39 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RendererCapabilities.detectRendererCapabilities (cyclomatic 41) src/engine/render/RendererCapabilities.js:37— RendererCapabilities.detectRendererCapabilities has cyclomatic complexity 41 (threshold 15). Of this number, 32 points are the body's own statements and 9 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Engine.setParam (cyclomatic 41) src/engine/Engine.js:2776— Engine.setParam has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generation_builder.build_generated_terrain (cyclomatic 41) plugins/blender/procedural_terrains/generation_builder.py:154— generation_builder.build_generated_terrain has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PlanetCloudChunks.update (cyclomatic 40) src/engine/sky/PlanetCloudChunks.js:351— PlanetCloudChunks.update 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.
_warmupPlanetShaders (cyclomatic 40) src/engine/Engine.js:10838— _warmupPlanetShaders has cyclomatic complexity 40 (threshold 15). Of this number, 38 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
createTerrainCodeDocument (cyclomatic 40) src/export/TerrainCodeExporter.js:17— createTerrainCodeDocument has cyclomatic complexity 40 (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.
ExportValidator.validateExport (cyclomatic 39) src/export/ExportValidator.js:7— ExportValidator.validateExport has cyclomatic complexity 39 (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.
_completeBootIfQualityReady (cyclomatic 39) src/engine/Engine.js:7359— _completeBootIfQualityReady has cyclomatic complexity 39 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.TerrainPanel (cyclomatic 38) src/components/panels/index.jsx:105— index.TerrainPanel has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Playground.Playground (cyclomatic 38) src/docs/playground/Playground.jsx:24— Playground.Playground has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 56, a function literal at line 45, a function literal at line 72, …). 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.
_setWorldModeImmediate (cyclomatic 38) src/engine/Engine.js:9681— _setWorldModeImmediate has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
registerAuthRoutes (cyclomatic 38) REDACTED:103— registerAuthRoutes has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 153, 106, 309, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Engine._rebuildPlanetStackMaterialsAsync (cyclomatic 37) src/engine/Engine.js:4343— Engine._rebuildPlanetStackMaterialsAsync has cyclomatic complexity 37 (threshold 15). Of this number, 27 points are the body's own statements and 10 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
newProject (cyclomatic 37) src/engine/Engine.js:2952— newProject has cyclomatic complexity 37 (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.
_ensureTerrainShaderVariantAsync (cyclomatic 37) src/engine/Engine.js:11251— _ensureTerrainShaderVariantAsync has cyclomatic complexity 37 (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.
applyParams (cyclomatic 37) src/engine/sky/PlanetCloudLayer.js:128— applyParams has cyclomatic complexity 37 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ProgramHealthGate.inspectProgram (cyclomatic 36) src/engine/render/ProgramHealthGate.js:47— ProgramHealthGate.inspectProgram has cyclomatic complexity 36 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
erosionSim.erode (cyclomatic 36) src/engine/terrain/erosion/erosionSim.js:85— erosionSim.erode has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
constructor (cyclomatic 36) src/engine/Engine.js:277— constructor has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 14 function items inside it that branch (_onContextLost, _onContextRestored, _onContextRestored::(anonymous)::isCurrent, …). 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.
setTerrainGraph (cyclomatic 36) src/engine/Engine.js:3763— setTerrainGraph has cyclomatic complexity 36 (threshold 15). Of this number, 29 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
normalizeProject (cyclomatic 36) src/project/ProjectStore.js:100— normalizeProject has cyclomatic complexity 36 (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.
LeftToolbar.LeftToolbar (cyclomatic 35) src/components/ui/LeftToolbar.jsx:25— LeftToolbar.LeftToolbar has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 10 of the 35 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 190, startDrag, a function literal at line 85, …). 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.
SurfaceLibraryPanel.SurfaceLibraryPanel (cyclomatic 35) REDACTED:498— SurfaceLibraryPanel.SurfaceLibraryPanel has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 528, 581, 562, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
export3DTerrain (cyclomatic 35) src/engine/Engine.js:12734— export3DTerrain has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_stepFlatSector (cyclomatic 35) src/engine/props/ProceduralPropsManager.js:480— _stepFlatSector 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.
applyParams (cyclomatic 35) src/engine/sky/PlanetCloudChunks.js:229— applyParams has cyclomatic complexity 35 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExportDiagnostics.estimateExport (cyclomatic 34) src/export/ExportDiagnostics.js:14— ExportDiagnostics.estimateExport has cyclomatic complexity 34 (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.
PlanetController.update (cyclomatic 34) src/engine/player/PlanetController.js:188— PlanetController.update has cyclomatic complexity 34 (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.
MinimapOverlay.MinimapOverlay (cyclomatic 34) src/components/MinimapOverlay.jsx:38— MinimapOverlay.MinimapOverlay has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 14 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 105, updateHover, a function literal at line 77, …). 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.
CloudProjectsPanel.CloudProjectsPanel (cyclomatic 34) src/project/CloudProjectsPanel.jsx:26— CloudProjectsPanel.CloudProjectsPanel has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (sync, rename, a function literal at line 35, …). 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.
normalizeTerrainSource (cyclomatic 34) src/runtime/TerrainSources.js:9— normalizeTerrainSource has cyclomatic complexity 34 (threshold 15). Of this number, 31 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
runner.iframeBootstrap (cyclomatic 33) src/docs/playground/runner.js:15— runner.iframeBootstrap has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (report, start, describe, …). 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.
runtime_document.validate_document (cyclomatic 33) plugins/blender/procedural_terrains/runtime_document.py:53— runtime_document.validate_document has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GraphCompiler.packUniforms (cyclomatic 32) src/engine/terrain/graph/GraphCompiler.js:681— GraphCompiler.packUniforms has cyclomatic complexity 32 (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.
PlayerController.update (cyclomatic 32) src/engine/player/PlayerController.js:123— PlayerController.update 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.
Engine._installSurfaceAtlas (cyclomatic 32) src/engine/Engine.js:5068— Engine._installSurfaceAtlas has cyclomatic complexity 32 (threshold 15). Of this number, 17 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_completeBootIfInteractiveReady (cyclomatic 32) src/engine/Engine.js:7310— _completeBootIfInteractiveReady has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ManualTerrainImportDialog.ManualTerrainImportDialog (cyclomatic 31) src/components/ui/ManualTerrainImportDialog.jsx:10— ManualTerrainImportDialog.ManualTerrainImportDialog has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 113, 32, 43, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_warmUnderwaterShaders (cyclomatic 31) src/engine/Engine.js:8281— _warmUnderwaterShaders has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 8296, 8328, 8395, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GraphDocument.validateGraph (cyclomatic 30) src/engine/terrain/graph/GraphDocument.js:272— GraphDocument.validateGraph has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SplineSerializer.migrateSplines (cyclomatic 30) src/creator/splines/SplineSerializer.js:7— SplineSerializer.migrateSplines has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 9, 13). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ImportMapsContent.CustomAreaPicker (cyclomatic 30) src/components/ui/ImportMapsContent.jsx:323— ImportMapsContent.CustomAreaPicker has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (load, a function literal at line 342, commitCoordText, …). 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.
ProfilePage.ProfilePage (cyclomatic 30) src/auth/ProfilePage.jsx:11— ProfilePage.ProfilePage has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (savePassword, chooseAvatar, passwordField, …). 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.
AdminDashboard.UsersPanel (cyclomatic 30) src/admin/AdminDashboard.jsx:186— AdminDashboard.UsersPanel has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (update, revoke, a function literal at line 286, …). 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.
DocsPage.DocsPage (cyclomatic 30) src/docs/DocsPage.jsx:160— DocsPage.DocsPage has cyclomatic complexity 30 (threshold 15). Of this number, 16 points are the body's own statements and 14 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
setNoiseStack (cyclomatic 30) src/engine/Engine.js:3567— setNoiseStack has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_warmupInfiniteShaders (cyclomatic 30) src/engine/Engine.js:9955— _warmupInfiniteShaders has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
beforeRender (cyclomatic 30) src/engine/mini/MiniTerrainController.js:276— beforeRender has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stamp (cyclomatic 30) src/paint/PaintLayerManager.js:263— stamp has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.ExportPanel (cyclomatic 29) src/components/panels/index.jsx:937— index.ExportPanel has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_compileMaterialDescriptor (cyclomatic 29) src/engine/Engine.js:5775— _compileMaterialDescriptor has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cyclomatic 29) src/engine/terrain/PlanetWorld.js:408— update 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.
TerrainMaterial.buildFragmentSource (cyclomatic 28) src/engine/terrain/TerrainMaterial.js:499— TerrainMaterial.buildFragmentSource has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CloudPanel.CloudPanel (cyclomatic 28) src/components/ui/CloudPanel.jsx:102— CloudPanel.CloudPanel has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ensureTerrainHeightTex (cyclomatic 28) src/engine/Engine.js:10389— _ensureTerrainHeightTex has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_applyCloudSettings (cyclomatic 28) src/engine/Engine.js:10624— _applyCloudSettings has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_targetTerrainVariant (cyclomatic 28) src/engine/Engine.js:11222— _targetTerrainVariant has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_tickPlanet (cyclomatic 28) src/engine/Engine.js:13812— _tickPlanet has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TerrainGenerator.Generate (cyclomatic 27) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:102— TerrainGenerator.Generate has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ManualTerrainModeManager.setSculptSetting (cyclomatic 27) src/manual/ManualTerrainModeManager.js:393— ManualTerrainModeManager.setSculptSetting has cyclomatic complexity 27 (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.
Engine.transitionMode (cyclomatic 27) src/engine/Engine.js:9591— Engine.transitionMode 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.
_applySurfaceSettings (cyclomatic 27) src/engine/Engine.js:4980— _applySurfaceSettings has cyclomatic complexity 27 (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.
_maybeFpsDowngrade (cyclomatic 27) src/engine/water/WaterSystem.js:1038— _maybeFpsDowngrade 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.
setCircularBoundary (cyclomatic 27) src/engine/terrain/TerrainBoard.js:450— setCircularBoundary has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cyclomatic 27) src/engine/render/VisualPostProcess.js:469— update has cyclomatic complexity 27 (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.
capture (cyclomatic 27) src/engine/water/WaterPlanarReflectionPass.js:199— capture has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TerrainGenerationPresets.ApplyTerrainPreset (cyclomatic 26) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationPresets.cs:8— TerrainGenerationPresets.ApplyTerrainPreset 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.
DetailPageCache.update (cyclomatic 26) src/engine/terrain/detail/DetailPageCache.js:88— DetailPageCache.update 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.
FiniteTerrain.configure (cyclomatic 26) src/runtime/FiniteTerrain.js:361— FiniteTerrain.configure 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 3 function literals inside it that branch (lines 382, 408, 419). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ManualTerrainModeManager.setTexturePaintSetting (cyclomatic 26) src/manual/ManualTerrainModeManager.js:442— ManualTerrainModeManager.setTexturePaintSetting 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.
Engine.refreshCityMarkers (cyclomatic 26) src/engine/Engine.js:2676— Engine.refreshCityMarkers has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_autoPerfTick (cyclomatic 26) src/engine/Engine.js:11399— _autoPerfTick has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cyclomatic 26) src/engine/terrain/NearHeightCache.js:114— update 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.
TerrainSceneBuilder.Build (cyclomatic 25) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainSceneBuilder.cs:46— TerrainSceneBuilder.Build 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.
FiniteTerrainConfiguration.normalizeConfiguration (cyclomatic 25) src/runtime/FiniteTerrainConfiguration.js:69— FiniteTerrainConfiguration.normalizeConfiguration has cyclomatic complexity 25 (threshold 15). Of this number, 22 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.
_loadRealWorldHeightmap (cyclomatic 25) src/engine/Engine.js:1991— _loadRealWorldHeightmap has cyclomatic complexity 25 (threshold 15). Of this number, 18 points are the body's own statements and 7 belong to 9 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.
_tickInfinite (cyclomatic 25) src/engine/Engine.js:13730— _tickInfinite 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.
buildSurfaceAtlas (cyclomatic 25) src/engine/terrain/surface/SurfaceTextureAtlas.js:180— buildSurfaceAtlas has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 196, 202, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
cullChunks (cyclomatic 25) src/engine/terrain/InfiniteTerrainCulling.js:66— cullChunks 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.
GraphDocument.resolveGraphConnection (cyclomatic 24) src/engine/terrain/graph/GraphDocument.js:404— GraphDocument.resolveGraphConnection has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PlanetExportBuilder.build (cyclomatic 24) src/engine/terrain/PlanetExportBuilder.js:138— PlanetExportBuilder.build has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ManualTerrainModeManager._handleKeyDown (cyclomatic 24) src/manual/ManualTerrainModeManager.js:1119— ManualTerrainModeManager._handleKeyDown has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GenerationSettings.validate (cyclomatic 24) plugins/blender/procedural_terrains/generation.py:178— GenerationSettings.validate has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_prepareStudioHeightCacheAsync (cyclomatic 24) src/engine/Engine.js:10243— _prepareStudioHeightCacheAsync has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 10256, 10284, 10280). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_updateUnderwater (cyclomatic 24) src/engine/Engine.js:13360— _updateUnderwater has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
buildSurfaceResources (cyclomatic 24) src/engine/terrain/surface/SurfaceResources.js:56— buildSurfaceResources has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 19 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
validateProjectUpdate (cyclomatic 24) api/src/project-utils.js:61— validateProjectUpdate has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ManualTerrainField._stampErosion (cyclomatic 23) src/manual/ManualTerrainField.js:314— ManualTerrainField._stampErosion 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.
InputFrameBridge._bind (cyclomatic 23) src/engine/InputFrameBridge.js:80— InputFrameBridge._bind has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 109, a function literal at line 82, onContextMenu, …). 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.
PlayerController._updateWalk (cyclomatic 23) src/engine/player/PlayerController.js:192— PlayerController._updateWalk 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.
NodeWorkspace.TerrainNode (cyclomatic 23) REDACTED:152— NodeWorkspace.TerrainNode has cyclomatic complexity 23 (threshold 15). Of this number, 15 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AuthPage.AuthPage (cyclomatic 23) src/auth/AuthPage.jsx:12— AuthPage.AuthPage has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_buildFinalBootCompilePlan (cyclomatic 23) src/engine/Engine.js:6741— _buildFinalBootCompilePlan has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (add, replacePass, a function literal at line 6775, …). 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.
_schedulePostFirstPaintWarmups (cyclomatic 23) src/engine/Engine.js:7731— _schedulePostFirstPaintWarmups has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (run, a function literal at line 7798, a function literal at line 7750, …). 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.
SurfaceUploadQueue.uploadSurfaceTextures (cyclomatic 22) src/engine/terrain/surface/SurfaceUploadQueue.js:17— SurfaceUploadQueue.uploadSurfaceTextures has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Engine.setGenerationSource (cyclomatic 22) src/engine/Engine.js:3888— Engine.setGenerationSource has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 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.
ImportMapsContent.ImportMapSection (cyclomatic 22) src/components/ui/ImportMapsContent.jsx:115— ImportMapsContent.ImportMapSection has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_writeSurfaceAtlasUniforms (cyclomatic 22) src/engine/Engine.js:5037— _writeSurfaceAtlasUniforms has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to 8 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_compileSceneStaggered (cyclomatic 22) src/engine/Engine.js:6300— _compileSceneStaggered has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 6316, 6311, 6349). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_prepareHeightCacheProgram (cyclomatic 22) src/engine/Engine.js:10204— _prepareHeightCacheProgram has cyclomatic complexity 22 (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.
_composeItem (cyclomatic 22) src/engine/props/ProceduralPropsManager.js:540— _composeItem has cyclomatic complexity 22 (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.
compositeCellPatches (cyclomatic 22) src/engine/terrain/RealWorldHeightmap.js:582— compositeCellPatches 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.
densityForType (cyclomatic 22) src/engine/props/PropPlacement.js:52— densityForType has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
validateProfileUpdate (cyclomatic 22) api/src/profile-utils.js:9— validateProfileUpdate 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.
RealWorldBuildingLayer.rebuild (cyclomatic 21) src/engine/terrain/RealWorldBuildingLayer.js:44— RealWorldBuildingLayer.rebuild has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SplineMaskBaker.bake (cyclomatic 21) src/creator/splines/SplineMaskBaker.js:34— SplineMaskBaker.bake has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Engine._runInitialShaderBenchmark (cyclomatic 21) src/engine/Engine.js:6874— Engine._runInitialShaderBenchmark has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PopupProvider.PopupDialog (cyclomatic 21) src/components/ui/PopupProvider.jsx:33— PopupProvider.PopupDialog has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Markdown.Inline (cyclomatic 21) src/docs/Markdown.jsx:79— Markdown.Inline has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CodeEditor.CodeEditor (cyclomatic 21) src/docs/playground/CodeEditor.jsx:12— CodeEditor.CodeEditor has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function items inside it that branch (onKeyDown, syncScroll, edit, …). 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.
_packNoiseUniforms (cyclomatic 21) src/engine/Engine.js:3518— _packNoiseUniforms has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
waitForTerrainReady (cyclomatic 21) src/engine/Engine.js:7429— waitForTerrainReady has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cpuEvaluator (cyclomatic 21) src/engine/terrain/graph/GraphCompiler.js:796— cpuEvaluator has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 41 function items inside it that branch (evalNode::mountain, evalNode::mountain::cellular, evalNode::source, …). 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.
update (cyclomatic 21) src/engine/props/ProceduralPropsManager.js:218— update has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
parseOverpassBuildings (cyclomatic 21) src/engine/terrain/RealWorldBuildings.js:116— parseOverpassBuildings has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TerrainExport.exportTerrain (cyclomatic 20) src/runtime/export/TerrainExport.js:8— TerrainExport.exportTerrain has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EngineProxy.createEngineProxy (cyclomatic 20) src/engine/EngineProxy.js:472— EngineProxy.createEngineProxy has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodeWorkspace.InspectorField (cyclomatic 20) REDACTED:233— NodeWorkspace.InspectorField has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocsPage.Sidebar (cyclomatic 20) src/docs/DocsPage.jsx:49— DocsPage.Sidebar has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 59, onKeyDown, 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.
Landing.Landing::renderProjectCard (cyclomatic 20) src/landing/Landing.jsx:430— Landing.Landing::renderProjectCard 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 shape REPEATS in the file: one other method here (Landing.Landing) 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.
_syncImportedMapUniforms (cyclomatic 20) src/engine/Engine.js:2588— _syncImportedMapUniforms 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.
_updateInstanced (cyclomatic 20) src/engine/props/ProceduralPropsManager.js:870— _updateInstanced has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
packMaskUniforms (cyclomatic 20) src/engine/terrain/noise/noiseStackCodegen.js:185— packMaskUniforms has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
withEnergySaving::_tick (cyclomatic 20) src/engine/render/withEnergySaving.js:123— withEnergySaving::_tick has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cyclomatic 20) src/engine/render/UnderwaterController.js:77— update 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.
capture (cyclomatic 20) src/engine/water/WaterSurfacePass.js:98— capture has cyclomatic complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
GraphDocument.migrateGraphDocument.edges (cyclomatic 19) src/engine/terrain/graph/GraphDocument.js:91— GraphDocument.migrateGraphDocument.edges has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ManualTerrainField.stamp (cyclomatic 19) src/manual/ManualTerrainField.js:416— ManualTerrainField.stamp 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.
erosionSim.finalizeErosion (cyclomatic 19) src/engine/terrain/erosion/erosionSim.js:218— erosionSim.finalizeErosion 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.
SpatialUpscaler.resolveCameraReconstruction (cyclomatic 19) src/engine/render/SpatialUpscaler.js:19— SpatialUpscaler.resolveCameraReconstruction has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DestructionField.restore (cyclomatic 19) src/engine/destruction/DestructionField.js:454— DestructionField.restore has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PropModels.makeConiferGeometry (cyclomatic 19) src/engine/props/PropModels.js:151— PropModels.makeConiferGeometry 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.
ProceduralPropsManager._updatePlanet (cyclomatic 19) src/engine/props/ProceduralPropsManager.js:630— ProceduralPropsManager._updatePlanet 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.
Engine._validateCompiledPrograms (cyclomatic 19) src/engine/Engine.js:6083— Engine._validateCompiledPrograms has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Engine._finalBootMaterials (cyclomatic 19) src/engine/Engine.js:6689— Engine._finalBootMaterials has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Engine._upgradeMinimalTerrain (cyclomatic 19) src/engine/Engine.js:7600— Engine._upgradeMinimalTerrain has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 7603, 7668, 7690). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Engine._setPlaneMode (cyclomatic 19) src/engine/Engine.js:9078— Engine._setPlaneMode 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.
TerrainEvaluator._evaluate_stack (cyclomatic 19) plugins/blender/procedural_terrains/generation.py:634— TerrainEvaluator._evaluate_stack 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.
createFramePacket (cyclomatic 19) src/engine/Minimap.js:403— createFramePacket has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
stamp (cyclomatic 19) src/manual/SurfacePaintLayers.js:38— stamp 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.
rebuild (cyclomatic 19) src/engine/terrain/RealWorldMarkerLayer.js:46— rebuild has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 9 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.
constructor (cyclomatic 19) src/runtime/effects/EffectHost.js:9— constructor 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.
JsonValueSlice.TrySkipValue (cyclomatic 18) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:461— JsonValueSlice.TrySkipValue 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.
ManualSurfacePaintField.stamp (cyclomatic 18) src/manual/ManualSurfacePaintField.js:312— ManualSurfacePaintField.stamp has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PlanetWorld._foldPass (cyclomatic 18) src/engine/terrain/PlanetWorld.js:503— PlanetWorld._foldPass 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.
ParameterValidation.validateParameters (cyclomatic 18) src/runtime/resources/ParameterValidation.js:1— ParameterValidation.validateParameters 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.
RealWorldCities.fetchCityMarkers (cyclomatic 18) src/engine/terrain/RealWorldCities.js:18— RealWorldCities.fetchCityMarkers 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.
PlaneController._input (cyclomatic 18) src/engine/player/PlaneController.js:290— PlaneController._input 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.
Engine._tilePointerUp (cyclomatic 18) src/engine/Engine.js:1807— Engine._tilePointerUp 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.
Engine.setTileMapSetting (cyclomatic 18) src/engine/Engine.js:2412— Engine.setTileMapSetting 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.
Engine._applyUniforms (cyclomatic 18) src/engine/Engine.js:4890— Engine._applyUniforms 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.
Engine._prepareFinalBootResources (cyclomatic 18) src/engine/Engine.js:6574— Engine._prepareFinalBootResources has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Engine.setPerfSetting (cyclomatic 18) src/engine/Engine.js:11037— Engine.setPerfSetting has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Engine.resetPanelSettings (cyclomatic 18) src/engine/Engine.js:12308— Engine.resetPanelSettings has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
settingsSearch.scoreEntry (cyclomatic 18) src/components/panels/settingsSearch.js:318— settingsSearch.scoreEntry 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.
InfiniteHUD.InfiniteHUD (cyclomatic 18) src/components/InfiniteHUD.jsx:38— InfiniteHUD.InfiniteHUD has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SurfaceLibraryPanel.RoleCard (cyclomatic 18) REDACTED:292— SurfaceLibraryPanel.RoleCard has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 323, 374, 303, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AdminDashboard.AdminDashboard (cyclomatic 18) src/admin/AdminDashboard.jsx:417— AdminDashboard.AdminDashboard has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Markdown.Blocks (cyclomatic 18) src/docs/Markdown.jsx:150— Markdown.Blocks has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 151, 170, 185, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_setOctavesAsync (cyclomatic 18) src/engine/Engine.js:8455— _setOctavesAsync has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
createProjectPayload (cyclomatic 18) src/engine/Engine.js:11669— createProjectPayload 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.
_syncCausticWaveUniforms (cyclomatic 18) src/engine/Engine.js:13438— _syncCausticWaveUniforms 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.
_installSurface (cyclomatic 18) src/runtime/FiniteTerrain.js:113— _installSurface has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 5 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.
erodeWebGPU (cyclomatic 18) src/engine/terrain/erosion/erosionWebGPU.js:267— erodeWebGPU has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
createManualShape (cyclomatic 18) src/manual/ManualShapeCatalog.js:192— createManualShape has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
translateText (cyclomatic 18) src/i18n/language.js:50— translateText has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ManualShapeCatalog.normalizeManualShape (cyclomatic 17) src/manual/ManualShapeCatalog.js:226— ManualShapeCatalog.normalizeManualShape has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SurfaceArrayGLSL.syncSurfaceMaterialBackend (cyclomatic 17) src/engine/terrain/surface/SurfaceArrayGLSL.js:105— SurfaceArrayGLSL.syncSurfaceMaterialBackend has cyclomatic complexity 17 (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.
PaletteUniforms.applyPlanetStyleToUniforms (cyclomatic 17) src/engine/style/PaletteUniforms.js:44— PaletteUniforms.applyPlanetStyleToUniforms has cyclomatic complexity 17 (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.
SurfaceMapPreparation.prepareSurfaceMaps (cyclomatic 17) src/engine/terrain/surface/SurfaceMapPreparation.js:7— SurfaceMapPreparation.prepareSurfaceMaps has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
cloudFieldCPU.dilateMax (cyclomatic 17) src/engine/sky/cloudFieldCPU.js:165— cloudFieldCPU.dilateMax 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.
TerrainRenderPipeline.render (cyclomatic 17) src/runtime/effects/TerrainRenderPipeline.js:51— TerrainRenderPipeline.render has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 54, 62, 63). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DestructionField.finalizeCrater (cyclomatic 17) src/engine/destruction/DestructionField.js:230— DestructionField.finalizeCrater has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
PlayerController._updateSwim (cyclomatic 17) src/engine/player/PlayerController.js:266— PlayerController._updateSwim has cyclomatic complexity 17 (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.
ManualTerrainModeManager._handlePointerMove (cyclomatic 17) src/manual/ManualTerrainModeManager.js:913— ManualTerrainModeManager._handlePointerMove 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.
SplineManager._render (cyclomatic 17) src/creator/splines/SplineManager.js:67— SplineManager._render 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.
Engine._rebuildImportedTexture (cyclomatic 17) src/engine/Engine.js:2521— Engine._rebuildImportedTexture 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.
Engine._prepareFirstFrameShaders (cyclomatic 17) src/engine/Engine.js:5304— Engine._prepareFirstFrameShaders has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Engine._renderSharedOpaqueOverlays (cyclomatic 17) src/engine/Engine.js:5632— Engine._renderSharedOpaqueOverlays has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Engine._warmDeferredWater (cyclomatic 17) src/engine/Engine.js:7841— Engine._warmDeferredWater has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 7846, 7855). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ControlSection.ControlSection (cyclomatic 17) src/components/ui/ControlSection.jsx:119— ControlSection.ControlSection has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NoiseLayersPanel.NoiseLayersPanel (cyclomatic 17) src/components/NoiseLayersPanel.jsx:318— NoiseLayersPanel.NoiseLayersPanel 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 7 function items inside it that branch (handleDragEnd, handlePreset, handleUpdate, …). 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.
NodeWorkspace.graphCompileNodeIds (cyclomatic 17) REDACTED:72— NodeWorkspace.graphCompileNodeIds has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App.historyActionLabel (cyclomatic 17) src/App.jsx:124— App.historyActionLabel has cyclomatic complexity 17 (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.
engine.worker.onmessage (cyclomatic 17) src/engine/engine.worker.js:127— engine.worker.onmessage has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
ui._draw_layer (cyclomatic 17) plugins/blender/procedural_terrains/ui.py:44— ui._draw_layer has cyclomatic complexity 17 (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.
_upgradePlanetMaterials (cyclomatic 17) src/engine/Engine.js:10935— _upgradePlanetMaterials has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
planChange (cyclomatic 17) src/engine/mini/MiniTerrainController.js:104— planChange 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.
_createContext (cyclomatic 17) REDACTED:42— _createContext has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
createWaterBaselineReport (cyclomatic 17) src/engine/water/WaterBaseline.js:179— createWaterBaselineReport 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.
FiniteTerrain.update (cyclomatic 16) src/runtime/FiniteTerrain.js:454— FiniteTerrain.update has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InfiniteWorld._updateLOD (cyclomatic 16) src/engine/terrain/InfiniteWorld.js:469— InfiniteWorld._updateLOD 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.
CloudSlabLayer.update (cyclomatic 16) src/engine/sky/CloudSlabLayer.js:542— CloudSlabLayer.update has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FirstFrameShaderPreparation.request (cyclomatic 16) src/engine/render/FirstFrameShaderPreparation.js:6— FirstFrameShaderPreparation.request has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FPSControls.update (cyclomatic 16) src/engine/FPSControls.js:140— FPSControls.update has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CameraRenderPlan.resolveCameraRenderPlan (cyclomatic 16) src/engine/render/CameraRenderPlan.js:8— CameraRenderPlan.resolveCameraRenderPlan has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DestructionField.stampCrater (cyclomatic 16) src/engine/destruction/DestructionField.js:152— DestructionField.stampCrater 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.
ProceduralPropsManager._processPlanetBuild (cyclomatic 16) src/engine/props/ProceduralPropsManager.js:716— ProceduralPropsManager._processPlanetBuild 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.
Engine.compileWaterMaterialsAsync::run (cyclomatic 16) src/engine/Engine.js:6371— Engine.compileWaterMaterialsAsync::run has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EnergySavingEngine._tick (cyclomatic 16) src/engine/render/withEnergySaving.js:123— EnergySavingEngine._tick has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SettingsSearchOverlay.SettingsSearchOverlay (cyclomatic 16) src/components/ui/SettingsSearchOverlay.jsx:16— SettingsSearchOverlay.SettingsSearchOverlay has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (handleKeyDown, a function literal at line 110, a function literal at line 39, …). 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.
SurfaceResolutionSetting.SurfaceResolutionSetting (cyclomatic 16) src/components/ui/SurfaceResolutionSetting.jsx:6— SurfaceResolutionSetting.SurfaceResolutionSetting has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SurfaceLibraryPanel.SurfaceModeControls (cyclomatic 16) REDACTED:426— SurfaceLibraryPanel.SurfaceModeControls has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SplinesPanel.SplinesPanel (cyclomatic 16) src/components/panels/SplinesPanel.jsx:17— SplinesPanel.SplinesPanel has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
setRealWorldImageryStyle (cyclomatic 16) src/engine/Engine.js:2164— setRealWorldImageryStyle has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_updatePlinth (cyclomatic 16) src/engine/Engine.js:4833— _updatePlinth has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
compositeCellImagery (cyclomatic 16) src/engine/terrain/RealWorldHeightmap.js:666— compositeCellImagery 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.
createPropLitMaterial (cyclomatic 16) src/engine/props/PropModels.js:436— createPropLitMaterial has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
update (cyclomatic 16) REDACTED:181— update has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
App.App (cognitive 592) src/App.jsx:147— App.App has cognitive complexity 592 (threshold 15). Drivers by points: if/else 237 (278 pts), boolean chains 172, ternaries 75 (100 pts), error handling 29 (35 pts), loops 5 (6 pts), match/switch 1 (nesting depth added 73). Of this number, 75 points are the body's own statements and 517 belong to 148 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
build (cognitive 369) src/engine/terrain/TerrainExportBuilder.js:201— build has cognitive complexity 369 (threshold 15). Drivers by points: if/else 77 (168 pts), ternaries 36 (87 pts), loops 27 (64 pts), boolean chains 45, other 5 (nesting depth added 179). Of this number, 301 points are the body's own statements and 68 belong to 32 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.
NodeWorkspace.NodeWorkspace (cognitive 219) REDACTED:460— NodeWorkspace.NodeWorkspace has cognitive complexity 219 (threshold 15). Drivers by points: if/else 60 (79 pts), ternaries 53 (69 pts), boolean chains 54, loops 7 (15 pts), error handling 2 (nesting depth added 43). Of this number, 51 points are the body's own statements and 168 belong to 47 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ManualTerrainPanel.ManualTerrainPanel (cognitive 215) src/components/manual/ManualTerrainPanel.jsx:188— ManualTerrainPanel.ManualTerrainPanel has cognitive complexity 215 (threshold 15). Drivers by points: ternaries 59 (182 pts), if/else 12 (17 pts), boolean chains 15, loops 1 (nesting depth added 128). Of this number, 108 points are the body's own statements and 107 belong to 24 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.
_rebuildStackMaterialsAsync (cognitive 137) src/engine/Engine.js:4059— _rebuildStackMaterialsAsync has cognitive complexity 137 (threshold 15). Drivers by points: if/else 45 (77 pts), boolean chains 47, other 5, ternaries 4 (5 pts), loops 1 (2 pts), error handling 1 (nesting depth added 34). Of this number, 133 points are the body's own statements and 4 belong to 5 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.
TerrainGenerationSceneBuilder.Build (cognitive 109) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:35— TerrainGenerationSceneBuilder.Build has cognitive complexity 109 (threshold 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.
validateRuntimeTerrainDocument (cognitive 108) src/export/runtime/RuntimeTerrainValidator.js:18— validateRuntimeTerrainDocument has cognitive complexity 108 (threshold 15). Drivers by points: if/else 34 (76 pts), boolean chains 26, loops 1 (2 pts), other 2, ternaries 1 (2 pts) (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectLibrary.ProjectLibrary (cognitive 100) src/project/ProjectLibrary.jsx:40— ProjectLibrary.ProjectLibrary has cognitive complexity 100 (threshold 15). Drivers by points: boolean chains 35, ternaries 16 (34 pts), if/else 23 (26 pts), error handling 5 (nesting depth added 21). Most of this is not in the body itself: 11 of the 100 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 296, 186, 147, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_syncRealWorldNeighborTiles (cognitive 90) src/engine/Engine.js:2238— _syncRealWorldNeighborTiles has cognitive complexity 90 (threshold 15). Drivers by points: if/else 26 (40 pts), ternaries 10 (19 pts), boolean chains 14, error handling 4 (10 pts), loops 2 (6 pts), other 1 (nesting depth added 33). Of this number, 31 points are the body's own statements and 59 belong to 20 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.
_tickStudio (cognitive 89) src/engine/Engine.js:13534— _tickStudio has cognitive complexity 89 (threshold 15). Drivers by points: boolean chains 40, if/else 16 (26 pts), other 13, ternaries 4 (10 pts) (nesting depth added 16). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
loadSeedJSON (cognitive 87) src/engine/Engine.js:11742— loadSeedJSON has cognitive complexity 87 (threshold 15). Drivers by points: if/else 28 (38 pts), ternaries 23, boolean chains 17, loops 2 (4 pts), error handling 2 (3 pts), other 2 (nesting depth added 13). Of this number, 81 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
compileSurfaceGraph (cognitive 87) src/engine/terrain/surface/SurfaceGraph.js:23— compileSurfaceGraph has cognitive complexity 87 (threshold 15). Drivers by points: if/else 24 (39 pts), ternaries 10 (22 pts), boolean chains 14, other 10, loops 2 (nesting depth added 27). Of this number, 75 points are the body's own statements and 12 belong to 11 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.
erosionSim.erode (cognitive 78) src/engine/terrain/erosion/erosionSim.js:85— erosionSim.erode has cognitive complexity 78 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 8 (24 pts), ternaries 3 (12 pts), boolean chains 9 (nesting depth added 47). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
registerAdminRoutes (cognitive 76) REDACTED:45— registerAdminRoutes has cognitive complexity 76 (threshold 15). Drivers by points: if/else 37 (40 pts), ternaries 14 (15 pts), other 11, boolean chains 8, error handling 2 (nesting depth added 4). None of this is in the body itself: all 76 points belong to 25 function literals inside it that branch (lines 153, 214, 48, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
stamp (cognitive 74) src/paint/PaintLayerManager.js:263— stamp has cognitive complexity 74 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 7 (25 pts), ternaries 6 (20 pts), boolean chains 2, other 2 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
restoreState (cognitive 73) src/engine/Engine.js:12049— restoreState has cognitive complexity 73 (threshold 15). Drivers by points: if/else 23 (31 pts), ternaries 17 (20 pts), boolean chains 10, other 8, error handling 2 (4 pts) (nesting depth added 13). 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.
getPerfDiagnostics (cognitive 73) src/engine/Engine.js:13915— getPerfDiagnostics has cognitive complexity 73 (threshold 15). Drivers by points: other 25, ternaries 17 (25 pts), boolean chains 14, if/else 8 (9 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.
Engine._tickBody (cognitive 72) src/engine/Engine.js:13177— Engine._tickBody has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 21 (33 pts), if/else 23 (30 pts), boolean chains 9 (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.
_setDebugFreeCam (cognitive 70) src/engine/Engine.js:8633— _setDebugFreeCam has cognitive complexity 70 (threshold 15). Drivers by points: if/else 20 (33 pts), ternaries 8 (16 pts), other 12, boolean chains 5, error handling 2 (4 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update (cognitive 70) src/engine/sky/PlanetCloudChunks.js:351— update has cognitive complexity 70 (threshold 15). Drivers by points: if/else 23 (48 pts), boolean chains 12, loops 2 (5 pts), ternaries 3 (5 pts) (nesting depth added 30). 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.
generation_builder.build_generated_terrain (cognitive 66) plugins/blender/procedural_terrains/generation_builder.py:154— generation_builder.build_generated_terrain has cognitive complexity 66 (threshold 15). Drivers by points: loops 18 (30 pts), if/else 15 (29 pts), boolean chains 3, ternaries 3, error handling 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_swapMaterials (cognitive 66) src/engine/water/WaterSystem.js:612— _swapMaterials has cognitive complexity 66 (threshold 15). Drivers by points: if/else 22 (42 pts), boolean chains 16, other 8 (nesting depth added 20). Of this number, 23 points are the body's own statements and 43 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Landing.Landing (cognitive 65) src/landing/Landing.jsx:120— Landing.Landing has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 62, ternaries 50 (61 pts), if/else 44 (48 pts), error handling 5 (nesting depth added 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (Landing.Landing::renderProjectCard) 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.
WaterPanel.WaterPanelInner (cognitive 64) src/components/ui/WaterPanel.jsx:244— WaterPanel.WaterPanelInner has cognitive complexity 64 (threshold 15). Drivers by points: boolean chains 42, ternaries 13 (18 pts), if/else 4 (nesting depth added 5). Of this number, 55 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_stepFlatSector (cognitive 64) src/engine/props/ProceduralPropsManager.js:480— _stepFlatSector has cognitive complexity 64 (threshold 15). Drivers by points: if/else 9 (32 pts), boolean chains 10, ternaries 3 (10 pts), loops 3 (6 pts), other 6 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
applyMiniWaterLook (cognitive 64) src/engine/mini/MiniWaterMaterial.js:806— applyMiniWaterLook has cognitive complexity 64 (threshold 15). Drivers by points: if/else 21 (32 pts), other 21, ternaries 3 (7 pts), boolean chains 4 (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.
CommunityPage.CommunityPage (cognitive 63) REDACTED:65— CommunityPage.CommunityPage has cognitive complexity 63 (threshold 15). Drivers by points: ternaries 12 (26 pts), boolean chains 21, if/else 11 (12 pts), error handling 4 (nesting depth added 15). Most of this is not in the body itself: 15 of the 63 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 241, a function literal at line 85, a function literal at line 112, …). 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.
registerProjectRoutes (cognitive 63) REDACTED:55— registerProjectRoutes has cognitive complexity 63 (threshold 15). Drivers by points: if/else 29 (40 pts), other 11, ternaries 4, boolean chains 3, error handling 2 (3 pts), loops 2 (nesting depth added 12). None of this is in the body itself: all 63 points belong to 11 function literals inside it that branch (lines 125, 200, 223, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_updateFlat (cognitive 62) src/engine/props/ProceduralPropsManager.js:319— _updateFlat has cognitive complexity 62 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 18, loops 5 (6 pts), ternaries 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeWorkspace.NodeInspector (cognitive 61) REDACTED:318— NodeWorkspace.NodeInspector has cognitive complexity 61 (threshold 15). Drivers by points: ternaries 21 (44 pts), boolean chains 17 (nesting depth added 23). Of this number, 50 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
setTerrainGraph (cognitive 61) src/engine/Engine.js:3763— setTerrainGraph has cognitive complexity 61 (threshold 15). Drivers by points: if/else 20 (36 pts), boolean chains 16, error handling 1 (3 pts), loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 22). Of this number, 46 points are the body's own statements and 15 belong to 4 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.
TopBar.TopBar (cognitive 60) src/components/TopBar.jsx:44— TopBar.TopBar has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 27 (38 pts), boolean chains 12, if/else 10 (nesting depth added 11). Of this number, 44 points are the body's own statements and 16 belong to 13 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_warmDeferredWaterImpl (cognitive 60) src/engine/Engine.js:8044— _warmDeferredWaterImpl has cognitive complexity 60 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 13, other 10, error handling 2 (4 pts), ternaries 3 (nesting depth added 11). Of this number, 49 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bake (cognitive 60) src/creator/splines/SplineMaskBaker.js:34— bake has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 8 (28 pts), if/else 6 (19 pts), loops 4 (10 pts), boolean chains 3 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_compileMaterialVariants (cognitive 59) src/engine/Engine.js:5832— _compileMaterialVariants has cognitive complexity 59 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 21, ternaries 8 (9 pts), loops 2 (3 pts) (nesting depth added 8). Of this number, 53 points are the body's own statements and 6 belong to 19 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Engine.setParam (cognitive 57) src/engine/Engine.js:2776— Engine.setParam has cognitive complexity 57 (threshold 15). Drivers by points: if/else 29 (39 pts), boolean chains 12, ternaries 3 (6 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.
RuntimeTerrainDocumentValidator.Validate (cognitive 55) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:164— RuntimeTerrainDocumentValidator.Validate has cognitive complexity 55 (threshold 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.
ManualTerrainField._stampErosion (cognitive 55) src/manual/ManualTerrainField.js:314— ManualTerrainField._stampErosion has cognitive complexity 55 (threshold 15). Drivers by points: if/else 6 (29 pts), loops 9 (21 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.
runtime_document.validate_document (cognitive 54) plugins/blender/procedural_terrains/runtime_document.py:53— runtime_document.validate_document has cognitive complexity 54 (threshold 15). Drivers by points: if/else 24 (42 pts), boolean chains 10, loops 1 (2 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.
_compileShaderBenchmarkCandidate (cognitive 54) src/engine/Engine.js:6937— _compileShaderBenchmarkCandidate has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 30, ternaries 9 (13 pts), if/else 4 (6 pts), other 4, error handling 1 (nesting depth added 6). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dispose (cognitive 54) src/engine/Engine.js:14100— dispose has cognitive complexity 54 (threshold 15). Drivers by points: if/else 46, loops 4 (6 pts), boolean chains 1, other 1 (nesting depth added 2). 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.
TerrainGenerator.Validate (cognitive 52) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:42— TerrainGenerator.Validate has cognitive complexity 52 (threshold 15). Of this number, 51 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sanitizePerfSettings (cognitive 52) src/engine/render/PerformanceSettings.js:265— sanitizePerfSettings has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 35, ternaries 9, if/else 5 (6 pts), loops 1, other 1 (nesting depth added 1). Of this number, 50 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PlanetWorld.update (cognitive 49) src/engine/terrain/PlanetWorld.js:408— PlanetWorld.update has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 6 (16 pts), loops 4 (5 pts), boolean chains 4 (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.
RealWorldMapPicker.RealWorldMapPicker (cognitive 48) src/components/ui/RealWorldMapPicker.jsx:70— RealWorldMapPicker.RealWorldMapPicker has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 17, ternaries 8 (11 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 12 of the 48 points are its own statements and the rest belongs to 11 function items inside it that branch (searchPlaces, commitSelectionCenter, changeCoordinateFormat, …). 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.
PropsAssetLibrary.PropsAssetLibrary (cognitive 48) src/components/ui/PropsAssetLibrary.jsx:238— PropsAssetLibrary.PropsAssetLibrary has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 19, if/else 14, ternaries 11 (14 pts), error handling 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 31 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_applyCloudSettings (cognitive 48) src/engine/Engine.js:10624— _applyCloudSettings has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 8, error handling 2 (8 pts), ternaries 1 (4 pts), other 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManualSurfacePaintField.stamp (cognitive 47) src/manual/ManualSurfacePaintField.js:312— ManualSurfacePaintField.stamp has cognitive complexity 47 (threshold 15). Drivers by points: loops 8 (29 pts), if/else 6 (14 pts), boolean chains 2, ternaries 2 (nesting depth added 29). 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.
GraphCompiler.packUniforms (cognitive 46) src/engine/terrain/graph/GraphCompiler.js:681— GraphCompiler.packUniforms has cognitive complexity 46 (threshold 15). Drivers by points: if/else 27 (35 pts), loops 4 (11 pts) (nesting depth added 15). 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.
SurfacePaintLayers.stamp (cognitive 46) src/manual/SurfacePaintLayers.js:38— SurfacePaintLayers.stamp has cognitive complexity 46 (threshold 15). Drivers by points: loops 7 (21 pts), if/else 6 (14 pts), ternaries 3 (10 pts), boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManualTerrainImportDialog.ManualTerrainImportDialog (cognitive 46) src/components/ui/ManualTerrainImportDialog.jsx:10— ManualTerrainImportDialog.ManualTerrainImportDialog has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 15 (33 pts), boolean chains 7, if/else 6 (nesting depth added 18). Most of this is not in the body itself: 15 of the 46 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 113, 32, 43, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
applyRealisticWaterUniforms (cognitive 46) src/engine/water/RealisticWaterMaterial.js:1210— applyRealisticWaterUniforms has cognitive complexity 46 (threshold 15). Drivers by points: other 37, ternaries 8, if/else 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.
applyParams (cognitive 46) src/engine/sky/CloudSlabLayer.js:186— applyParams has cognitive complexity 46 (threshold 15). Drivers by points: other 26, boolean chains 11, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TerrainSceneBuilder.Build (cognitive 44) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainSceneBuilder.cs:46— TerrainSceneBuilder.Build has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
GraphDocument.validateGraph (cognitive 44) src/engine/terrain/graph/GraphDocument.js:272— GraphDocument.validateGraph has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 8, loops 4 (7 pts), error handling 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.
withEnergySaving.withEnergySaving (cognitive 44) src/engine/render/withEnergySaving.js:8— withEnergySaving.withEnergySaving has cognitive complexity 44 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 18, loops 2, ternaries 2 (nesting depth added 2). Of this number, 35 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SideDrawer.SideDrawer (cognitive 44) src/components/ui/SideDrawer.jsx:14— SideDrawer.SideDrawer has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 12, ternaries 10 (12 pts) (nesting depth added 4). Of this number, 19 points are the body's own statements and 25 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_rebuildPlanetStackMaterialsAsync (cognitive 44) src/engine/Engine.js:4343— _rebuildPlanetStackMaterialsAsync has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 11, loops 2 (3 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 8). Of this number, 32 points are the body's own statements and 12 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
constructor (cognitive 43) src/engine/Engine.js:277— constructor has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 13, ternaries 7, error handling 1 (2 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 13 of the 43 points are its own statements and the rest belongs to 14 function items inside it that branch (_onContextLost, _onContextRestored, _onVisibility, …). 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.
_warmupPlanetShaders (cognitive 43) src/engine/Engine.js:10838— _warmupPlanetShaders has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 17, if/else 12 (13 pts), ternaries 7 (11 pts), error handling 1, other 1 (nesting depth added 5). Of this number, 41 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
registerAuthRoutes (cognitive 43) REDACTED:103— registerAuthRoutes has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (21 pts), ternaries 4 (10 pts), boolean chains 5, error handling 4, other 3 (nesting depth added 8). None of this is in the body itself: all 43 points belong to 13 function literals inside it that branch (lines 106, 153, 216, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
transitionMode (cognitive 42) src/engine/Engine.js:9591— transitionMode has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (20 pts), error handling 4 (9 pts), boolean chains 8, loops 2 (4 pts), ternaries 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.
_setWorldModeImmediate (cognitive 42) src/engine/Engine.js:9681— _setWorldModeImmediate has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 10, ternaries 6, error handling 1 (2 pts), other 2 (nesting depth added 5). 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.
update (cognitive 42) src/engine/player/PlanetController.js:188— update has cognitive complexity 42 (threshold 15). Drivers by points: if/else 20 (27 pts), boolean chains 10, ternaries 5 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_sceneRevisionKey (cognitive 41) src/engine/Engine.js:5465— _sceneRevisionKey has cognitive complexity 41 (threshold 15). Drivers by points: other 26, boolean chains 10, ternaries 5. Of this number, 38 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dilateMax (cognitive 41) src/engine/sky/cloudFieldCPU.js:165— dilateMax has cognitive complexity 41 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 6 (16 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalizeTerrainSource (cognitive 41) src/runtime/TerrainSources.js:9— normalizeTerrainSource has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 9, other 3, loops 1, ternaries 1 (nesting depth added 10). Of this number, 39 points are the body's own statements and 2 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.
_tickInfinite (cognitive 40) src/engine/Engine.js:13730— _tickInfinite has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 8 (21 pts), if/else 12 (14 pts), boolean chains 3, other 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compositeCellPatches (cognitive 40) src/engine/terrain/RealWorldHeightmap.js:582— compositeCellPatches has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 6 (10 pts), ternaries 3 (8 pts), other 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.
detectRendererCapabilities (cognitive 40) src/engine/render/RendererCapabilities.js:37— detectRendererCapabilities has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 13, error handling 11 (12 pts), ternaries 7 (8 pts), if/else 7 (nesting depth added 2). Of this number, 30 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropModels.makeConiferGeometry (cognitive 39) src/engine/props/PropModels.js:151— PropModels.makeConiferGeometry has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 14 (32 pts), if/else 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SurfaceUploadQueue.uploadSurfaceTextures (cognitive 39) src/engine/terrain/surface/SurfaceUploadQueue.js:17— SurfaceUploadQueue.uploadSurfaceTextures has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 10 (18 pts), boolean chains 1 (nesting depth added 18). Of this number, 36 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Playground.Playground (cognitive 39) src/docs/playground/Playground.jsx:24— Playground.Playground has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 10 (11 pts), boolean chains 8, error handling 4 (nesting depth added 3). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 56, a function literal at line 45, a function literal at line 72, …). 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.
newProject (cognitive 39) src/engine/Engine.js:2952— newProject has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 13 (16 pts), if/else 11, boolean chains 9, other 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_tickPlanet (cognitive 39) src/engine/Engine.js:13812— _tickPlanet has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 6 (15 pts), boolean chains 5, other 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
beforeRender (cognitive 39) src/engine/mini/MiniTerrainController.js:276— beforeRender has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 9, ternaries 3 (6 pts), loops 1 (2 pts), other 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update (cognitive 39) src/engine/player/PlayerController.js:123— update has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 15, ternaries 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.
TerrainMaterial.buildFragmentSource (cognitive 38) src/engine/terrain/TerrainMaterial.js:499— TerrainMaterial.buildFragmentSource has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 23 (34 pts), boolean chains 4 (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.
ExportValidator.validateExport (cognitive 38) src/export/ExportValidator.js:7— ExportValidator.validateExport has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20, boolean chains 13, ternaries 3 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
NodeWorkspace.GraphNodeIcon (cognitive 38) REDACTED:57— NodeWorkspace.GraphNodeIcon has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 8 (36 pts), boolean chains 2 (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.
setNoiseStack (cognitive 38) src/engine/Engine.js:3567— setNoiseStack has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 12, ternaries 3 (5 pts), other 3 (nesting depth added 8). Of this number, 31 points are the body's own statements and 7 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.
_ensureTerrainShaderVariantAsync (cognitive 38) src/engine/Engine.js:11251— _ensureTerrainShaderVariantAsync has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 12, ternaries 7, error handling 1, other 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
export3DTerrain (cognitive 38) src/engine/Engine.js:12734— export3DTerrain has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 11, ternaries 5 (9 pts), loops 1 (3 pts), other 2, error handling 1 (nesting depth added 7). Of this number, 37 points are the body's own statements and 1 belongs to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
migrateGraphDocument (cognitive 38) src/engine/terrain/graph/GraphDocument.js:65— migrateGraphDocument has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 28, ternaries 6, if/else 3, other 1. Most of this is not in the body itself: 7 of the 38 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 91, 71, 115, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
createTerrainCodeDocument (cognitive 38) src/export/TerrainCodeExporter.js:17— createTerrainCodeDocument has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 10, ternaries 6, other 5 (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.
build (cognitive 38) src/engine/terrain/PlanetExportBuilder.js:138— build has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 7 (14 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 14). Of this number, 35 points are the body's own statements and 3 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.
buildSurfaceResources (cognitive 38) src/engine/terrain/surface/SurfaceResources.js:56— buildSurfaceResources has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 5, ternaries 4 (5 pts), loops 2 (4 pts), other 2, error handling 1 (nesting depth added 15). Of this number, 17 points are the body's own statements and 21 belong to 19 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.
normalizeConfiguration (cognitive 38) src/runtime/FiniteTerrainConfiguration.js:69— normalizeConfiguration has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 6, ternaries 3 (6 pts), boolean chains 4 (nesting depth added 12). Of this number, 35 points are the body's own statements and 3 belong to 4 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.
TerrainGenerator.Generate (cognitive 37) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:102— TerrainGenerator.Generate has cognitive complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkersPanel.MarkersPanel (cognitive 37) src/components/panels/MarkersPanel.jsx:8— MarkersPanel.MarkersPanel has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 17, ternaries 10 (12 pts), if/else 7 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (save, a function literal at line 54, a function literal at line 71, …). 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.
CloudProjectsPanel.CloudProjectsPanel (cognitive 37) src/project/CloudProjectsPanel.jsx:26— CloudProjectsPanel.CloudProjectsPanel has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 14, if/else 9, error handling 7, ternaries 4 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (sync, rename, a function literal at line 35, …). 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.
_completeBootIfQualityReady (cognitive 37) src/engine/Engine.js:7359— _completeBootIfQualityReady has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 21, if/else 8 (9 pts), other 5, error handling 1 (2 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_warmUnderwaterShaders (cognitive 37) src/engine/Engine.js:8281— _warmUnderwaterShaders has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 8, loops 3 (5 pts), other 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 7). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 8296, 8328, 8395, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_maybeFpsDowngrade (cognitive 37) src/engine/water/WaterSystem.js:1038— _maybeFpsDowngrade has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 9, other 5, 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.
erosionSim.finalizeErosion (cognitive 36) src/engine/terrain/erosion/erosionSim.js:218— erosionSim.finalizeErosion has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 8 (12 pts), ternaries 4 (12 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.
SurfaceLibraryPanel.SurfaceLibraryPanel (cognitive 36) REDACTED:498— SurfaceLibraryPanel.SurfaceLibraryPanel has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 16, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 36 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 528, 581, 562, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
applyParams (cognitive 36) src/engine/sky/PlanetCloudLayer.js:128— applyParams has cognitive complexity 36 (threshold 15). Drivers by points: other 23, boolean chains 7, if/else 4, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
parseOverpassBuildings (cognitive 36) src/engine/terrain/RealWorldBuildings.js:116— parseOverpassBuildings has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 8, loops 2 (3 pts), other 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.
captureSurfaceAtlasMaps (cognitive 36) src/engine/terrain/surface/SurfaceAtlasBridge.js:45— captureSurfaceAtlasMaps has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 3 (6 pts), ternaries 1 (6 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 25). Of this number, 19 points are the body's own statements and 17 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.
_installSurfaceAtlas (cognitive 35) src/engine/Engine.js:5068— _installSurfaceAtlas has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 15, if/else 12 (14 pts), ternaries 3 (4 pts), loops 1 (2 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 13 belong to 8 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_targetTerrainVariant (cognitive 35) src/engine/Engine.js:11222— _targetTerrainVariant has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts), ternaries 4 (10 pts), other 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.
ManualTerrainField.stamp (cognitive 34) src/manual/ManualTerrainField.js:416— ManualTerrainField.stamp has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 4 (12 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
applyParams (cognitive 34) src/engine/sky/PlanetCloudChunks.js:229— applyParams has cognitive complexity 34 (threshold 15). Drivers by points: other 22, boolean chains 7, if/else 3, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
createFramePacket (cognitive 34) src/engine/Minimap.js:403— createFramePacket has cognitive complexity 34 (threshold 15). Drivers by points: loops 5 (16 pts), ternaries 4 (7 pts), if/else 5 (6 pts), boolean chains 4, other 1 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TerrainGenerationPresets.ApplyTerrainPreset (cognitive 33) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationPresets.cs:8— TerrainGenerationPresets.ApplyTerrainPreset has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DetailPageCache.update (cognitive 33) src/engine/terrain/detail/DetailPageCache.js:88— DetailPageCache.update has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 5 (8 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramHealthGate.inspectProgram (cognitive 33) src/engine/render/ProgramHealthGate.js:47— ProgramHealthGate.inspectProgram has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (8 pts), ternaries 3, error handling 2, loops 2 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DestructionField.stampCrater (cognitive 33) src/engine/destruction/DestructionField.js:152— DestructionField.stampCrater has cognitive complexity 33 (threshold 15). Drivers by points: if/else 3 (13 pts), loops 4 (10 pts), ternaries 5 (7 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProceduralPropsManager._processPlanetBuild (cognitive 33) src/engine/props/ProceduralPropsManager.js:716— ProceduralPropsManager._processPlanetBuild has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (27 pts), boolean chains 5, 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.
Engine._rebuildImportedTexture (cognitive 33) src/engine/Engine.js:2521— Engine._rebuildImportedTexture has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 3 (5 pts), boolean chains 1, ternaries 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.
ImportMapsContent.CustomAreaPicker (cognitive 33) src/components/ui/ImportMapsContent.jsx:323— ImportMapsContent.CustomAreaPicker has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 11, ternaries 7 (10 pts) (nesting depth added 4). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (commitCoordText, load, a function literal at line 342, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.TerrainPanel (cognitive 33) src/components/panels/index.jsx:105— index.TerrainPanel has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 18, ternaries 9 (12 pts), if/else 3 (nesting depth added 3). Of this number, 26 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
configure (cognitive 33) src/runtime/FiniteTerrain.js:361— configure has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 8, ternaries 2, error handling 1, loops 1 (nesting depth added 7). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 382, a function literal at line 408, (anonymous)::check, …). 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.
LeftToolbar.LeftToolbar (cognitive 32) src/components/ui/LeftToolbar.jsx:25— LeftToolbar.LeftToolbar has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 14, if/else 13 (14 pts), ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 9 of the 32 points are its own statements and the rest belongs to 12 function items inside it that branch (startDrag, a function literal at line 85, a function literal at line 190, …). 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.
_loadRealWorldHeightmap (cognitive 32) src/engine/Engine.js:1991— _loadRealWorldHeightmap has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 3 (5 pts), other 4, boolean chains 2, error handling 2 (nesting depth added 7). Of this number, 20 points are the body's own statements and 12 belong to 9 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.
setTexturePaintSetting (cognitive 32) src/manual/ManualTerrainModeManager.js:442— setTexturePaintSetting has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 5 (10 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.
normalizeProject (cognitive 32) src/project/ProjectStore.js:100— normalizeProject has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 12, other 11, boolean chains 9. 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.
cullChunks (cognitive 32) src/engine/terrain/InfiniteTerrainCulling.js:66— cullChunks has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (22 pts), other 7, boolean chains 1, loops 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.
InputFrameBridge._bind (cognitive 31) src/engine/InputFrameBridge.js:80— InputFrameBridge._bind has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7, error handling 2 (6 pts), loops 3 (nesting depth added 9). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 109, onContextMenu, a function literal at line 82, …). 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.
_writeSurfaceAtlasUniforms (cognitive 31) src/engine/Engine.js:5037— _writeSurfaceAtlasUniforms has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 8 (11 pts), boolean chains 5, other 2 (nesting depth added 10). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 5045, 5041, 5050, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_ensureTerrainHeightTex (cognitive 31) src/engine/Engine.js:10389— _ensureTerrainHeightTex has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 6 (8 pts), boolean chains 4, other 2 (nesting depth added 4). Of this number, 28 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
generateWaterMasks (cognitive 31) src/engine/water/WaterMaskArtifacts.js:17— generateWaterMasks has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (16 pts), if/else 3 (8 pts), loops 5 (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.
_schedulePostFirstPaintWarmups (cognitive 30) src/engine/Engine.js:7731— _schedulePostFirstPaintWarmups has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 4, ternaries 2 (4 pts), error handling 2 (3 pts), other 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (run, a function literal at line 7798, a function literal at line 7826, …). 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.
_warmupInfiniteShaders (cognitive 30) src/engine/Engine.js:9955— _warmupInfiniteShaders has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 11, ternaries 2 (3 pts), error handling 1, other 1 (nesting depth added 2). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
estimateExport (cognitive 30) src/export/ExportDiagnostics.js:14— estimateExport has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 14, boolean chains 13, if/else 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rebuild (cognitive 30) src/engine/terrain/RealWorldBuildingLayer.js:44— rebuild has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (7 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MinimapOverlay.MinimapOverlay (cognitive 29) src/components/MinimapOverlay.jsx:38— MinimapOverlay.MinimapOverlay has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 8 (9 pts), boolean chains 7 (nesting depth added 3). Most of this is not in the body itself: 11 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 105, updateHover, a function literal at line 77, …). 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.
update (cognitive 29) src/engine/terrain/NearHeightCache.js:114— update has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, ternaries 3 (4 pts), other 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.
validateProfileUpdate (cognitive 29) api/src/profile-utils.js:9— validateProfileUpdate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (17 pts), other 7, error handling 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfiniteWorld._updateLOD (cognitive 28) src/engine/terrain/InfiniteWorld.js:469— InfiniteWorld._updateLOD has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 3 (7 pts), boolean chains 4, loops 3 (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.
DocsPage.DocsPage (cognitive 28) src/docs/DocsPage.jsx:160— DocsPage.DocsPage has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), ternaries 5, loops 1 (nesting depth added 1). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 179, a function literal at line 198, a function literal at line 188, …). 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.
compositeCellImagery (cognitive 28) src/engine/terrain/RealWorldHeightmap.js:666— compositeCellImagery has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 5 (8 pts), ternaries 2 (7 pts), other 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.
SurfaceMapPreparation.prepareSurfaceMaps (cognitive 27) src/engine/terrain/surface/SurfaceMapPreparation.js:7— SurfaceMapPreparation.prepareSurfaceMaps has cognitive complexity 27 (threshold 15). Drivers by points: loops 8 (20 pts), if/else 3 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 14). Of this number, 26 points are the body's own statements and 1 belongs to 2 function items inside it that branch. 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.
UnderwaterController.update (cognitive 27) src/engine/render/UnderwaterController.js:77— UnderwaterController.update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, ternaries 1 (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.
ProceduralPropsManager._composeItem (cognitive 27) src/engine/props/ProceduralPropsManager.js:540— ProceduralPropsManager._composeItem has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 11 (13 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.
SplineManager._render (cognitive 27) src/creator/splines/SplineManager.js:67— SplineManager._render has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 4 (8 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.
Engine.setGenerationSource (cognitive 27) src/engine/Engine.js:3888— Engine.setGenerationSource has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 9, ternaries 4 (6 pts) (nesting depth added 5). Of this number, 20 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runner.iframeBootstrap (cognitive 27) src/docs/playground/runner.js:15— runner.iframeBootstrap has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 6, loops 4, error handling 2, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (report, start, describe, …). 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.
_applySurfaceSettings (cognitive 27) src/engine/Engine.js:4980— _applySurfaceSettings has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 7, other 6, boolean chains 5 (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.
_completeBootIfInteractiveReady (cognitive 27) src/engine/Engine.js:7310— _completeBootIfInteractiveReady has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 17, if/else 5, error handling 1 (2 pts), other 2, ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
setSculptSetting (cognitive 27) src/manual/ManualTerrainModeManager.js:393— setSculptSetting has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13, boolean chains 12, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
update (cognitive 27) src/engine/render/VisualPostProcess.js:469— update has cognitive complexity 27 (threshold 15). Drivers by points: other 14, ternaries 9 (10 pts), if/else 2, boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlayerController._updateWalk (cognitive 26) src/engine/player/PlayerController.js:192— PlayerController._updateWalk has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 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.
SplineSerializer.migrateSplines (cognitive 26) src/creator/splines/SplineSerializer.js:7— SplineSerializer.migrateSplines has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, ternaries 6 (8 pts), if/else 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 9, 13). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PlanetCloudChunks._buildTerrainChunkMap (cognitive 26) src/engine/sky/PlanetCloudChunks.js:197— PlanetCloudChunks._buildTerrainChunkMap has cognitive complexity 26 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 3 (11 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
index.ExportPanel (cognitive 26) src/components/panels/index.jsx:937— index.ExportPanel has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 15, ternaries 8 (10 pts), if/else 1 (nesting depth added 2). Of this number, 20 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ProfilePage.ProfilePage (cognitive 26) src/auth/ProfilePage.jsx:11— ProfilePage.ProfilePage has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 9, ternaries 8, if/else 6, error handling 3. Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (savePassword, chooseAvatar, passwordField, …). 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.
AdminDashboard.UsersPanel (cognitive 26) src/admin/AdminDashboard.jsx:186— AdminDashboard.UsersPanel has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, ternaries 8 (10 pts), error handling 3, if/else 2 (nesting depth added 2). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (update, revoke, a function literal at line 202, …). 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.
Landing.Landing::renderProjectCard (cognitive 26) src/landing/Landing.jsx:430— Landing.Landing::renderProjectCard has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 14 (21 pts), boolean chains 5 (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. This shape REPEATS in the file: one other method here (Landing.Landing) 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.
_syncImportedMapUniforms (cognitive 26) src/engine/Engine.js:2588— _syncImportedMapUniforms has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (7 pts), other 5, boolean chains 3, 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.
_packNoiseUniforms (cognitive 26) src/engine/Engine.js:3518— _packNoiseUniforms has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 5 (6 pts), boolean chains 3, loops 2 (3 pts), other 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.
_compileMaterialDescriptor (cognitive 26) src/engine/Engine.js:5775— _compileMaterialDescriptor has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, if/else 9, other 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_buildFinalBootCompilePlan (cognitive 26) src/engine/Engine.js:6741— _buildFinalBootCompilePlan has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 4 (6 pts), loops 4, other 2 (nesting depth added 4). Of this number, 13 points are the body's own statements and 13 belong to 6 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.
_updateUnderwater (cognitive 26) src/engine/Engine.js:13360— _updateUnderwater has cognitive complexity 26 (threshold 15). Drivers by points: other 12, if/else 3 (5 pts), ternaries 3 (5 pts), boolean chains 4 (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.
requestOverpass (cognitive 26) src/engine/terrain/RealWorldBuildings.js:189— requestOverpass has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 2 (4 pts), boolean chains 3, loops 1, other 1 (nesting depth added 12). Of this number, 14 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validateProjectUpdate (cognitive 26) api/src/project-utils.js:61— validateProjectUpdate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), other 10, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
JsonValueSlice.TrySkipValue (cognitive 25) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:461— JsonValueSlice.TrySkipValue has cognitive complexity 25 (threshold 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.
TerrainGenerator.EvaluateMask (cognitive 25) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:276— TerrainGenerator.EvaluateMask has cognitive complexity 25 (threshold 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.
noiseTypes.voronoiJs3 (cognitive 25) src/engine/terrain/noise/noiseTypes.js:452— noiseTypes.voronoiJs3 has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 5 (8 pts), loops 3 (6 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.
AuthPage.AuthPage (cognitive 25) src/auth/AuthPage.jsx:12— AuthPage.AuthPage has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 4, if/else 4, error handling 1 (nesting depth added 2). Of this number, 13 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GenerationSettings.validate (cognitive 25) plugins/blender/procedural_terrains/generation.py:178— GenerationSettings.validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 8, loops 2 (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.
_compileSceneStaggered (cognitive 25) src/engine/Engine.js:6300— _compileSceneStaggered has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 4, loops 1, other 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
waitForTerrainReady (cognitive 25) src/engine/Engine.js:7429— waitForTerrainReady has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (10 pts), ternaries 1 (3 pts), loops 1, other 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.
_setPlaneMode (cognitive 25) src/engine/Engine.js:9078— _setPlaneMode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 5 (10 pts), boolean chains 4 (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.
_foldPass (cognitive 25) src/engine/terrain/PlanetWorld.js:503— _foldPass has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 8). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildSurfaceAtlas (cognitive 25) src/engine/terrain/surface/SurfaceTextureAtlas.js:180— buildSurfaceAtlas has cognitive complexity 25 (threshold 15). Drivers by points: loops 6 (9 pts), ternaries 9, boolean chains 4, if/else 2, other 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 196, 202, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
rebuild (cognitive 25) src/engine/terrain/RealWorldMarkerLayer.js:46— rebuild has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, loops 3 (4 pts), other 2 (nesting depth added 7). Of this number, 19 points are the body's own statements and 6 belong to 9 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.
GraphDocument.resolveGraphConnection (cognitive 24) src/engine/terrain/graph/GraphDocument.js:404— GraphDocument.resolveGraphConnection has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (7 pts), ternaries 4, loops 1 (nesting depth added 1). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TerrainBoard._updateChunkLOD (cognitive 24) src/engine/terrain/TerrainBoard.js:567— TerrainBoard._updateChunkLOD has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (16 pts), if/else 2 (4 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TerrainExport.exportTerrain (cognitive 24) src/runtime/export/TerrainExport.js:8— TerrainExport.exportTerrain has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 7 (9 pts), boolean chains 4, loops 1 (nesting depth added 8). Of this number, 14 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloudPanel.CloudPanel (cognitive 24) src/components/ui/CloudPanel.jsx:102— CloudPanel.CloudPanel has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, boolean chains 7, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 18 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
SurfaceLibraryPanel.importDroppedTextures (cognitive 24) REDACTED:72— SurfaceLibraryPanel.importDroppedTextures has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (5 pts), error handling 1 (3 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.
DocsPage.Sidebar (cognitive 24) src/docs/DocsPage.jsx:49— DocsPage.Sidebar has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 7 (8 pts), boolean chains 5 (nesting depth added 5). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 59, onKeyDown, 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.
refreshCityMarkers (cognitive 24) src/engine/Engine.js:2676— refreshCityMarkers has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (11 pts), error handling 1, loops 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_prepareHeightCacheProgram (cognitive 24) src/engine/Engine.js:10204— _prepareHeightCacheProgram has cognitive complexity 24 (threshold 15). Drivers by points: other 10, if/else 5, ternaries 2 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_autoPerfTick (cognitive 24) src/engine/Engine.js:11399— _autoPerfTick has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 8 (10 pts), other 1, ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
cpuEvaluator (cognitive 24) src/engine/terrain/graph/GraphCompiler.js:796— cpuEvaluator has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8, if/else 5 (7 pts), boolean chains 4, loops 2 (3 pts), other 2 (nesting depth added 3). None of this is in the body itself: all 24 points belong to 41 function items inside it that branch (evalNode::mountain::cellular, evalNode::mountain, evalNode::source, …). 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.
_handleKeyDown (cognitive 24) src/manual/ManualTerrainModeManager.js:1119— _handleKeyDown has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 8 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TerrainProjectImporter.OnImportAsset (cognitive 23) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainProjectImporter.cs:14— TerrainProjectImporter.OnImportAsset has cognitive complexity 23 (threshold 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.
RendererReadback.readRenderTargetPixelsAsync (cognitive 23) src/engine/render/RendererReadback.js:9— RendererReadback.readRenderTargetPixelsAsync has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, error handling 1 (3 pts), ternaries 1 (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.
ProceduralPropsManager._replaceMeshes (cognitive 23) src/engine/props/ProceduralPropsManager.js:809— ProceduralPropsManager._replaceMeshes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 5 (7 pts), ternaries 2 (5 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.
PopupProvider.PopupDialog (cognitive 23) src/components/ui/PopupProvider.jsx:33— PopupProvider.PopupDialog has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (14 pts), boolean chains 7, if/else 2 (nesting depth added 4). Of this number, 15 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
builder.build_project (cognitive 23) plugins/blender/procedural_terrains/builder.py:265— builder.build_project has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (8 pts), boolean chains 2, error handling 1, ternaries 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.
_prepareFinalBootResources (cognitive 23) src/engine/Engine.js:6574— _prepareFinalBootResources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 5). Of this number, 22 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
planChange (cognitive 23) src/engine/mini/MiniTerrainController.js:104— planChange has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), other 5, boolean chains 3, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capture (cognitive 23) src/engine/water/WaterPlanarReflectionPass.js:199— capture has cognitive complexity 23 (threshold 15). Drivers by points: other 9, boolean chains 6, if/else 6, loops 2. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DestructionField.smoothEdges (cognitive 22) src/engine/destruction/DestructionField.js:291— DestructionField.smoothEdges has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeWorkspace.TerrainNode (cognitive 22) REDACTED:152— NodeWorkspace.TerrainNode has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 17, boolean chains 5. Of this number, 14 points are the body's own statements and 8 belong to 2 function literals inside it that branch. 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.
Markdown.Inline (cognitive 22) src/docs/Markdown.jsx:79— Markdown.Inline has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 3, ternaries 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 12). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
operators.register (cognitive 22) plugins/blender/procedural_terrains/operators.py:457— operators.register has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (5 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ui.register (cognitive 22) plugins/blender/procedural_terrains/ui.py:226— ui.register has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 3 (7 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_legacySetPlayerMode (cognitive 22) src/engine/Engine.js:9124— _legacySetPlayerMode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 1, other 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.
packMaskUniforms (cognitive 22) src/engine/terrain/noise/noiseStackCodegen.js:185— packMaskUniforms has cognitive complexity 22 (threshold 15). Drivers by points: other 9, ternaries 3 (6 pts), boolean chains 4, if/else 3 (nesting depth added 3). Of this number, 19 points are the body's own statements and 3 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.
SurfaceArrayGLSL.syncSurfaceMaterialBackend (cognitive 21) src/engine/terrain/surface/SurfaceArrayGLSL.js:105— SurfaceArrayGLSL.syncSurfaceMaterialBackend has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 6, ternaries 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.
ParameterValidation.validateParameters (cognitive 21) src/runtime/resources/ParameterValidation.js:1— ParameterValidation.validateParameters has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 7, ternaries 1 (2 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.
Engine._finalBootMaterials (cognitive 21) src/engine/Engine.js:6689— Engine._finalBootMaterials has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, loops 3, ternaries 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
settingsSearch.scoreEntry (cognitive 21) src/components/panels/settingsSearch.js:318— settingsSearch.scoreEntry has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeWorkspace.InspectorField (cognitive 21) REDACTED:233— NodeWorkspace.InspectorField has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (7 pts), if/else 5 (6 pts) (nesting depth added 3). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
archive._validate_archive (cognitive 21) plugins/blender/procedural_terrains/archive.py:46— archive._validate_archive has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_applyUniforms (cognitive 21) src/engine/Engine.js:4890— _applyUniforms has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 6 (8 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_setOctavesAsync (cognitive 21) src/engine/Engine.js:8455— _setOctavesAsync has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, other 2, ternaries 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 8505, 8472, 8489, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_prepareStudioHeightCacheAsync (cognitive 21) src/engine/Engine.js:10243— _prepareStudioHeightCacheAsync has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 7, other 3, error handling 1. Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 10256, 10284, 10280). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_updatePlanet (cognitive 21) src/engine/props/ProceduralPropsManager.js:630— _updatePlanet has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, ternaries 3 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
_updateInstanced (cognitive 21) src/engine/props/ProceduralPropsManager.js:870— _updateInstanced has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7, loops 1, other 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
setCircularBoundary (cognitive 21) src/engine/terrain/TerrainBoard.js:450— setCircularBoundary has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 12, if/else 4 (5 pts), ternaries 2, loops 1, other 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
withEnergySaving::_tick (cognitive 21) src/engine/render/withEnergySaving.js:123— withEnergySaving::_tick has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (6 pts), other 4 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
translateText (cognitive 21) src/i18n/language.js:50— translateText has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (2 pts), other 2, ternaries 2 (nesting depth added 4). Of this number, 19 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
update (cognitive 21) src/engine/sky/CloudAdaptiveQualityController.js:63— update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (18 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.
EffectQuality.effectQuality (cognitive 20) src/runtime/effects/EffectQuality.js:8— EffectQuality.effectQuality has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 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.
EngineProxy.createEngineProxy (cognitive 20) src/engine/EngineProxy.js:472— EngineProxy.createEngineProxy has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 9, if/else 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_getPropSampler (cognitive 20) src/engine/Engine.js:10737— _getPropSampler has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (5 pts), other 5, boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 9 function items inside it that branch (getPaintMask, getPaintBiomeWeights, getPropExclusion, …). 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.
_handlePointerMove (cognitive 20) src/manual/ManualTerrainModeManager.js:913— _handlePointerMove has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 2 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_syncCustomModels (cognitive 20) src/engine/props/ProceduralPropsManager.js:277— _syncCustomModels has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (nesting depth added 9). Of this number, 14 points are the body's own statements and 6 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.
_visitNode (cognitive 20) src/engine/terrain/TerrainBoard.js:532— _visitNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, 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.
_installSurface (cognitive 20) src/runtime/FiniteTerrain.js:113— _installSurface has cognitive complexity 20 (threshold 15). Drivers by points: other 11, ternaries 5 (8 pts), if/else 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 10 belong to 5 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.
erodeWebGPU (cognitive 20) src/engine/terrain/erosion/erosionWebGPU.js:267— erodeWebGPU has cognitive complexity 20 (threshold 15). Drivers by points: loops 8 (9 pts), if/else 4 (5 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 3). 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.
constructor (cognitive 20) src/runtime/effects/EffectHost.js:9— constructor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (6 pts), other 6, boolean chains 4, ternaries 2 (3 pts), loops 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.
TerrainGenerator.Voronoi (cognitive 19) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:519— TerrainGenerator.Voronoi has cognitive complexity 19 (threshold 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.
noiseTypes.voronoiJs2 (cognitive 19) src/engine/terrain/noise/noiseTypes.js:433— noiseTypes.voronoiJs2 has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (7 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
terrainGLSL.countReferencedSamplers (cognitive 19) src/engine/terrain/terrainGLSL.js:378— terrainGLSL.countReferencedSamplers has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerrainBoard.cull (cognitive 19) src/engine/terrain/TerrainBoard.js:803— TerrainBoard.cull has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (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.
Minimap.renderBase (cognitive 19) src/engine/Minimap.js:248— Minimap.renderBase has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (5 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DestructionField.restore (cognitive 19) src/engine/destruction/DestructionField.js:454— DestructionField.restore has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 8, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExplodeTool.update (cognitive 19) src/engine/destruction/ExplodeTool.js:322— ExplodeTool.update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Engine._tilePointerUp (cognitive 19) src/engine/Engine.js:1807— Engine._tilePointerUp has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7 (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.
SettingsSearchOverlay.SettingsSearchOverlay (cognitive 19) src/components/ui/SettingsSearchOverlay.jsx:16— SettingsSearchOverlay.SettingsSearchOverlay has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (6 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (handleKeyDown, a function literal at line 110, a function literal at line 39, …). 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.
NodeWorkspace.graphCompileNodeIds (cognitive 19) REDACTED:72— NodeWorkspace.graphCompileNodeIds has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, loops 4 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_updatePlinth (cognitive 19) src/engine/Engine.js:4833— _updatePlinth has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 3 (4 pts), other 3, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_upgradeMinimalTerrain (cognitive 19) src/engine/Engine.js:7600— _upgradeMinimalTerrain has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 7603, 7668, 7690). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
finalizeCrater (cognitive 19) src/engine/destruction/DestructionField.js:230— finalizeCrater has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (10 pts), boolean chains 4, ternaries 1 (3 pts), if/else 2 (nesting depth added 5). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
_writeWeights (cognitive 19) src/manual/ManualSurfacePaintField.js:232— _writeWeights has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 5 (8 pts), loops 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.
_input (cognitive 19) src/engine/player/PlaneController.js:290— _input has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, ternaries 7, if/else 3 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
stamp (cognitive 19) src/manual/ManualPropPaintField.js:165— stamp has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (7 pts), other 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.
D2 · Cognitive Complexity· run (cognitive 19) · ×1
run (cognitive 19) src/engine/render/ShaderBenchmark.js:110— run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 5, loops 2 (3 pts), ternaries 3, other 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 5 belong to 9 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.
densityForType (cognitive 19) src/engine/props/PropPlacement.js:52— densityForType has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 4, other 4, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
JsonValueSlice.TryExtractTopLevelProperty (cognitive 18) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:402— JsonValueSlice.TryExtractTopLevelProperty has cognitive complexity 18 (threshold 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.
PlayerController._clampToBounds (cognitive 18) src/engine/player/PlayerController.js:91— PlayerController._clampToBounds has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Engine._renderSharedOpaqueOverlays (cognitive 18) src/engine/Engine.js:5632— Engine._renderSharedOpaqueOverlays has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, loops 4 (6 pts), if/else 3 (4 pts) (nesting depth added 3). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SurfaceTextureImport.collectSurfaceTextureSets (cognitive 18) src/engine/terrain/surface/SurfaceTextureImport.js:15— SurfaceTextureImport.collectSurfaceTextureSets has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, 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.
engine.worker.onmessage (cognitive 18) src/engine/engine.worker.js:127— engine.worker.onmessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, error handling 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.
setTileMapSetting (cognitive 18) src/engine/Engine.js:2412— setTileMapSetting has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 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.
_runInitialShaderBenchmark (cognitive 18) src/engine/Engine.js:6874— _runInitialShaderBenchmark has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 1. Of this number, 15 points are the body's own statements and 3 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_compileModeTransition (cognitive 18) src/engine/Engine.js:9513— _compileModeTransition has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, other 2, ternaries 1 (2 pts) (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.
createProjectPayload (cognitive 18) src/engine/Engine.js:11669— createProjectPayload has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5, other 2, boolean chains 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
applyUniforms (cognitive 18) src/engine/mini/MiniTerrainController.js:160— applyUniforms has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 6, boolean chains 2, other 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
load (cognitive 18) src/manual/ManualPropPaintField.js:231— load has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 5, loops 2 (5 pts), other 2 (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.
capture (cognitive 18) src/engine/water/WaterSurfacePass.js:98— capture has cognitive complexity 18 (threshold 15). Drivers by points: other 8, loops 4 (5 pts), if/else 3, boolean chains 2 (nesting depth added 1). 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.
PaletteUniforms.applyPlanetStyleToUniforms (cognitive 17) src/engine/style/PaletteUniforms.js:44— PaletteUniforms.applyPlanetStyleToUniforms has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LodMorph.stepTemporalLod (cognitive 17) src/engine/terrain/LodMorph.js:81— LodMorph.stepTemporalLod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (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.
RealWorldHeightmap.fetchBboxStitched (cognitive 17) src/engine/terrain/RealWorldHeightmap.js:379— RealWorldHeightmap.fetchBboxStitched has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 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.
TerrainRenderPipeline.render (cognitive 17) src/runtime/effects/TerrainRenderPipeline.js:51— TerrainRenderPipeline.render has cognitive complexity 17 (threshold 15). Drivers by points: loops 9, if/else 4 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 54, 62, 63). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Engine._sanitizeTiles (cognitive 17) src/engine/Engine.js:1407— Engine._sanitizeTiles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Engine._stackWithCompatParam (cognitive 17) src/engine/Engine.js:3415— Engine._stackWithCompatParam has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4 (nesting depth added 3). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
Engine.compileWaterMaterialsAsync::run (cognitive 17) src/engine/Engine.js:6371— Engine.compileWaterMaterialsAsync::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, error handling 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.
authValidation.validateAuthFields (cognitive 17) src/auth/authValidation.js:1— authValidation.validateAuthFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 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.
builder._cleanup (cognitive 17) plugins/blender/procedural_terrains/builder.py:248— builder._cleanup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 4 (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.
_prepareFirstFrameShaders (cognitive 17) src/engine/Engine.js:5304— _prepareFirstFrameShaders has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 4, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_validateCompiledPrograms (cognitive 17) src/engine/Engine.js:6083— _validateCompiledPrograms has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: 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.
_warmDeferredWater (cognitive 17) src/engine/Engine.js:7841— _warmDeferredWater has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 7846, 7855). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
_syncCausticWaveUniforms (cognitive 17) src/engine/Engine.js:13438— _syncCausticWaveUniforms has cognitive complexity 17 (threshold 15). Drivers by points: other 12, if/else 3, ternaries 2. 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.
_handlePointerDown (cognitive 17) src/manual/ManualTerrainModeManager.js:866— _handlePointerDown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (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.
packStackUniforms (cognitive 17) src/engine/terrain/noise/noiseStackCodegen.js:161— packStackUniforms has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (4 pts), other 4, ternaries 2 (4 pts), boolean chains 3, loops 2 (nesting depth added 4). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evalStack2D (cognitive 17) src/engine/terrain/noise/noiseStackCodegen.js:256— evalStack2D has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), other 3, 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.
evalStack3D (cognitive 17) src/engine/terrain/noise/noiseStackCodegen.js:285— evalStack3D has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), other 3, 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.
_createContext (cognitive 17) REDACTED:42— _createContext has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, if/else 4, other 3, loops 1. Of this number, 12 points are the body's own statements and 5 belong to 6 function items inside it that branch. 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.
packTerrainSourceUniforms (cognitive 17) src/runtime/TerrainSources.js:62— packTerrainSourceUniforms has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 2 (4 pts), other 3, boolean chains 1, ternaries 1 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
constructor (cognitive 17) src/runtime/TerrainSources.js:92— constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 3, loops 1 (2 pts), ternaries 2, other 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
buildTileAssemblyPlinthGeometry (cognitive 17) src/engine/terrain/BoardPlinth.js:83— buildTileAssemblyPlinthGeometry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 4 (8 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
disposeImportedModelParts (cognitive 17) src/engine/props/ImportedPropModel.js:103— disposeImportedModelParts has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 4 (7 pts), ternaries 1 (2 pts), other 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.
ProceduralTerrainsWindow.DrawAdvancedGeneration (cognitive 16) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/ProceduralTerrainsWindow.cs:207— ProceduralTerrainsWindow.DrawAdvancedGeneration has cognitive complexity 16 (threshold 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.
TerrainGenerator.PostProcess (cognitive 16) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:349— TerrainGenerator.PostProcess has cognitive complexity 16 (threshold 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.
TerrainZipImportService.ValidateEntries (cognitive 16) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainZipImportService.cs:112— TerrainZipImportService.ValidateEntries has cognitive complexity 16 (threshold 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.
SurfaceGraph.compileSurfaceGraph.input (cognitive 16) src/engine/terrain/surface/SurfaceGraph.js:30— SurfaceGraph.compileSurfaceGraph.input has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 1 (nesting depth added 10). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ManualShapeCatalog.normalizeManualShape (cognitive 16) src/manual/ManualShapeCatalog.js:226— ManualShapeCatalog.normalizeManualShape has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 7. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
InfiniteTerrainBatches.commit (cognitive 16) src/engine/terrain/InfiniteTerrainBatches.js:73— InfiniteTerrainBatches.commit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, loops 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.
PlanetWorld._buildFaceNode (cognitive 16) src/engine/terrain/PlanetWorld.js:245— PlanetWorld._buildFaceNode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlanetWorld._uploadPatchBatches (cognitive 16) src/engine/terrain/PlanetWorld.js:611— PlanetWorld._uploadPatchBatches has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PortableProject.decodePortableProject (cognitive 16) src/project/PortableProject.js:21— PortableProject.decodePortableProject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 3, ternaries 2 (3 pts), loops 2 (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.
RealWorldCities.fetchCityMarkers (cognitive 16) src/engine/terrain/RealWorldCities.js:18— RealWorldCities.fetchCityMarkers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, error handling 1 (2 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.
Engine.applyInputFrame (cognitive 16) src/engine/Engine.js:12916— Engine.applyInputFrame has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 4, loops 3, ternaries 1 (2 pts) (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NoiseLayersPanel.NoiseLayersPanel (cognitive 16) src/components/NoiseLayersPanel.jsx:318— NoiseLayersPanel.NoiseLayersPanel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 7 function items inside it that branch (handleStackOutput, handlePreset, handleDragEnd, …). 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.
highlight.highlight (cognitive 16) src/docs/highlight.js:83— highlight.highlight has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (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.
CodeEditor.CodeEditor::onKeyDown (cognitive 16) src/docs/playground/CodeEditor.jsx:40— CodeEditor.CodeEditor::onKeyDown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 1 (2 pts) (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.
SurfaceTextureAtlas.loadImage (cognitive 16) src/engine/terrain/surface/SurfaceTextureAtlas.js:28— SurfaceTextureAtlas.loadImage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerrainEvaluator.sample (cognitive 16) plugins/blender/procedural_terrains/generation.py:678— TerrainEvaluator.sample has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_initManualTerrain::onChange (cognitive 16) src/engine/Engine.js:1024— _initManualTerrain::onChange has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 1 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
setDebugFlag (cognitive 16) src/engine/Engine.js:8601— setDebugFlag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (4 pts), other 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.
_enterStudioMode (cognitive 16) src/engine/Engine.js:10066— _enterStudioMode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 3 (4 pts) (nesting depth added 3). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_upgradePlanetMaterials (cognitive 16) src/engine/Engine.js:10935— _upgradePlanetMaterials has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4, loops 1 (2 pts), error handling 1, other 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update (cognitive 16) src/runtime/FiniteTerrain.js:454— update has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 2 (3 pts), loops 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.
initialize (cognitive 16) src/engine/EngineProxy.js:343— initialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (onEvent, a function literal at line 362, a function literal at line 345, …). 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.
createManualShape (cognitive 16) src/manual/ManualShapeCatalog.js:192— createManualShape has cognitive complexity 16 (threshold 15). Drivers by points: other 13, boolean chains 2, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
normalizePropAsset (cognitive 16) src/engine/props/PropAssetLibrary.js:82— normalizePropAsset has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 6, if/else 2 (3 pts) (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.
resolveWaterBaselineCamera (cognitive 16) src/engine/water/WaterBaseline.js:144— resolveWaterBaselineCamera has cognitive complexity 16 (threshold 15). Drivers by points: other 8, ternaries 3 (6 pts), if/else 2 (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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) plugins/blender/procedural_terrains/generation.py:428— plugins/blender/procedural_terrains/generation.py:428-450 | plugins/blender/procedural_terrains/generation.py:454-470 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:466— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:466-481 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:504-517 — 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 (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:597— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:597-604 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerator.cs:607-621 — 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 (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) plugins/blender/procedural_terrains/operators.py:443— plugins/blender/procedural_terrains/operators.py:443-454 | plugins/blender/procedural_terrains/ui.py:215-223 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:396— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:396-400 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainZipImportService.cs:227-233 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (7 lines × 2) plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411— plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411-417 | plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainZipImportService.cs:212-218 — 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 `plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/TerrainGenerationSceneBuilder.cs:411` 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 (14 lines × 2) plugins/blender/procedural_terrains/operators.py:463— plugins/blender/procedural_terrains/operators.py:463-476 | plugins/blender/procedural_terrains/ui.py:227-240 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/blender/procedural_terrains/operators.py:461` calls `hasattr` and `plugins/blender/procedural_terrains/ui.py:226` 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 (10–11 lines × 2) plugins/blender/procedural_terrains/generation_builder.py:35— plugins/blender/procedural_terrains/generation_builder.py:35-45 | plugins/blender/procedural_terrains/surfaces.py:9-18 — 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) plugins/blender/procedural_terrains/generation.py:374— plugins/blender/procedural_terrains/generation.py:374-378 | plugins/blender/procedural_terrains/generation.py:386-390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) plugins/blender/procedural_terrains/generation.py:406— plugins/blender/procedural_terrains/generation.py:406-411 | plugins/blender/procedural_terrains/generation.py:454-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: Zyfou.ProceduralTerrains — Zyfou.ProceduralTerrains: 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.
Duplication concentrated across 13 sibling directories (41 clone groups) src/engine/destruction/DestructionField.js:4— 41 duplicated blocks under src/ have copies in at least two of the sibling directories admin, auth, components, creator, engine, export (+7 more sibling(s) not listed) — 28 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 41 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 10 sibling directories (21 clone groups) src/engine/boot/FinalFrameBootPipeline.js:22— 21 duplicated blocks under src/engine/ have copies in at least two of the sibling directories boot, destruction, mini, mode, player, props (+4 more sibling(s) not listed) — 14 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (12 clone groups) src/components/panels/QualitySettingsContent.jsx:374— 12 duplicated blocks under src/components/ have copies in at least two of the sibling directories manual, nodes, panels, support, ui — 10 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) src/engine/boot/FinalFrameBootPipeline.js:22— src/engine/boot/FinalFrameBootPipeline.js:22 · src/engine/mode/ModeTransitionCoordinator.js:11 — the two spans are one implementation copied and then locally edited — 971 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 (132 matched lines × 2 locations) · ×1
Duplicated block with local edits (132 matched lines × 2 locations) src/components/ui/LeftToolbar.jsx:44— src/components/ui/LeftToolbar.jsx:44 · src/components/ui/SideDrawer.jsx:41 — the two spans are one implementation copied and then locally edited — 811 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 (110 matched lines × 2 locations) · ×1
Duplicated block with local edits (110 matched lines × 2 locations) src/engine/terrain/MergeQuadtree.js:83— src/engine/terrain/MergeQuadtree.js:83 · src/engine/terrain/TerrainBoard.js:630 — the two spans are one implementation copied and then locally edited — 1069 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 (103 matched lines × 2 locations) · ×1
Duplicated block with local edits (103 matched lines × 2 locations) src/engine/sky/CloudSlabLayer.js:479— src/engine/sky/CloudSlabLayer.js:479 · src/engine/sky/PlanetCloudLayer.js:325 — the two spans are one implementation copied and then locally edited — 869 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 (99 matched lines × 2 locations) · ×1
Duplicated block with local edits (99 matched lines × 2 locations) src/components/ui/CloudPanel.jsx:159— src/components/ui/CloudPanel.jsx:159 · src/components/ui/CloudPanel.jsx:290 — the two spans are one implementation copied and then locally edited — 597 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 (81 matched lines × 2 locations) · ×1
Duplicated block with local edits (81 matched lines × 2 locations) src/engine/sky/realistic/RealisticCloudLayers.js:140— src/engine/sky/realistic/RealisticCloudLayers.js:140 · src/engine/sky/realistic/RealisticCloudLayers.js:342 — the two spans are one implementation copied and then locally edited — 742 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 (74 matched lines × 2 locations) · ×1
Duplicated block with local edits (74 matched lines × 2 locations) src/engine/sky/CloudSlabLayer.js:344— src/engine/sky/CloudSlabLayer.js:344 · src/engine/sky/PlanetCloudLayer.js:235 — the two spans are one implementation copied and then locally edited — 529 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.
Wholesale file copy (57 identical lines × 2 files) src/engine/sky/CloudSlabShader.js:1— src/engine/sky/CloudSlabShader.js:1 · src/engine/sky/CloudVolumeShader.js:1 — these 2 files are line-for-line copies of one another — 57 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) src/engine/destruction/DestructionField.js:4— src/engine/destruction/DestructionField.js:4 · src/manual/ManualSurfacePaintField.js:4 — the two spans are one implementation copied and then locally edited — 278 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 (27 matched lines × 2 locations) · ×1
Duplicated block with local edits (27 matched lines × 2 locations) tools/perf-harness/experiments/mini-props-ui.mjs:18— tools/perf-harness/experiments/mini-props-ui.mjs:18 · tools/perf-harness/experiments/mini-ui-smoke.mjs:17 — the two spans are one implementation copied and then locally edited — 346 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 (26 lines × 2 locations) REDACTED:338— REDACTED:338 · REDACTED:371 — 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.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) tools/perf-harness/experiments/cloud-loops.mjs:7— tools/perf-harness/experiments/cloud-loops.mjs:7 · tools/perf-harness/experiments/water-loop.mjs:8 — the two spans are one implementation copied and then locally edited — 308 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 (23 matched lines × 2 locations) · ×1
Duplicated block with local edits (23 matched lines × 2 locations) tools/perf-harness/experiments/planet-climate-ablation.mjs:2— tools/perf-harness/experiments/planet-climate-ablation.mjs:2 · tools/perf-harness/experiments/shade-ablation.mjs:3 — the two spans are one implementation copied and then locally edited — 293 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) src/App.jsx:1698— src/App.jsx:1698 · src/App.jsx:1728 — 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 (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) src/engine/sky/CloudSlabLayer.js:174— src/engine/sky/CloudSlabLayer.js:174 · src/engine/sky/realistic/RealisticCloudLayers.js:184 — the two spans are one implementation copied and then locally edited — 217 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 (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) src/engine/sky/InfiniteCloudLayer.js:13— src/engine/sky/InfiniteCloudLayer.js:13 · src/engine/sky/realistic/RealisticCloudLayers.js:309 — the two spans are one implementation copied and then locally edited — 229 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 (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) src/runtime/resources/TerrainCompute.js:23— src/runtime/resources/TerrainCompute.js:23 · src/runtime/resources/TerrainSurfaceWorker.js:12 — the two spans are one implementation copied and then locally edited — 129 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 (18 lines × 2 locations) src/components/TouchControls.jsx:52— src/components/TouchControls.jsx:52 · src/components/TouchControls.jsx:112 — 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 (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) src/engine/terrain/surface/SurfaceAtlasBridge.js:103— src/engine/terrain/surface/SurfaceAtlasBridge.js:103 · src/engine/terrain/surface/SurfaceAtlasBridge.js:123 — the two spans are one implementation copied and then locally edited — 106 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.
Complex function (anonymous) (cyclomatic 225, cognitive 75) src/App.jsx:1988— (anonymous) has cyclomatic complexity 225 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 build (cyclomatic 159, cognitive 301) src/engine/terrain/TerrainExportBuilder.js:201— build has cyclomatic complexity 159 and cognitive complexity 301; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 App (cyclomatic 115, cognitive 88) src/App.jsx:147— App has cyclomatic complexity 115 and cognitive complexity 88; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _rebuildStackMaterialsAsync (cyclomatic 100, cognitive 133) src/engine/Engine.js:4059— _rebuildStackMaterialsAsync has cyclomatic complexity 100 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 validateRuntimeTerrainDocument (cyclomatic 94, cognitive 108) src/export/runtime/RuntimeTerrainValidator.js:18— validateRuntimeTerrainDocument has cyclomatic complexity 94 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 _tickStudio (cyclomatic 78, cognitive 89) src/engine/Engine.js:13534— _tickStudio has cyclomatic complexity 78 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PerformanceOverlay (cyclomatic 73, cognitive 68) src/components/perf/PerformanceOverlay.jsx:65— PerformanceOverlay has cyclomatic complexity 73 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 WaterPanelInner (cyclomatic 70, cognitive 62) src/components/ui/WaterPanel.jsx:244— WaterPanelInner has cyclomatic complexity 70 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 loadSeedJSON (cyclomatic 68, cognitive 81) src/engine/Engine.js:11742— loadSeedJSON has cyclomatic complexity 68 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Landing (cyclomatic 67, cognitive 64) src/landing/Landing.jsx:120— Landing has cyclomatic complexity 67 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 getPerfDiagnostics (cyclomatic 66, cognitive 73) src/engine/Engine.js:13915— getPerfDiagnostics has cyclomatic complexity 66 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 restoreState (cyclomatic 58, cognitive 73) src/engine/Engine.js:12049— restoreState has cyclomatic complexity 58 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 computeWarnings (cyclomatic 57, cognitive 91) src/components/perf/warnings.js:23— computeWarnings has cyclomatic complexity 57 and cognitive complexity 91; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _tickBody (cyclomatic 57, cognitive 72) src/engine/Engine.js:13177— _tickBody has cyclomatic complexity 57 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 compileSurfaceGraph (cyclomatic 54, cognitive 75) src/engine/terrain/surface/SurfaceGraph.js:23— compileSurfaceGraph has cyclomatic complexity 54 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _compileShaderBenchmarkCandidate (cyclomatic 53, cognitive 54) src/engine/Engine.js:6937— _compileShaderBenchmarkCandidate has cyclomatic complexity 53 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 applyMiniWaterLook (cyclomatic 52, cognitive 64) src/engine/mini/MiniWaterMaterial.js:806— applyMiniWaterLook has cyclomatic complexity 52 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function dispose (cyclomatic 52, cognitive 54) src/engine/Engine.js:14100— dispose has cyclomatic complexity 52 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _updateFlat (cyclomatic 51, cognitive 62) src/engine/props/ProceduralPropsManager.js:319— _updateFlat has cyclomatic complexity 51 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 sanitizePerfSettings (cyclomatic 49, cognitive 50) src/engine/render/PerformanceSettings.js:265— sanitizePerfSettings has cyclomatic complexity 49 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ManualTerrainPanel (cyclomatic 49, cognitive 46) src/components/manual/ManualTerrainPanel.jsx:188— ManualTerrainPanel has cyclomatic complexity 49 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _compileMaterialVariants (cyclomatic 48, cognitive 53) src/engine/Engine.js:5832— _compileMaterialVariants has cyclomatic complexity 48 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _warmDeferredWaterImpl (cyclomatic 48, cognitive 49) src/engine/Engine.js:8044— _warmDeferredWaterImpl has cyclomatic complexity 48 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 _setDebugFreeCam (cyclomatic 47, cognitive 70) src/engine/Engine.js:8633— _setDebugFreeCam has cyclomatic complexity 47 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyRealisticWaterUniforms (cyclomatic 47, cognitive 46) src/engine/water/RealisticWaterMaterial.js:1210— applyRealisticWaterUniforms has cyclomatic complexity 47 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 applyParams (cyclomatic 46, cognitive 46) src/engine/sky/CloudSlabLayer.js:186— applyParams has cyclomatic complexity 46 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 NodeWorkspace (cyclomatic 44, cognitive 42) REDACTED:460— NodeWorkspace has cyclomatic complexity 44 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 setParam (cyclomatic 41, cognitive 56) src/engine/Engine.js:2776— setParam has cyclomatic complexity 41 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 update (cyclomatic 40, cognitive 70) src/engine/sky/PlanetCloudChunks.js:351— update has cyclomatic complexity 40 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateExport (cyclomatic 40, cognitive 40) src/export/ExportValidator.js:7— validateExport has cyclomatic complexity 40 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createTerrainCodeDocument (cyclomatic 40, cognitive 38) src/export/TerrainCodeExporter.js:17— createTerrainCodeDocument has cyclomatic complexity 40 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _sceneRevisionKey (cyclomatic 39, cognitive 38) src/engine/Engine.js:5465— _sceneRevisionKey has cyclomatic complexity 39 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 TopBar (cyclomatic 39, cognitive 37) src/components/TopBar.jsx:44— TopBar has cyclomatic complexity 39 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _completeBootIfQualityReady (cyclomatic 39, cognitive 37) src/engine/Engine.js:7359— _completeBootIfQualityReady has cyclomatic complexity 39 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _setWorldModeImmediate (cyclomatic 38, cognitive 42) src/engine/Engine.js:9681— _setWorldModeImmediate has cyclomatic complexity 38 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _warmupPlanetShaders (cyclomatic 38, cognitive 41) src/engine/Engine.js:10838— _warmupPlanetShaders has cyclomatic complexity 38 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 newProject (cyclomatic 37, cognitive 39) src/engine/Engine.js:2952— newProject has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _ensureTerrainShaderVariantAsync (cyclomatic 37, cognitive 38) src/engine/Engine.js:11251— _ensureTerrainShaderVariantAsync has cyclomatic complexity 37 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 applyParams (cyclomatic 37, cognitive 36) src/engine/sky/PlanetCloudLayer.js:128— applyParams has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 erode (cyclomatic 36, cognitive 78) src/engine/terrain/erosion/erosionSim.js:85— erode has cyclomatic complexity 36 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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.
src/engine/Engine.js: 13464 lines of code src/engine/Engine.js:1— src/engine/Engine.js has 13464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/App.jsx: 2916 lines of code src/App.jsx:1— src/App.jsx has 2916 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· src/engine/terrain/TerrainMaterial.js · ×1
src/engine/terrain/TerrainMaterial.js: 1600 lines of code src/engine/terrain/TerrainMaterial.js:1— src/engine/terrain/TerrainMaterial.js has 1600 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· src/engine/water/RealisticWaterMaterial.js · ×1
src/engine/water/RealisticWaterMaterial.js: 1220 lines of code src/engine/water/RealisticWaterMaterial.js:1— src/engine/water/RealisticWaterMaterial.js has 1220 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/engine/terrain/graph/GraphCompiler.js · ×1
src/engine/terrain/graph/GraphCompiler.js: 1147 lines of code src/engine/terrain/graph/GraphCompiler.js:1— src/engine/terrain/graph/GraphCompiler.js has 1147 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· src/manual/ManualTerrainModeManager.js · ×1
src/manual/ManualTerrainModeManager.js: 1138 lines of code src/manual/ManualTerrainModeManager.js:1— src/manual/ManualTerrainModeManager.js has 1138 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· src/engine/water/WaterSystem.js · ×1
src/engine/water/WaterSystem.js: 1126 lines of code src/engine/water/WaterSystem.js:1— src/engine/water/WaterSystem.js has 1126 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/panels/index.jsx · ×1
src/components/panels/index.jsx: 1092 lines of code src/components/panels/index.jsx:1— src/components/panels/index.jsx has 1092 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: 1015 lines of code REDACTED:1— REDACTED has 1015 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· src/engine/terrain/terrainGLSL.js · ×1
src/engine/terrain/terrainGLSL.js: 946 lines of code src/engine/terrain/terrainGLSL.js:1— src/engine/terrain/terrainGLSL.js has 946 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· src/engine/props/ProceduralPropsManager.js · ×1
src/engine/props/ProceduralPropsManager.js: 935 lines of code src/engine/props/ProceduralPropsManager.js:1— src/engine/props/ProceduralPropsManager.js has 935 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· src/engine/mini/MiniWaterMaterial.js · ×1
src/engine/mini/MiniWaterMaterial.js: 895 lines of code src/engine/mini/MiniWaterMaterial.js:1— src/engine/mini/MiniWaterMaterial.js has 895 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· src/engine/terrain/TerrainExportBuilder.js · ×1
src/engine/terrain/TerrainExportBuilder.js: 870 lines of code src/engine/terrain/TerrainExportBuilder.js:1— src/engine/terrain/TerrainExportBuilder.js has 870 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· src/components/manual/ManualTerrainPanel.jsx · ×1
src/components/manual/ManualTerrainPanel.jsx: 867 lines of code src/components/manual/ManualTerrainPanel.jsx:1— src/components/manual/ManualTerrainPanel.jsx has 867 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· src/components/ui/WaterPanel.jsx · ×1
src/components/ui/WaterPanel.jsx: 820 lines of code src/components/ui/WaterPanel.jsx:1— src/components/ui/WaterPanel.jsx has 820 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· src/engine/terrain/TerrainBoard.js · ×1
src/engine/terrain/TerrainBoard.js: 810 lines of code src/engine/terrain/TerrainBoard.js:1— src/engine/terrain/TerrainBoard.js has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/landing/Landing.jsx: 781 lines of code src/landing/Landing.jsx:1— src/landing/Landing.jsx has 781 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· src/engine/mini/MiniTerrainSettings.js · ×1
src/engine/mini/MiniTerrainSettings.js: 702 lines of code src/engine/mini/MiniTerrainSettings.js:1— src/engine/mini/MiniTerrainSettings.js has 702 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· src/engine/terrain/PlanetWorld.js · ×1
src/engine/terrain/PlanetWorld.js: 670 lines of code src/engine/terrain/PlanetWorld.js:1— src/engine/terrain/PlanetWorld.js has 670 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· src/engine/terrain/RealWorldHeightmap.js · ×1
src/engine/terrain/RealWorldHeightmap.js: 648 lines of code src/engine/terrain/RealWorldHeightmap.js:1— src/engine/terrain/RealWorldHeightmap.js has 648 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· src/engine/sky/CloudSlabLayer.js · ×1
src/engine/sky/CloudSlabLayer.js: 622 lines of code src/engine/sky/CloudSlabLayer.js:1— src/engine/sky/CloudSlabLayer.js has 622 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· src/engine/sky/realistic/realisticCloudGLSL.js · ×1
src/engine/sky/realistic/realisticCloudGLSL.js: 619 lines of code src/engine/sky/realistic/realisticCloudGLSL.js:1— src/engine/sky/realistic/realisticCloudGLSL.js has 619 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· tools/perf-harness/harness-entry.js · ×1
tools/perf-harness/harness-entry.js: 593 lines of code tools/perf-harness/harness-entry.js:1— tools/perf-harness/harness-entry.js has 593 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: 587 lines of code REDACTED:1— REDACTED has 587 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· src/engine/mini/MiniTerrainController.js · ×1
src/engine/mini/MiniTerrainController.js: 576 lines of code src/engine/mini/MiniTerrainController.js:1— src/engine/mini/MiniTerrainController.js has 576 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· src/engine/render/VisualPostProcess.js · ×1
src/engine/render/VisualPostProcess.js: 572 lines of code src/engine/render/VisualPostProcess.js:1— src/engine/render/VisualPostProcess.js has 572 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· src/engine/terrain/PlanetMaterial.js · ×1
src/engine/terrain/PlanetMaterial.js: 568 lines of code src/engine/terrain/PlanetMaterial.js:1— src/engine/terrain/PlanetMaterial.js has 568 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· src/manual/ManualTerrainField.js · ×1
src/manual/ManualTerrainField.js: 554 lines of code src/manual/ManualTerrainField.js:1— src/manual/ManualTerrainField.js has 554 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· src/runtime/FiniteTerrain.js · ×1
src/runtime/FiniteTerrain.js: 544 lines of code src/runtime/FiniteTerrain.js:1— src/runtime/FiniteTerrain.js has 544 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· src/components/panels/QualitySettingsContent.jsx · ×1
src/components/panels/QualitySettingsContent.jsx: 538 lines of code src/components/panels/QualitySettingsContent.jsx:1— src/components/panels/QualitySettingsContent.jsx has 538 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· src/components/ui/ImportMapsContent.jsx · ×1
src/components/ui/ImportMapsContent.jsx: 514 lines of code src/components/ui/ImportMapsContent.jsx:1— src/components/ui/ImportMapsContent.jsx has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/engine/terrain/surface/terrainSurfaceTextureGLSL.js · ×1
src/engine/terrain/surface/terrainSurfaceTextureGLSL.js: 509 lines of code src/engine/terrain/surface/terrainSurfaceTextureGLSL.js:1— src/engine/terrain/surface/terrainSurfaceTextureGLSL.js has 509 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· src/engine/sky/PlanetCloudChunks.js · ×1
src/engine/sky/PlanetCloudChunks.js: 504 lines of code src/engine/sky/PlanetCloudChunks.js:1— src/engine/sky/PlanetCloudChunks.js has 504 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· src/engine/terrain/noise/noiseTypes.js · ×1
src/engine/terrain/noise/noiseTypes.js: 504 lines of code src/engine/terrain/noise/noiseTypes.js:1— src/engine/terrain/noise/noiseTypes.js has 504 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· src/engine/terrain/graph/GraphRegistry.js · ×1
src/engine/terrain/graph/GraphRegistry.js: 503 lines of code src/engine/terrain/graph/GraphRegistry.js:1— src/engine/terrain/graph/GraphRegistry.js has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/engine/terrain/InfiniteWorld.js · ×1
src/engine/terrain/InfiniteWorld.js: 500 lines of code src/engine/terrain/InfiniteWorld.js:1— src/engine/terrain/InfiniteWorld.js has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/engine/EngineProxy.js: 480 lines of code src/engine/EngineProxy.js:1— src/engine/EngineProxy.js has 480 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· src/components/ui/RealWorldMapPicker.jsx · ×1
src/components/ui/RealWorldMapPicker.jsx: 478 lines of code src/components/ui/RealWorldMapPicker.jsx:1— src/components/ui/RealWorldMapPicker.jsx has 478 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· src/engine/destruction/DestructionField.js · ×1
src/engine/destruction/DestructionField.js: 473 lines of code src/engine/destruction/DestructionField.js:1— src/engine/destruction/DestructionField.js has 473 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· src/components/NoiseLayersPanel.jsx · ×1
src/components/NoiseLayersPanel.jsx: 471 lines of code src/components/NoiseLayersPanel.jsx:1— src/components/NoiseLayersPanel.jsx has 471 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~626 LoC) tools/perf-harness/harness-entry.js— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~214 LoC) src/project/CloudProjectsPanel.jsx— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~182 LoC) tools/perf-harness/experiments/mini-light-cost.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~132 LoC) tools/check-real-elevation-browser.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~119 LoC) tools/worker-render-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~112 LoC) tools/terrain-compile-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~111 LoC) tools/background-surface-browser-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~108 LoC) tools/check-terrain-playground-browser.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~95 LoC) tools/check-real-terrain-appearance.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~90 LoC) tools/check-terrain-snippet-browser.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~89 LoC) tools/perf-harness/experiments/mini-terrain.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~88 LoC) tools/perf-harness/experiments/mini-props-instant.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~80 LoC) tools/perf-harness/experiments/mini-circle.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~75 LoC) tools/imported-pbr-browser-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) tools/perf-harness/experiments/water-zfight.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~71 LoC) tools/perf-harness/experiments/planet-pop-debug.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~70 LoC) tools/perf-harness/experiments/deferred-proto.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~64 LoC) tools/perf-harness/cache-probe.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~62 LoC) tools/perf-harness/experiments/motion-frames.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~57 LoC) tools/perf-harness/experiments/stylized-water.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~55 LoC) tools/perf-harness/experiments/mini-grid-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~54 LoC) tools/check-terrain-docs-browser.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~53 LoC) tools/surface-pack-ui-check.mjs— no import path from any entry point (88 application, 18 tooling, 138 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'motion' package.json:48— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Duplicated predicate src/engine/terrain/BoardPlinth.js:71— `!Number.isFinite(cx) || !Number.isFinite(cz)` appears character-identically in 2 files — src/engine/terrain/BoardPlinth.js, src/engine/terrain/TerrainBoard.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 src/engine/terrain/PlanetHeightBaker.js:279— `!handle || handle.serial !== this._programSerial` appears character-identically in 2 files — src/engine/terrain/PlanetHeightBaker.js, src/engine/terrain/TerrainHeightBaker.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 api/src/admin-utils.js:5— `!input || typeof input !== 'object' || Array.isArray(input)` appears character-identically in 2 files — api/src/admin-utils.js, src/engine/terrain/RealWorldSource.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 src/engine/FPSControls.js:103— `!this._locked && e.pointerType !== 'touch'` appears character-identically in 3 files — src/engine/FPSControls.js, src/engine/player/PlaneController.js, src/engine/player/PlanetController.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 src/engine/terrain/InfiniteWorld.js:266— `!this._lodRebuildQueue.length || !this._targetSegments` appears character-identically in 3 files — src/engine/terrain/InfiniteWorld.js, src/engine/terrain/PlanetWorld.js, src/engine/terrain/TerrainBoard.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 src/engine/boot/FinalFrameBootPipeline.js:31— `!value || typeof value !== 'object' || Object.isFrozen(value)` appears character-identically in 2 files — src/engine/boot/FinalFrameBootPipeline.js, src/engine/mode/ModeTransitionCoordinator.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 src/engine/FPSControls.js:133— `Math.abs(lookX) < 0.02 && Math.abs(lookY) < 0.02` appears character-identically in 2 files — src/engine/FPSControls.js, src/engine/player/PlanetController.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 src/manual/ManualPropPaintField.js:10— `Math.abs(originA.x - originB.x) <= BOUNDS_EPSILON && Math.abs(originA.z - originB.z) <= BOUNDS_EPSILON && Math.abs(spanA.x - spanB.x) <= BOU…` appears character-identically in 3 files — src/manual/ManualPropPaintField.js, src/manual/ManualSurfacePaintField.js, src/manual/ManualTerrainField.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 src/engine/FPSControls.js:85— `Math.hypot(moveX, moveY) > 0.02 || Math.hypot(lookX, lookY) > 0.02` appears character-identically in 3 files — src/engine/FPSControls.js, src/engine/player/PlaneController.js, src/engine/player/PlanetController.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 src/engine/sky/CloudSlabLayer.js:651— `baseSize || renderer.getDrawingBufferSize(this._depthSize)` appears character-identically in 3 files — src/engine/sky/CloudSlabLayer.js, src/engine/sky/PlanetCloudChunks.js, src/engine/sky/PlanetCloudLayer.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 src/engine/props/ProceduralPropsManager.js:509— `desc.id === 'broadleaf' || desc.id === 'conifer'` appears character-identically in 2 files — src/engine/props/ProceduralPropsManager.js, src/engine/props/PropPlacement.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 src/engine/EditorControls.js:291— `e.pointerType === 'touch' && this._touches.has(e.pointerId)` appears character-identically in 2 files — src/engine/EditorControls.js, src/engine/PlanetOrbitControls.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 src/components/MinimapOverlay.jsx:106— `event.defaultPrevented || event.repeat || event.isComposing` appears character-identically in 2 files — src/components/MinimapOverlay.jsx, src/components/TopBar.jsx. 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 src/engine/terrain/graph/GraphCompiler.js:1150— `getGraphNodeDefinition(node.type)?.colorUniformSlots?.(node) || 0` appears character-identically in 2 files — src/engine/terrain/graph/GraphCompiler.js, src/engine/terrain/graph/GraphDocument.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 src/engine/terrain/graph/GraphCompiler.js:1148— `getGraphNodeDefinition(node.type)?.uniformSlots?.(node) || 0` appears character-identically in 2 files — src/engine/terrain/graph/GraphCompiler.js, src/engine/terrain/graph/GraphDocument.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 src/engine/render/GpuTier.js:43— `gl.getParameter(dbg.UNMASKED_RENDERER_WEBGL) || ''` appears character-identically in 2 files — src/engine/render/GpuTier.js, src/engine/render/RendererCapabilities.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 src/engine/terrain/InfiniteTerrainClipmap.js:168— `handle?.material && !handle.published && handle.material !== this.material` appears character-identically in 2 files — src/engine/terrain/InfiniteTerrainClipmap.js, src/engine/terrain/TerrainHeightBaker.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 src/engine/terrain/MergeQuadtree.js:54— `mergeDistance !== undefined && Number.isFinite(+mergeDistance)` appears character-identically in 2 files — src/engine/terrain/MergeQuadtree.js, src/engine/terrain/PlanetWorld.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 src/engine/terrain/graph/GraphDocument.js:70— `node && typeof node.id === 'string' && typeof node.type === 'string'` appears character-identically in 2 files — src/engine/terrain/graph/GraphDocument.js, src/export/runtime/RuntimeTerrainDocument.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 src/engine/sky/CloudSlabLayer.js:457— `occupancyRatio > 0 && occupancyRatio < 0.78` appears character-identically in 2 files — src/engine/sky/CloudSlabLayer.js, src/engine/sky/PlanetCloudLayer.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 tools/perf-harness/experiments/mini-terrain.mjs:83— `p.diagnostics && !p.diagnostics.runnable` appears character-identically in 2 files — tools/perf-harness/experiments/mini-terrain.mjs, tools/perf-harness/experiments/terrain-detail.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/perf-harness/experiments/depth-prepass.mjs:13— `process.env.VIEW || 'close,grazing,overview'` appears character-identically in 2 files — tools/perf-harness/experiments/depth-prepass.mjs, tools/perf-harness/experiments/morph-sensitivity.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/manual/ManualPropPaintField.js:118— `px < 0 || px > this.resolution - 1 || py < 0 || py > this.resolution - 1` appears character-identically in 2 files — src/manual/ManualPropPaintField.js, src/manual/ManualSurfacePaintField.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 src/engine/sky/CloudSlabLayer.js:282— `q.steps !== this._steps || q.lightSteps !== this._lightSteps || q.octaves !== this._octaves || q.detailOctaves !== this._detailOctaves || q.…` appears character-identically in 2 files — src/engine/sky/CloudSlabLayer.js, src/engine/sky/PlanetCloudChunks.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 src/manual/ManualPropPaintField.js:42— `resolution || resolutionForTier(gpuTier)` appears character-identically in 4 files — src/manual/ManualPropPaintField.js, src/manual/ManualSurfacePaintField.js, src/manual/ManualTerrainField.js, src/paint/PaintLayerManager.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.
Silent fallback default in catch api/src/auth-utils.js:63— `verifyPassword` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch electron/desktop-state.cjs:11— `readState` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/project/ProjectStore.js:50— `fallbackRead` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/project/ProjectStore.js:55— `fallbackSyncRead` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/i18n/language.js:10— `readLanguage` swallows every exception into `return 'en'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/engine/terrain/surface/SurfaceLibrary.js:121— `readSelectionStore` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/engine/render/RendererCapabilities.js:99— `detectRendererCapabilities` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/engine/render/GpuTier.js:45— `readRendererString` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/hooks/useSupportPrompt.js:34— `readMajorVersions` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch tools/verify-desktop-release.cjs:10— `dotenvValue` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
redundant comment src/components/NoiseLayersPanel.jsx:352— "structural changes: blendMode, enabled, masks" repeats the code it sits on: 5 of its 6 words (structural, blend, mode, enabled, masks) are already in `const structural = 'blendMode' in patch || 'enabled' in patch || 'masks' in patch;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/engine/Engine.js:9916— "Create FPS controls" repeats the code it sits on: 3 of its 3 words (create, fps, controls) are already in `this.fpsControls = new FPSControls(this.camera, this.canvas);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/engine/Engine.js:9930— "Create fog manager" repeats the code it sits on: 3 of its 3 words (create, fog, manager) are already in `this.fogManager = new FogManager(this.uniforms, this.scene);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/engine/Engine.js:9935— "Apply time of day" repeats the code it sits on: 3 of its 3 words (apply, time, day) are already in `this._applyTimeOfDay();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Documentation: no build, run or usage example plugins/unity/Packages/com.zyfou.procedural-terrains/README.md:1— `com.zyfou.procedural-terrains` is a published package (`package.json` without `"private": true`) and neither `plugins/unity/Packages/com.zyfou.procedural-terrains/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.
D21 · Naming Consistency· `blendGlslStmt` spells `Glsl` where 62 names in the project spell it `GLSL` · ×1
`blendGlslStmt` spells `Glsl` where 62 names in the project spell it `GLSL` src/engine/terrain/noise/blendModes.js:61— 62 of 64 names in project terrain-studio spell the token `GLSL` (62 of 64; unit: names in project terrain-studio containing `GLSL`). Peers: Engine._stackGLSL (src/engine/Engine.js:331); InfiniteTerrainClipmap.buildFragment(heightGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:21); InfiniteTerrainClipmap._makeProgramMaterial(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:115); InfiniteTerrainClipmap.prepareProgram(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:130); InfiniteTerrainClipmap.setProgram(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:173). Rename to `blendGLSLStmt`. [rule N6]
D21 · Naming Consistency· `evalMaskGlsl` spells `Glsl` where 62 names in the project spell it `GLSL` · ×1
`evalMaskGlsl` spells `Glsl` where 62 names in the project spell it `GLSL` src/engine/terrain/noise/masks.js:67— 62 of 64 names in project terrain-studio spell the token `GLSL` (62 of 64; unit: names in project terrain-studio containing `GLSL`). Peers: Engine._stackGLSL (src/engine/Engine.js:331); InfiniteTerrainClipmap.buildFragment(heightGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:21); InfiniteTerrainClipmap._makeProgramMaterial(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:115); InfiniteTerrainClipmap.prepareProgram(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:130); InfiniteTerrainClipmap.setProgram(stackGLSL) (src/engine/terrain/InfiniteTerrainClipmap.js:173). Rename to `evalMaskGLSL`. [rule N6]
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.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to as a CI step. What was searched, so you can tell an absence from a miss: the 3 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.
No dependency-update automation package.json:43— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Silent fallback default on unknown code plugins/unity/Packages/com.zyfou.procedural-terrains/Editor/RuntimeTerrainDocumentJson.cs:380— `ParseProjectMode` maps every unrecognised code to `TerrainProjectMode.Unknown`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
doc comments repeat the names src/engine/Engine.js:11463— 0 of 99 documented parameters and 1 of 406 summaries in `terrain-studio` only repeat the member or parameter name (e.g. "Set time of day (0..1)." for `setTimeOfDay`). 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 2 file(s) — `packages/procedural-terrains/types/index.d.ts`, `packages/procedural-terrains/types/render.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1eadf-8996-7067-85f4-a03fd7f3d654 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 98 · Warnings: 1071 · Recommendations: 65 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 18:58 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.