Public report of Leonxlnx/taste-skill, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 15:38 UTC · Survey ID cd_ab1fb869de684dbcb7c21063655004f0
Leonxlnx/taste-skill
Measured 13 November 2026, 15:37 UTC, at code version f6b7657
Code coverage is not measured: Suite not runnable in-image.
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 47,908 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 30
Findings by how serious they are
5 critical925 serious57 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 15:37 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
52of 52 dimensions measured by tools.
981of 987 findings point to an exact file and line, so you can open each one in the code. The other 6 concern the repository as a whole, such as missing documentation.
52dimensions across 7 lenses, read from 47,908 lines of product code in 1 project.
Leonxlnx/taste-skill falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 37 out of 100 and is rated Weak, and two of its five critical findings are security problems in the build pipeline.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step is fixing the eight files that change often and are hard to read, worth about 4 points. Adopting a logging library would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 42.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One control can't be used without a mouse, and one form field can't be read by a screen reader. Pinning each tool to an exact version, making the controls work with a keyboard and labelling the form fields would close these risks. The label or group of fields with no name needs connecting to its fields or naming.
The product code is 47,908 lines, about €41,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 37 to about 42.
Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 897 findings
These 897 critical or serious findings weren't in the previous survey, on 24 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 169 findings
These 169 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one. The first 100 are listed here.
€14,000 to €68,000, for 227 to 720 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 47,908 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with consistency.mjs, photos.mjs, layout-check.js.
Adopt pino (or winston) and log at meaningful points in the services you run.
Raises the score by about 4 points · Medium effort · Observability
3
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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 €41,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 30 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for high effort, because it clears the 8 Churn × Complexity Hotspots 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 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 98,814 lines over the last 90 days, which is about 400,746 lines a year. At that pace, the extra work comes to an estimated 83.5 to 500.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
At a glance — Code Health · 32% · Weak · gated by D1, D2, R1, R2, X3 ·
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
3
High / Critical
Roadmap
Top priorities: Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with consistency.mjs, photos.mjs, layout-check.js; Adopt pino (or winston) and log at meaningful points in the services you run; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with consistency.mjs, photos.mjs, layout-check.js.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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 — 5
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 — 925
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 — 57
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.6, 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 — 52 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, 981 of 987 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.
D4 Code Duplication — 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 language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 1% of production LoC (273 test / 47,908 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
D14 License Compliance — 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 — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
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 (27 contributor(s) across 321 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 26 hold 0.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.
D20 ADR Quality — 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 ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `.codex-plugin/plugin.json`.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D26 Project Cohesion — 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. `(repository root)` (44893 LoC, 167 module-visible types across 116 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
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. `skills/taste-skill/scripts/copy-lint.mjs`, `skills/taste-skill/scripts/moments.mjs` 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.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 170 commits in the last 90 days, yet 100 of 108 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
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. 46 further occurrence(s) are not listed individually; the score already reflects all 86.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 145 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
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. 83 further occurrence(s) are not listed individually; the score already reflects all 123.
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. 355 further occurrence(s) are not listed individually; the score already reflects all 395.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 189 further occurrence(s) are not listed individually; the score already reflects all 229.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
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").
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.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
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.
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.
358 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was consistency.runWidth at 899. 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 Diagram.bindCard at 16 — they are counted neither in the figure above nor in this dimension's score.
+ 181 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 26 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with consistency.runWidth (cyclomatic 899), consistency.lib::extras (cyclomatic 336), consistency.lib::pageInfo (cyclomatic 287). — 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 26 together lifts Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 217 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 46 bodies over 60 down to 60 or less in Cognitive Complexity — start with consistency.runWidth (cognitive 1499), consistency.lib::extras (cognitive 466), consistency.lib::pageInfo (cognitive 382). — 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 46 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.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 12 FileTooLong finding(s) in God Classes — start with effect.js (2), consistency.mjs, print3d.js. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 7 FunctionTooLong finding(s) in God Classes — start with effect.js (2), photo.js, photos.mjs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether 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: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with consistency.mjs, photos.mjs, layout-check.js. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d15_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.
31 % 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
3 finding(s): 0 critical, 2 high, 1 medium, 0 low. 2 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 8 file(s) — `install.sh` (line 120), `skills/taste-skill/assets/diagrams/diagram.js`, `skills/taste-skill/assets/icons/demo.html`, `skills/taste-skill/assets/objects/_print-core/print3d.js`, `skills/taste-skill/scripts/copy-lint.mjs` (line 85), … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
No action in Static Analysis (SAST) — all 2 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 (2 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 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.
No strong hidden change-coupling between production files.
✓ On the Gold path — maintain.
Detailed fixes: d35_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels7.8 / 10Strong✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — skills/taste-skill/assets/backgrounds/demo.html:144
This <label> has no for 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 for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — skills/taste-skill/scripts/fx-gallery.template.html:375
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — skills/taste-skill/assets/backgrounds/check.html:2, skills/taste-skill/assets/icons/demo.html:2, skills/taste-skill/assets/moments/gallery.html:1, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×36) — skills/taste-skill/assets/backgrounds/demo.html:171, skills/taste-skill/assets/backgrounds/demo.html:208, skills/taste-skill/assets/backgrounds/demo.html:270, …
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 script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — skills/taste-skill/assets/components/index.html:137
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.
`.toast` moves (`transition: opacity .2s ease, transform .2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — skills/taste-skill/assets/effects/gallery.html:143, skills/taste-skill/scripts/fx-gallery.template.html:284
`.l-assign .ptr` moves (`animation: assign-ptr var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:76
`.l-assign .who` moves (`animation: assign-who var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:81
`.l-late .st-late` moves (`animation: late-on var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:89
`.l-late.toast` moves (`animation: late-toast var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:93
`.l-cycle .bar i` moves (`animation: cycle-fill var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:100
`.l-cycle.done` moves (`animation: cycle-done var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:102
`.mover` moves (`animation: move-card var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/motion/demo.html:124
`.seg button[aria-pressed="true"]` sets color: #17181b on background-color: #111113 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/objects/_print-core/cards.html:26
`.swatch` moves (`transition: transform 160ms ease, border-color 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/objects/product-render/views.html:35
`.ground-base, .ground-surface, .ground-inverse` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:160
`body` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:166
`.btn--secondary` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:438
`.pill` sets color: #ffffff on background-color: #ffffff — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:488
`.nav` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:639
`.nav__menu` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:693
`.tab[aria-selected="true"]` sets color: #f4f4f4 on background-color: #ffffff — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:857
`.field :is(input, select, textarea)` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:1241
`.skip-link:focus` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — skills/taste-skill/assets/system.css:1322
`.cx-knock` 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. — skills/taste-skill/assets/components/base.css:74
`.cx-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. — skills/taste-skill/assets/components/fx-search/component.css:19
`.cx-prompt__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. — skills/taste-skill/assets/components/fx-prompt/component.css:17
`.nav__menu` moves (`transition: opacity 120ms var(--ease), transform 120ms var(--ease), visibility 0s linear 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/system.css:697
`.tile__media > img` moves (`transition: transform 600ms var(--ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/system.css:1145
`.ui-btn` moves (`transition: transform 160ms var(--u-ease), background-color 200ms var(--u-ease), color 200ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/base.css:116
`.ui-ring.is-on` moves (`animation: ui-ring 520ms var(--u-ease) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/base.css:224
`.ui-spin` moves (`animation: ui-spin 700ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/base.css:231
`.card__link svg` moves (`transition: transform 200ms cubic-bezier(.2,.7,.2,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/cards.css:46
`.ui-win__st.is-work::before` moves (`animation: ui-spin 800ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/window/fragment.css:45
`.ui-voice__orb::before` moves (`animation: ui-pearl 18s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/voice/fragment.css:29
`.ui-voice.is-talking .ui-voice__wave i` moves (`animation: ui-wave 820ms var(--u-ease) infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/voice/fragment.css:61
`.ui-switch i` moves (`transition: transform 300ms var(--u-spring)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/toggles/fragment.css:18
`.ui-term__track` moves (`transition: transform 120ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/terminal-run/fragment.css:30
`.ui-term__bar i` moves (`transition: transform 180ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/terminal-run/fragment.css:51
`.ui-term__ln.is-new` moves (`animation: ui-term-in 140ms var(--u-ease) 110ms backwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/terminal-run/fragment.css:76
`.ui-term__ln.is-new .ui-term__ok` moves (`animation: ui-term-pop 240ms var(--u-ease) 110ms both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/terminal-run/fragment.css:77
`.ui-term__tick.is-new` moves (`animation: ui-term-pop 200ms var(--u-ease) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/terminal-run/fragment.css:78
`.ui-search__row` moves (`transition: opacity 240ms var(--u-ease), transform 300ms var(--u-ease), background-color 200ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/search/fragment.css:16
`.ui-pipe__btn` moves (`transition: transform 90ms var(--u-ease), background-color 200ms var(--u-ease), box-shadow 200ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/taste-skill/assets/ui/pipeline-board/fragment.css:35
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.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — skills/taste-skill/scripts/effects.mjs:375
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`publish` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — skills/taste-skill/scripts/effects.mjs:300
What to do
Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
P1 · CI/CD gates6.5 / 10Adequate✓ Tool-verified
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.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 143 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 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:6
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×17) — skills/taste-skill/assets/backgrounds/check.mjs:100, skills/taste-skill/assets/components/fx-map/bake.mjs:57, skills/taste-skill/assets/components/fx-map/component.js:32, …
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.writeFileSync` in `snap` 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. — skills/taste-skill/assets/layout/check.mjs:138
`fs.mkdirSync` in `chrome` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:191
`fs.rmSync` in `chrome` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:193
`execFileSync` in `kill` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:197
`fs.readFileSync` in `chrome` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:199
`fs.mkdirSync` in `cmdShoot` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:241
`fs.writeFileSync` in `cmdShoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — skills/taste-skill/assets/scenes/_demo/shoot.mjs:271, skills/taste-skill/assets/scenes/_demo/shoot.mjs:288, skills/taste-skill/assets/scenes/_demo/shoot.mjs:291
`fs.readFileSync` in `callback to map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:285
`fs.writeFileSync` in `cmdMake` 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. — skills/taste-skill/assets/scenes/_demo/shoot.mjs:311
`mkdirSync` in `launch` 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. — skills/taste-skill/scripts/consistency.mjs:4619
`spawnSync` in `stop` 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. — skills/taste-skill/scripts/consistency.mjs:4632
`rmSync` in `stop` 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. — skills/taste-skill/scripts/consistency.mjs:4635
`spawnSync` in `close` 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. — skills/taste-skill/scripts/consistency.mjs:4643
`existsSync` in `close` 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. — skills/taste-skill/scripts/consistency.mjs:4647
`rmSync` in `close` 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. — skills/taste-skill/scripts/consistency.mjs:4647
`existsSync` in `pageExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — skills/taste-skill/scripts/consistency.mjs:9205, skills/taste-skill/scripts/consistency.mjs:9206
`statSync` in `pageExists` 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. — skills/taste-skill/scripts/consistency.mjs:9205
`existsSync` in `shaderLint` 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. — skills/taste-skill/scripts/consistency.mjs:9740
`statSync` in `shaderLint` 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. — skills/taste-skill/scripts/consistency.mjs:9740
`readFileSync` in `shaderLint` 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. — skills/taste-skill/scripts/consistency.mjs:9740
`writeFileSync` in `cropTo` 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. — skills/taste-skill/scripts/consistency.mjs:10203
`writeFileSync` in `safe("rendered page")` 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. — skills/taste-skill/scripts/consistency.mjs:10252
`writeFileSync` in `runWidth` 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. — skills/taste-skill/scripts/consistency.mjs:10367
`readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — skills/taste-skill/scripts/consistency.mjs:10852
`fs.existsSync` in `buildIndex` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — skills/taste-skill/scripts/effects.mjs:110, skills/taste-skill/scripts/effects.mjs:116, skills/taste-skill/scripts/effects.mjs:122
`fs.readdirSync` in `buildIndex` 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. — skills/taste-skill/scripts/effects.mjs:110
`fs.readFileSync` in `buildIndex` 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. — skills/taste-skill/scripts/effects.mjs:119
`fs.statSync` in `buildIndex` 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. — skills/taste-skill/scripts/effects.mjs:125
`fs.writeFileSync` in `buildIndex` 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. — skills/taste-skill/scripts/effects.mjs:142
`fs.existsSync` in `readIndex` 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. — skills/taste-skill/scripts/effects.mjs:151
`fs.readFileSync` in `readIndex` 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. — skills/taste-skill/scripts/effects.mjs:152
`fs.mkdirSync` in `pick` 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. — skills/taste-skill/scripts/effects.mjs:228
`fs.writeFileSync` in `pick` 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. — skills/taste-skill/scripts/effects.mjs:229
`fs.readFileSync` in `gallery` 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. — skills/taste-skill/scripts/effects.mjs:255
`fs.writeFileSync` in `gallery` 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. — skills/taste-skill/scripts/effects.mjs:258
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.
0 typed · 134 plain JS — the untyped files are skills/taste-skill/assets/backgrounds/backgrounds.js, skills/taste-skill/assets/backgrounds/check.mjs, skills/taste-skill/assets/backgrounds/pick.mjs, skills/taste-skill/assets/components/fx-avatar/component.js, skills/taste-skill/assets/components/fx-band/component.js, skills/taste-skill/assets/components/fx-bars/component.js (+128 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
32 duplicated blocks under skills/taste-skill/assets/effects/ have copies in at least two of the sibling directories ascii-shade, aurora-curtains, bayer-dither, caustics, contour-lines, dot-terrain (+17 more sibling(s) not listed) — 23 of them are reported below, and 9 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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. — skills/taste-skill/assets/effects/bayer-dither/effect.js:112
22 duplicated blocks under skills/taste-skill/assets/ have copies in at least two of the sibling directories components, effects, layout, moments, motion, objects (+2 more sibling(s) not listed) — 19 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — skills/taste-skill/assets/moments/moments.js:30
15 duplicated blocks under skills/taste-skill/assets/objects/ have copies in at least two of the sibling directories _print-core, _scenes, dither-sequence, dot-object, exploded-layers, photo-dither (+7 more sibling(s) not listed) — 13 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 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 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 15 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. — skills/taste-skill/assets/objects/_print-core/auto.js:41
13 duplicated blocks under skills/taste-skill/ have copies in at least two of the sibling directories assets, scripts — 12 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — skills/taste-skill/assets/layout/check.mjs:108
8 duplicated blocks under skills/taste-skill/assets/components/ have copies in at least two of the sibling directories fx-avatar, fx-band, fx-bars, fx-chart, fx-headline, fx-icon-tiles (+7 more sibling(s) not listed) — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — skills/taste-skill/assets/components/fx-logos/component.js:10
6 duplicated blocks under skills/taste-skill/assets/scenes/ have copies in at least two of the sibling directories descend-through-weather, dot-becomes-the-full-stop, fixed-hero-object, fly-into-the-shape, letter-bar-floods-the-ground, object-through-giant-type (+3 more sibling(s) not listed) — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94
skills/taste-skill/assets/moments/moments.js:30 · skills/taste-skill/assets/scenes/scenes.js:25 — the two spans are one implementation copied and then locally edited — 552 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. — skills/taste-skill/assets/moments/moments.js:30
skills/taste-skill/assets/objects/_print-core/auto.js:41 · skills/taste-skill/assets/objects/_scenes/auto.js:41 — the two spans are one implementation copied and then locally edited — 417 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. — skills/taste-skill/assets/objects/_print-core/auto.js:41
skills/taste-skill/assets/ui/cursor/fragment.js:28 · skills/taste-skill/assets/ui/integrations/fragment.js:18 — the two spans are one implementation copied and then locally edited — 316 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. — skills/taste-skill/assets/ui/cursor/fragment.js:28
skills/taste-skill/assets/components/fx-feature-card/component.js:173 · skills/taste-skill/assets/components/fx-feature-card/component.js:201 — the two spans are one implementation copied and then locally edited — 173 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. — skills/taste-skill/assets/components/fx-feature-card/component.js:173
skills/taste-skill/assets/layout/check.mjs:108 · skills/taste-skill/scripts/perf.mjs:385 — the two spans are one implementation copied and then locally edited — 508 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. — skills/taste-skill/assets/layout/check.mjs:108
skills/taste-skill/scripts/perf.mjs:385 · REDACTED:317 — the two spans are one implementation copied and then locally edited — 522 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. — skills/taste-skill/scripts/perf.mjs:385
skills/taste-skill/scripts/consistency.mjs:3590 · REDACTED:212 — 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. — skills/taste-skill/scripts/consistency.mjs:3590
skills/taste-skill/assets/effects/fx.js:698 · skills/taste-skill/assets/objects/photo-kit/photo.js:775 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — skills/taste-skill/assets/effects/fx.js:698
skills/taste-skill/assets/effects/prism-dispersion/effect.js:177 · skills/taste-skill/assets/effects/spotlight-cone/effect.js:135 — 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. — skills/taste-skill/assets/effects/prism-dispersion/effect.js:177
skills/taste-skill/scripts/effects.mjs:56 · skills/taste-skill/scripts/moments.mjs: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. — skills/taste-skill/scripts/effects.mjs:56
skills/taste-skill/assets/effects/dotted-globe/effect.js:129 · skills/taste-skill/assets/objects/print-globe/object.js:121 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — skills/taste-skill/assets/effects/dotted-globe/effect.js:129
skills/taste-skill/assets/moments/moments.js:31 · skills/taste-skill/assets/scenes/scenes.js:26 · skills/taste-skill/assets/ui/ui.js:48 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — skills/taste-skill/assets/moments/moments.js:31
skills/taste-skill/assets/objects/_print-core/print3d.js:116 · skills/taste-skill/assets/objects/_scenes/kit.js:391 — the two spans are one implementation copied and then locally edited — 174 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. — skills/taste-skill/assets/objects/_print-core/print3d.js:116
skills/taste-skill/assets/effects/fx.js:580 · skills/taste-skill/assets/effects/ridgeline/effect.js:47 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — skills/taste-skill/assets/effects/fx.js:580
skills/taste-skill/assets/effects/fx.js:227 · skills/taste-skill/assets/effects/pick.js:59 — the two spans are one implementation copied and then locally edited — 109 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. — skills/taste-skill/assets/effects/fx.js:227
skills/taste-skill/assets/effects/grid-pulse/effect.js:24 · skills/taste-skill/assets/effects/ridgeline/effect.js:47 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — skills/taste-skill/assets/effects/grid-pulse/effect.js:24
skills/taste-skill/assets/moments/lib.js:114 · skills/taste-skill/assets/motion/motion.js:289 — the two spans are one implementation copied and then locally edited — 98 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. — skills/taste-skill/assets/moments/lib.js:114
skills/taste-skill/assets/effects/fx.js:25 · skills/taste-skill/assets/objects/_print-core/print3d.js:174 — the two spans are one implementation copied and then locally edited — 206 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. — skills/taste-skill/assets/effects/fx.js:25
skills/taste-skill/assets/backgrounds/check.mjs:92 · skills/taste-skill/scripts/moments.mjs:355 — 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. — skills/taste-skill/assets/backgrounds/check.mjs:92
skills/taste-skill/assets/components/fx-logos/component.js:10 · skills/taste-skill/assets/components/fx-stat/component.js:10 — the two spans are one implementation copied and then locally edited — 72 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. — skills/taste-skill/assets/components/fx-logos/component.js:10
skills/taste-skill/assets/effects/fx.js:190 · skills/taste-skill/assets/objects/_print-core/print3d.js:238 · skills/taste-skill/assets/system.js:388 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — skills/taste-skill/assets/effects/fx.js:190
skills/taste-skill/assets/effects/fx.js:492 · skills/taste-skill/assets/objects/photo-kit/photo.js:450 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — skills/taste-skill/assets/effects/fx.js:492
skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94 · skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:99 — the two spans are one implementation copied and then locally edited — 82 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. — skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94
skills/taste-skill/scripts/consistency.mjs:6588 · skills/taste-skill/scripts/consistency.mjs:6607 — 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. — skills/taste-skill/scripts/consistency.mjs:6588
skills/taste-skill/scripts/photos.mjs:117 · skills/taste-skill/scripts/start.mjs:85 — 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. — skills/taste-skill/scripts/photos.mjs:117
skills/taste-skill/assets/effects/caustics/effect.js:14 · skills/taste-skill/assets/effects/dot-terrain/effect.js:21 — the two spans are one implementation copied and then locally edited — 96 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. — skills/taste-skill/assets/effects/caustics/effect.js:14
skills/taste-skill/assets/effects/fluted-glass/effect.js:144 · skills/taste-skill/assets/effects/grain-gradient/effect.js:118 — 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. — skills/taste-skill/assets/effects/fluted-glass/effect.js:144
skills/taste-skill/assets/effects/grid-pulse/effect.js:64 · skills/taste-skill/assets/effects/ridgeline/effect.js:97 — 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. — skills/taste-skill/assets/effects/grid-pulse/effect.js:64
skills/taste-skill/assets/objects/_print-core/print3d.js:124 · skills/taste-skill/assets/objects/photo-kit/photo.js:505 — the two spans are one implementation copied and then locally edited — 130 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. — skills/taste-skill/assets/objects/_print-core/print3d.js:124
skills/taste-skill/assets/objects/dot-object/object.js:66 · skills/taste-skill/assets/objects/photo-kit/photo.js:166 — the two spans are one implementation copied and then locally edited — 135 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — skills/taste-skill/assets/objects/dot-object/object.js:66
skills/taste-skill/scripts/consistency.mjs:1747 · skills/taste-skill/scripts/consistency.mjs:3945 — 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. — skills/taste-skill/scripts/consistency.mjs:1747
skills/taste-skill/scripts/consistency.mjs:3510 · REDACTED:181 — 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. — skills/taste-skill/scripts/consistency.mjs:3510
skills/taste-skill/scripts/consistency.mjs:9764 · skills/taste-skill/scripts/consistency.mjs:9906 — 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. — skills/taste-skill/scripts/consistency.mjs:9764
skills/taste-skill/scripts/moments.mjs:157 · skills/taste-skill/scripts/photos.mjs:292 — the two spans are one implementation copied and then locally edited — 164 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. — skills/taste-skill/scripts/moments.mjs:157
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 · 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.
runWidth has cyclomatic complexity 693 and cognitive complexity 1310; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:10219
extras has cyclomatic complexity 333 and cognitive complexity 478; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:8190
pageInfo has cyclomatic complexity 282 and cognitive complexity 373; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:7207
measure has cyclomatic complexity 202 and cognitive complexity 279; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:1868
moreChecks has cyclomatic complexity 193 and cognitive complexity 329; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:8718
(anonymous) has cyclomatic complexity 148 and cognitive complexity 225; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:2660
pick has cyclomatic complexity 147 and cognitive complexity 266; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/photos.mjs:317
pageProbe has cyclomatic complexity 146 and cognitive complexity 219; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:4113
run has cyclomatic complexity 138 and cognitive complexity 268; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:4355
build has cyclomatic complexity 134 and cognitive complexity 139; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/assets/diagrams/diagram.js:1174
scan has cyclomatic complexity 130 and cognitive complexity 180; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:1385
audit has cyclomatic complexity 127 and cognitive complexity 159; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:7601
effectFindings has cyclomatic complexity 119 and cognitive complexity 171; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:1135
visualProbe has cyclomatic complexity 119 and cognitive complexity 157; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:700
areaProbe has cyclomatic complexity 115 and cognitive complexity 217; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:3777
checkCollide has cyclomatic complexity 114 and cognitive complexity 189; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:6099
buttonLook has cyclomatic complexity 102 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:5185
(anonymous) has cyclomatic complexity 90 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:2463
build has cyclomatic complexity 80 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/assets/objects/product-render/build.js:812
moreFindings has cyclomatic complexity 80 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:9593
lyCheck has cyclomatic complexity 77 and cognitive complexity 95; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/assets/layout/layout-check.js:34
cutLines has cyclomatic complexity 75 and cognitive complexity 151; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:5498
fetchCmd has cyclomatic complexity 74 and cognitive complexity 141; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/photos.mjs:852
checkSpill has cyclomatic complexity 74 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:5416
hiddenProbe has cyclomatic complexity 73 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:9963
extrasFindings has cyclomatic complexity 73 and cognitive complexity 98; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:9524
copyChecks has cyclomatic complexity 72 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:9397
fetchCmd has cyclomatic complexity 68 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/icons.mjs:310
makeNode has cyclomatic complexity 66 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. — skills/taste-skill/assets/diagrams/diagram.js:352
(anonymous) has cyclomatic complexity 63 and cognitive complexity 101; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:2560
buttonExtras has cyclomatic complexity 62 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:6503
gridCands has cyclomatic complexity 61 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:5610
probe has cyclomatic complexity 59 and cognitive complexity 120; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:6742
run has cyclomatic complexity 57 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:3661
visualCands has cyclomatic complexity 57 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. — skills/taste-skill/scripts/consistency.mjs:7921
fadeCands has cyclomatic complexity 55 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:7798
checkFold has cyclomatic complexity 55 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:6017
readHtml has cyclomatic complexity 54 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/copy-lint.mjs:79
searchCmd has cyclomatic complexity 54 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/photos.mjs:654
checkTaps has cyclomatic complexity 54 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — skills/taste-skill/scripts/consistency.mjs:6195
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.
skills/taste-skill/assets/objects/_print-core/print3d.js has 1728 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/objects/_print-core/print3d.js:1
skills/taste-skill/assets/diagrams/diagram.js has 1633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/diagrams/diagram.js:1
skills/taste-skill/assets/objects/product-render/build.js has 1350 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/objects/product-render/build.js:1
skills/taste-skill/assets/objects/photo-kit/photo.js has 1084 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/objects/photo-kit/photo.js:1
skills/taste-skill/assets/effects/dotted-globe/effect.js has 970 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/effects/dotted-globe/effect.js:1
skills/taste-skill/assets/objects/_scenes/kit.js has 909 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/objects/_scenes/kit.js:1
skills/taste-skill/assets/effects/fx.js has 894 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/effects/fx.js:1
skills/taste-skill/assets/ui/ui.js has 706 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/ui/ui.js:1
skills/taste-skill/assets/effects/duotone-grade/effect.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. — skills/taste-skill/assets/effects/duotone-grade/effect.js:1
skills/taste-skill/assets/system.js has 585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/system.js:1
skills/taste-skill/assets/components/shared.js has 534 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/components/shared.js:1
skills/taste-skill/assets/components/fx-map/bake.mjs has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/components/fx-map/bake.mjs:1
skills/taste-skill/assets/components/fx-dither-object/component.js has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/components/fx-dither-object/component.js:1
skills/taste-skill/assets/objects/product-turntable/object.js has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/taste-skill/assets/objects/product-turntable/object.js: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?
R7 · Dead Code10.0 / 10Exemplary✓ 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.
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 · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — skills/taste-skill/scripts/gate.mjs:308, skills/taste-skill/scripts/gate.mjs:736, skills/taste-skill/scripts/gate.mjs:743
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `skills/taste-skill/scripts/gate.mjs:308` (createHash("sha1")), `skills/taste-skill/scripts/gate.mjs:736` (createHash("sha1")), `skills/taste-skill/scripts/gate.mjs:743` (createHash("sha1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/14 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`pageExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/consistency.mjs:9200
`shaderLint` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/consistency.mjs:9733
`launch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/effects.mjs:424
`fetchCached` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/icons.mjs:90
`measureCmd` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/icons.mjs:492
`cmdShoot` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/scripts/moments.mjs:333
`loadProduct` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/assets/objects/product-render/build.js:1116
`demo` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — skills/taste-skill/assets/objects/photo-kit/demo.js:17, skills/taste-skill/assets/objects/_print-core/demo.js:18
`overpass` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/assets/components/fx-map/bake.mjs:53
`readData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — skills/taste-skill/assets/components/fx-map/component.js:27
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.5 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`t[best]` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `t[best]` at this site, or validate it against the shape the position accepts before interpolating it. — skills/taste-skill/assets/scenes/letter-bar-floods-the-ground/scene.js:41
`fmtDay(days[i])` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — skills/taste-skill/assets/components/fx-chart/component.js:30, skills/taste-skill/assets/components/fx-chart/component.js:31
`fmtDay(days[at])` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/components/fx-chart/component.js:77
`t` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/diagrams/diagram.js:229
`id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/moments/liquid-type/moment.js:29
`icon(!p)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/moments/marquee-row/moment.js:31
`obj.name` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:33
`obj.id` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:35
`obj.name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:36
`meta.line||meta.shows||''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:37
`meta.hover||''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:39
`e` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_print-core/demo.js:41
`p.id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/_scenes/demo.js:24
`n[0].toUpperCase()+n.slice(1)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/objects/photo-kit/demo.js:53
`POINTER_SVG` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — skills/taste-skill/assets/ui/calendar/fragment.js:21, skills/taste-skill/assets/ui/cursor/fragment.js:24, skills/taste-skill/assets/ui/integrations/fragment.js:16
`ico` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/ui/notify/fragment.js:16
`list0` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — skills/taste-skill/assets/ui/notify/fragment.js:21, skills/taste-skill/assets/ui/search/fragment.js:18
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/ui/search/fragment.js:20
`html.replace(="(?:assets\/ui\/)?icons\//g,`src="${new URL('icons/',BASE).href}`)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — skills/taste-skill/assets/ui/ui.js:106
`r.file` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — skills/taste-skill/scripts/moments.mjs:452, skills/taste-skill/scripts/moments.mjs:470
`escH(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — skills/taste-skill/scripts/photos.mjs:959
`escH(c.page)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — skills/taste-skill/scripts/photos.mjs:965, skills/taste-skill/scripts/photos.mjs:966
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×22) — skills/taste-skill/scripts/consistency.mjs:396, skills/taste-skill/scripts/consistency.mjs:725, skills/taste-skill/scripts/consistency.mjs:735, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×15) — skills/taste-skill/scripts/consistency.mjs:561, skills/taste-skill/scripts/consistency.mjs:1259, skills/taste-skill/scripts/consistency.mjs:1260, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — skills/taste-skill/scripts/consistency.mjs:570, skills/taste-skill/scripts/consistency.mjs:1682
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — skills/taste-skill/scripts/consistency.mjs:886
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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 — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 26 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
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.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D20 ADR Quality — Repository kind not determined
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
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 — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
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
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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.
D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Not applicable — no manifest declares this repository's modules, and its source holds 1 production component(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production components are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 3 test file(s) reach none of 132 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
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· <select> without a programmatic label · ×1
<select> without a programmatic label skills/taste-skill/assets/backgrounds/demo.html:144— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <label> that labels no control · ×1
<label> that labels no control skills/taste-skill/scripts/fx-gallery.template.html:375— This <label> has no for 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 for="<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> · ×1
Click handler on a non-interactive <div> skills/taste-skill/assets/components/index.html:137— A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
consistency.lib::extras (cognitive 466) skills/taste-skill/scripts/consistency.mjs:8190— consistency.lib::extras has cognitive complexity 466 (threshold 15). Drivers by points: if/else 113 (257 pts), boolean chains 104, loops 46 (78 pts), ternaries 6 (17 pts), error handling 4 (10 pts) (nesting depth added 193). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::pageInfo (cognitive 382) skills/taste-skill/scripts/consistency.mjs:7207— consistency.lib::pageInfo has cognitive complexity 382 (threshold 15). Drivers by points: if/else 76 (174 pts), boolean chains 88, ternaries 30 (70 pts), loops 26 (39 pts), error handling 4 (11 pts) (nesting depth added 158). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::moreChecks (cognitive 337) skills/taste-skill/scripts/consistency.mjs:8718— consistency.lib::moreChecks has cognitive complexity 337 (threshold 15). Drivers by points: if/else 67 (173 pts), boolean chains 69, ternaries 17 (58 pts), loops 22 (37 pts) (nesting depth added 162). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkCollide (cognitive 190) skills/taste-skill/scripts/consistency.mjs:6099— consistency.lib::checkCollide has cognitive complexity 190 (threshold 15). Drivers by points: if/else 31 (81 pts), ternaries 16 (54 pts), boolean chains 30, loops 14 (25 pts) (nesting depth added 99). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::audit (cognitive 164) skills/taste-skill/scripts/consistency.mjs:7601— consistency.lib::audit has cognitive complexity 164 (threshold 15). Drivers by points: if/else 45 (90 pts), boolean chains 43, loops 15 (20 pts), ternaries 5 (11 pts) (nesting depth added 56). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::cutLines (cognitive 152) skills/taste-skill/scripts/consistency.mjs:5498— consistency.lib::cutLines has cognitive complexity 152 (threshold 15). Drivers by points: if/else 30 (96 pts), boolean chains 23, loops 7 (17 pts), ternaries 5 (16 pts) (nesting depth added 87). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::probe (cognitive 120) skills/taste-skill/scripts/consistency.mjs:6742— consistency.lib::probe has cognitive complexity 120 (threshold 15). Drivers by points: if/else 23 (69 pts), loops 14 (34 pts), boolean chains 13, ternaries 2 (4 pts) (nesting depth added 68). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkSpill (cognitive 111) skills/taste-skill/scripts/consistency.mjs:5416— consistency.lib::checkSpill has cognitive complexity 111 (threshold 15). Drivers by points: if/else 27 (71 pts), boolean chains 29, loops 5 (8 pts), ternaries 1 (3 pts) (nesting depth added 49). To reduce it, split the body into named stages: move each independent 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: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::buttonLook (cognitive 108) skills/taste-skill/scripts/consistency.mjs:5185— consistency.lib::buttonLook has cognitive complexity 108 (threshold 15). Drivers by points: if/else 25 (44 pts), boolean chains 35, ternaries 10 (21 pts), loops 5 (6 pts), error handling 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkFragments (cognitive 90) skills/taste-skill/scripts/consistency.mjs:6387— consistency.lib::checkFragments has cognitive complexity 90 (threshold 15). Drivers by points: if/else 21 (53 pts), boolean chains 19, loops 5 (9 pts), ternaries 4 (9 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::fadeCands (cognitive 88) skills/taste-skill/scripts/consistency.mjs:7798— consistency.lib::fadeCands has cognitive complexity 88 (threshold 15). Drivers by points: if/else 20 (55 pts), boolean chains 17, loops 6 (16 pts) (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. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::gridCands (cognitive 86) skills/taste-skill/scripts/consistency.mjs:5610— consistency.lib::gridCands has cognitive complexity 86 (threshold 15). Drivers by points: if/else 21 (52 pts), boolean chains 19, ternaries 4 (9 pts), loops 4 (6 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::buttonExtras (cognitive 86) skills/taste-skill/scripts/consistency.mjs:6503— consistency.lib::buttonExtras has cognitive complexity 86 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 19, ternaries 5 (13 pts), loops 6 (10 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkTaps (cognitive 79) skills/taste-skill/scripts/consistency.mjs:6195— consistency.lib::checkTaps has cognitive complexity 79 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 18, ternaries 6 (12 pts), loops 4 (6 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::collectButtons (cognitive 76) skills/taste-skill/scripts/consistency.mjs:5761— consistency.lib::collectButtons has cognitive complexity 76 (threshold 15). Drivers by points: if/else 21 (52 pts), boolean chains 19, loops 2 (3 pts), ternaries 1 (2 pts) (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. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::noVisual (cognitive 75) skills/taste-skill/scripts/consistency.mjs:7104— consistency.lib::noVisual has cognitive complexity 75 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 22, ternaries 5 (11 pts), loops 3 (5 pts), error handling 1 (3 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::visualCands (cognitive 71) skills/taste-skill/scripts/consistency.mjs:7921— consistency.lib::visualCands has cognitive complexity 71 (threshold 15). Drivers by points: if/else 17 (39 pts), boolean chains 20, ternaries 3 (8 pts), loops 3 (4 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::holes (cognitive 69) skills/taste-skill/scripts/consistency.mjs:7068— consistency.lib::holes has cognitive complexity 69 (threshold 15). Drivers by points: if/else 16 (38 pts), boolean chains 13, loops 5 (13 pts), ternaries 2 (5 pts) (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. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkTopStagger (cognitive 61) skills/taste-skill/scripts/consistency.mjs:6266— consistency.lib::checkTopStagger has cognitive complexity 61 (threshold 15). Drivers by points: if/else 14 (38 pts), loops 6 (13 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkFold (cognitive 60) skills/taste-skill/scripts/consistency.mjs:6017— consistency.lib::checkFold has cognitive complexity 60 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 15, loops 4 (5 pts), ternaries 2 (5 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkUnderChrome (cognitive 60) skills/taste-skill/scripts/consistency.mjs:6233— consistency.lib::checkUnderChrome has cognitive complexity 60 (threshold 15). Drivers by points: if/else 15 (43 pts), boolean chains 9, loops 5 (8 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::holdPass (cognitive 56) skills/taste-skill/scripts/consistency.mjs:6854— consistency.lib::holdPass has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (34 pts), loops 11 (15 pts), boolean chains 7 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkStagger (cognitive 55) skills/taste-skill/scripts/consistency.mjs:5678— consistency.lib::checkStagger has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (34 pts), loops 5 (9 pts), boolean chains 7, ternaries 2 (5 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. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkCentre (cognitive 53) skills/taste-skill/scripts/consistency.mjs:6474— consistency.lib::checkCentre has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 12, ternaries 3 (6 pts), loops 3 (5 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. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::passLayer (cognitive 50) skills/taste-skill/scripts/consistency.mjs:5309— consistency.lib::passLayer has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 13, loops 4 (7 pts), ternaries 1 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 76 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 77 times rather than 77 independent problems. Splitting this body alone leaves the other 76 exactly as they are. Where these are variations on one operation, the change that clears all 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::extras (cyclomatic 336) skills/taste-skill/scripts/consistency.mjs:8190— consistency.lib::extras has cyclomatic complexity 336 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::pageInfo (cyclomatic 287) skills/taste-skill/scripts/consistency.mjs:7207— consistency.lib::pageInfo has cyclomatic complexity 287 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::moreChecks (cyclomatic 199) skills/taste-skill/scripts/consistency.mjs:8718— consistency.lib::moreChecks has cyclomatic complexity 199 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::audit (cyclomatic 131) skills/taste-skill/scripts/consistency.mjs:7601— consistency.lib::audit has cyclomatic complexity 131 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkCollide (cyclomatic 116) skills/taste-skill/scripts/consistency.mjs:6099— consistency.lib::checkCollide has cyclomatic complexity 116 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::buttonLook (cyclomatic 102) skills/taste-skill/scripts/consistency.mjs:5185— consistency.lib::buttonLook has cyclomatic complexity 102 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkSpill (cyclomatic 80) skills/taste-skill/scripts/consistency.mjs:5416— consistency.lib::checkSpill has cyclomatic complexity 80 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::cutLines (cyclomatic 75) skills/taste-skill/scripts/consistency.mjs:5498— consistency.lib::cutLines has cyclomatic complexity 75 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::buttonExtras (cyclomatic 62) skills/taste-skill/scripts/consistency.mjs:6503— consistency.lib::buttonExtras has cyclomatic complexity 62 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::gridCands (cyclomatic 61) skills/taste-skill/scripts/consistency.mjs:5610— consistency.lib::gridCands has cyclomatic complexity 61 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::probe (cyclomatic 59) skills/taste-skill/scripts/consistency.mjs:6742— consistency.lib::probe has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::visualCands (cyclomatic 57) skills/taste-skill/scripts/consistency.mjs:7921— consistency.lib::visualCands has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkFold (cyclomatic 56) skills/taste-skill/scripts/consistency.mjs:6017— consistency.lib::checkFold has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::noVisual (cyclomatic 56) skills/taste-skill/scripts/consistency.mjs:7104— consistency.lib::noVisual has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::fadeCands (cyclomatic 56) skills/taste-skill/scripts/consistency.mjs:7798— consistency.lib::fadeCands has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkTaps (cyclomatic 54) skills/taste-skill/scripts/consistency.mjs:6195— consistency.lib::checkTaps has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkFragments (cyclomatic 53) skills/taste-skill/scripts/consistency.mjs:6387— consistency.lib::checkFragments 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. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::collectButtons (cyclomatic 49) skills/taste-skill/scripts/consistency.mjs:5761— consistency.lib::collectButtons has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::holes (cyclomatic 45) skills/taste-skill/scripts/consistency.mjs:7068— consistency.lib::holes has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent 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: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::passLayer (cyclomatic 39) skills/taste-skill/scripts/consistency.mjs:5309— consistency.lib::passLayer has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkTilt (cyclomatic 37) skills/taste-skill/scripts/consistency.mjs:5364— consistency.lib::checkTilt has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkCentre (cyclomatic 37) skills/taste-skill/scripts/consistency.mjs:6474— consistency.lib::checkCentre has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::holdPass (cyclomatic 37) skills/taste-skill/scripts/consistency.mjs:6854— consistency.lib::holdPass has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::seams (cyclomatic 37) skills/taste-skill/scripts/consistency.mjs:8117— consistency.lib::seams has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.lib::checkTopStagger (cyclomatic 36) skills/taste-skill/scripts/consistency.mjs:6266— consistency.lib::checkTopStagger 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. This shape REPEATS in the file: 67 other methods here (consistency.lib::pinnedRight, consistency.lib::quickKind, consistency.lib::surface, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 68 times rather than 68 independent problems. Splitting this body alone leaves the other 67 exactly as they are. Where these are variations on one operation, the change that clears all 68 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Sync-over-async blocking skills/taste-skill/assets/layout/check.mjs:138— `fs.writeFileSync` in `snap` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:191— `fs.mkdirSync` in `chrome` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:193— `fs.rmSync` in `chrome` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:197— `execFileSync` in `kill` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:199— `fs.readFileSync` in `chrome` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:241— `fs.mkdirSync` in `cmdShoot` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:271— `fs.writeFileSync` in `cmdShoot` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:285— `fs.readFileSync` in `callback to map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking skills/taste-skill/assets/scenes/_demo/shoot.mjs:288— `fs.writeFileSync` in `cmdShoot` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:291— `fs.writeFileSync` in `cmdShoot` 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 skills/taste-skill/assets/scenes/_demo/shoot.mjs:311— `fs.writeFileSync` in `cmdMake` 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 skills/taste-skill/scripts/consistency.mjs:4619— `mkdirSync` in `launch` 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 skills/taste-skill/scripts/consistency.mjs:4632— `spawnSync` in `stop` 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 skills/taste-skill/scripts/consistency.mjs:4635— `rmSync` in `stop` 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 skills/taste-skill/scripts/consistency.mjs:4643— `spawnSync` in `close` 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 skills/taste-skill/scripts/consistency.mjs:4647— `existsSync` in `close` 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 skills/taste-skill/scripts/consistency.mjs:4647— `rmSync` in `close` 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 skills/taste-skill/scripts/consistency.mjs:9205— `existsSync` in `pageExists` 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 skills/taste-skill/scripts/consistency.mjs:9205— `statSync` in `pageExists` 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 skills/taste-skill/scripts/consistency.mjs:9206— `existsSync` in `pageExists` 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 skills/taste-skill/scripts/consistency.mjs:9740— `existsSync` in `shaderLint` 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 skills/taste-skill/scripts/consistency.mjs:9740— `statSync` in `shaderLint` 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 skills/taste-skill/scripts/consistency.mjs:9740— `readFileSync` in `shaderLint` 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 skills/taste-skill/scripts/consistency.mjs:10203— `writeFileSync` in `cropTo` 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 skills/taste-skill/scripts/consistency.mjs:10252— `writeFileSync` in `safe("rendered page")` 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.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:396— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:561— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:725— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:735— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:886— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:888— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:899— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:900— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:907— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:947— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1259— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1260— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1437— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1444— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1651— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:1662— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:2080— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3283— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3295— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3296— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3298— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3403— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3415— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3595— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/taste-skill/scripts/consistency.mjs:3604— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 12 more in this group — see findings.md.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×27
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/effects/gallery.html:143— `.toast` moves (`transition: opacity .2s ease, transform .2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:76— `.l-assign .ptr` moves (`animation: assign-ptr var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:81— `.l-assign .who` moves (`animation: assign-who var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:89— `.l-late .st-late` moves (`animation: late-on var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:93— `.l-late.toast` moves (`animation: late-toast var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:100— `.l-cycle .bar i` moves (`animation: cycle-fill var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:102— `.l-cycle.done` moves (`animation: cycle-done var(--m-cycle) var(--m-ease) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/motion/demo.html:124— `.mover` moves (`animation: move-card var(--m-cycle) var(--m-ease-io) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/objects/product-render/views.html:35— `.swatch` moves (`transition: transform 160ms ease, border-color 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/scripts/fx-gallery.template.html:284— `.toast` moves (`transition: opacity .2s ease, transform .2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/system.css:697— `.nav__menu` moves (`transition: opacity 120ms var(--ease), transform 120ms var(--ease), visibility 0s linear 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/system.css:1145— `.tile__media > img` moves (`transition: transform 600ms var(--ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/base.css:116— `.ui-btn` moves (`transition: transform 160ms var(--u-ease), background-color 200ms var(--u-ease), color 200ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/base.css:224— `.ui-ring.is-on` moves (`animation: ui-ring 520ms var(--u-ease) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/base.css:231— `.ui-spin` moves (`animation: ui-spin 700ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/cards.css:46— `.card__link svg` moves (`transition: transform 200ms cubic-bezier(.2,.7,.2,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/window/fragment.css:45— `.ui-win__st.is-work::before` moves (`animation: ui-spin 800ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/voice/fragment.css:29— `.ui-voice__orb::before` moves (`animation: ui-pearl 18s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/voice/fragment.css:61— `.ui-voice.is-talking .ui-voice__wave i` moves (`animation: ui-wave 820ms var(--u-ease) infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/toggles/fragment.css:18— `.ui-switch i` moves (`transition: transform 300ms var(--u-spring)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/terminal-run/fragment.css:30— `.ui-term__track` moves (`transition: transform 120ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/terminal-run/fragment.css:51— `.ui-term__bar i` moves (`transition: transform 180ms var(--u-ease)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/terminal-run/fragment.css:76— `.ui-term__ln.is-new` moves (`animation: ui-term-in 140ms var(--u-ease) 110ms backwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/terminal-run/fragment.css:77— `.ui-term__ln.is-new .ui-term__ok` moves (`animation: ui-term-pop 240ms var(--u-ease) 110ms both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/taste-skill/assets/ui/terminal-run/fragment.css:78— `.ui-term__tick.is-new` moves (`animation: ui-term-pop 200ms var(--u-ease) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
+ 2 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×27
Untrusted text written into markup unescaped skills/taste-skill/assets/components/fx-chart/component.js:30— `fmtDay(days[i])` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/components/fx-chart/component.js:31— `fmtDay(days[i])` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/components/fx-chart/component.js:77— `fmtDay(days[at])` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/diagrams/diagram.js:229— `t` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/moments/liquid-type/moment.js:29— `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/moments/marquee-row/moment.js:31— `icon(!p)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:33— `obj.name` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:35— `obj.id` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:36— `obj.name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:37— `meta.line||meta.shows||''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:39— `meta.hover||''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_print-core/demo.js:41— `e` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/_scenes/demo.js:24— `p.id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/objects/photo-kit/demo.js:53— `n[0].toUpperCase()+n.slice(1)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/calendar/fragment.js:21— `POINTER_SVG` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/cursor/fragment.js:24— `POINTER_SVG` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/integrations/fragment.js:16— `POINTER_SVG` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/notify/fragment.js:16— `ico` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/notify/fragment.js:21— `list0` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/search/fragment.js:18— `list0` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/search/fragment.js:20— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/assets/ui/ui.js:106— `html.replace(="(?:assets\/ui\/)?icons\//g,`src="${new URL('icons/',BASE).href}`)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped skills/taste-skill/scripts/moments.mjs:452— `r.file` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped skills/taste-skill/scripts/moments.mjs:470— `r.file` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped skills/taste-skill/scripts/photos.mjs:959— `escH(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
+ 2 more in this group — see findings.md.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×21
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:208— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:270— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:279— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:300— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:312— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:322— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/backgrounds/demo.html:357— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-centred.html:197— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-collage.html:195— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-editorial.html:103— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-film.html:107— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-photo.html:108— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-place.html:92— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-product.html:106— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-split.html:108— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-statement.html:121— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-triptych.html:159— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/layout/hero-word.html:132— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/moments/iris-opens/demo.html:54— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/moments/lines-rise/demo.html:56— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 skills/taste-skill/assets/motion/demo.html:454— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Outbound HTTP without resilience skills/taste-skill/assets/backgrounds/check.mjs:100— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/components/fx-map/bake.mjs:57— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/components/fx-map/component.js:32— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/diagrams/diagram.js:153— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/layout/check.mjs:125— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/objects/_print-core/demo.js:22— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/objects/photo-kit/demo.js:18— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/objects/product-render/build.js:1118— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/objects/product-render/build.js:1123— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/objects/product-render/make-posters.mjs:115— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/assets/ui/ui.js:66— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/scripts/effects.mjs:454— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/scripts/icons.mjs:94— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/scripts/icons.mjs:529— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/scripts/moments.mjs:362— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/taste-skill/scripts/perf.mjs:400— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:332— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×12
Heading level jumps from h1 to h4 skills/taste-skill/assets/backgrounds/demo.html:171— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/layout/hero-collage.html:113— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/layout/hero-triptych.html:103— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/counter-rolls/demo.html:42— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/cursor-spotlight/demo.html:38— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/headline-arrives/demo.html:40— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/iris-opens/demo.html:35— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/letters-assemble/demo.html:35— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/lines-rise/demo.html:34— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/marquee-row/demo.html:36— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/word-highlight/demo.html:37— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h4 skills/taste-skill/assets/moments/word-rotate/demo.html:45— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
FileTooLong: scripts/consistency.mjs skills/taste-skill/scripts/consistency.mjs— FileTooLong — 8272 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 7772 over it, 16.54× 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: _print-core/print3d.js skills/taste-skill/assets/objects/_print-core/print3d.js— FileTooLong — 1274 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 774 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: diagrams/diagram.js skills/taste-skill/assets/diagrams/diagram.js— FileTooLong — 1246 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 746 over it, 2.49× 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: product-render/build.js skills/taste-skill/assets/objects/product-render/build.js— FileTooLong — 996 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 496 over it, 1.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dotted-globe/effect.js skills/taste-skill/assets/effects/dotted-globe/effect.js— FileTooLong — 801 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 301 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: photo-kit/photo.js skills/taste-skill/assets/objects/photo-kit/photo.js— FileTooLong — 787 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 287 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scripts/photos.mjs skills/taste-skill/scripts/photos.mjs— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× 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: scripts/fx-gallery.template.html skills/taste-skill/scripts/fx-gallery.template.html— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 186 over it, 1.37× 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: _scenes/kit.js skills/taste-skill/assets/objects/_scenes/kit.js— FileTooLong — 659 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 159 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: effects/fx.js skills/taste-skill/assets/effects/fx.js— FileTooLong — 657 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 157 over it, 1.31× 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: scripts/gate.mjs skills/taste-skill/scripts/gate.mjs— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 99 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: duotone-grade/effect.js skills/taste-skill/assets/effects/duotone-grade/effect.js— FileTooLong — 514 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 14 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×11
Async function without AbortSignal: pageExists skills/taste-skill/scripts/consistency.mjs:9200— `pageExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: shaderLint skills/taste-skill/scripts/consistency.mjs:9733— `shaderLint` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: launch skills/taste-skill/scripts/effects.mjs:424— `launch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchCached skills/taste-skill/scripts/icons.mjs:90— `fetchCached` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: measureCmd skills/taste-skill/scripts/icons.mjs:492— `measureCmd` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: cmdShoot skills/taste-skill/scripts/moments.mjs:333— `cmdShoot` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadProduct skills/taste-skill/assets/objects/product-render/build.js:1116— `loadProduct` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: demo skills/taste-skill/assets/objects/photo-kit/demo.js:17— `demo` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: demo skills/taste-skill/assets/objects/_print-core/demo.js:18— `demo` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: overpass skills/taste-skill/assets/components/fx-map/bake.mjs:53— `overpass` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: readData skills/taste-skill/assets/components/fx-map/component.js:27— `readData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Low contrast colour pair in CSS (1.1:1) skills/taste-skill/assets/objects/_print-core/cards.html:26— `.seg button[aria-pressed="true"]` sets color: #17181b on background-color: #111113 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:160— `.ground-base, .ground-surface, .ground-inverse` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:166— `body` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:438— `.btn--secondary` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:639— `.nav` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:693— `.nav__menu` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:857— `.tab[aria-selected="true"]` sets color: #f4f4f4 on background-color: #ffffff — 1.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 (1.1:1) skills/taste-skill/assets/system.css:1241— `.field :is(input, select, textarea)` sets color: #ffffff on background-color: #f4f4f4 — 1.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 (1.1:1) skills/taste-skill/assets/system.css:1322— `.skip-link:focus` sets color: #ffffff on background-color: #f4f4f4 — 1.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
mount::frame (cognitive 44) skills/taste-skill/assets/objects/exploded-layers/object.js:221— mount::frame has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 14 (20 pts), if/else 7 (12 pts), boolean chains 6, loops 2 (4 pts), other 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mount::frame (cognitive 29) skills/taste-skill/assets/objects/product-turntable/object.js:363— mount::frame has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7, ternaries 4 (5 pts), 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.
mount::frame (cognitive 24) skills/taste-skill/assets/objects/dither-sequence/object.js:170— mount::frame has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 4 (6 pts), boolean chains 5, 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.
mount::frame (cognitive 22) skills/taste-skill/assets/objects/split-reveal/object.js:179— mount::frame has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
mount::update (cognitive 22) skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:66— mount::update has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 5 (7 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mount::update (cognitive 19) skills/taste-skill/assets/scenes/product-assembles-into-its-action/scene.js:63— mount::update has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 3 (4 pts), loops 3, 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.
mount::update (cognitive 17) skills/taste-skill/assets/scenes/dot-becomes-the-full-stop/scene.js:62— mount::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (6 pts), boolean chains 1, loops 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.
mount::frame (cognitive 16) skills/taste-skill/assets/objects/dot-object/object.js:249— mount::frame has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, 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.
mount::measure (cognitive 16) skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:40— mount::measure has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), boolean chains 2, loops 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.
Hotspot: skills/taste-skill/scripts/consistency.mjs skills/taste-skill/scripts/consistency.mjs:4865— skills/taste-skill/scripts/consistency.mjs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 4417 in consistency.lib at line 4865. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/scripts/consistency.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/scripts/photos.mjs skills/taste-skill/scripts/photos.mjs:317— skills/taste-skill/scripts/photos.mjs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 331 in photos.pick at line 317. 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-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/scripts/photos.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/assets/layout/layout-check.js skills/taste-skill/assets/layout/layout-check.js:34— skills/taste-skill/assets/layout/layout-check.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 123 in layout-check.lyCheck at line 34. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/assets/layout/layout-check.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: skills/taste-skill/scripts/moments.mjs skills/taste-skill/scripts/moments.mjs:333— skills/taste-skill/scripts/moments.mjs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in moments.cmdShoot at line 333. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/scripts/moments.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/scripts/icons.mjs skills/taste-skill/scripts/icons.mjs:492— skills/taste-skill/scripts/icons.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in icons.measureCmd at line 492. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/scripts/icons.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/scripts/effects.mjs skills/taste-skill/scripts/effects.mjs:424— skills/taste-skill/scripts/effects.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in effects.launch at line 424. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/scripts/effects.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/assets/layout/deal.mjs skills/taste-skill/assets/layout/deal.mjs:80— skills/taste-skill/assets/layout/deal.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in deal.dealOnce at line 80. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/assets/layout/deal.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: skills/taste-skill/assets/scenes/_demo/shoot.mjs skills/taste-skill/assets/scenes/_demo/shoot.mjs:75— skills/taste-skill/assets/scenes/_demo/shoot.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in shoot.buildIndex at line 75. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 13:33:21 +01:00' --until='2026-11-07 13:33:21 +01:00' --full-history --no-merges -- skills/taste-skill/assets/scenes/_demo/shoot.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: effect.mountGlobe skills/taste-skill/assets/effects/dotted-globe/effect.js:450— FunctionTooLong — mountGlobe runs 451 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 351 over it, 4.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: photo.photoGL skills/taste-skill/assets/objects/photo-kit/photo.js:582— FunctionTooLong — photoGL runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: photos.pick skills/taste-skill/scripts/photos.mjs:317— FunctionTooLong — pick runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: object.frag skills/taste-skill/assets/objects/product-turntable/object.js:25— FunctionTooLong — frag runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: effect.mountAscii skills/taste-skill/assets/effects/ascii-shade/effect.js:101— FunctionTooLong — mountAscii runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: build.build skills/taste-skill/assets/objects/product-render/build.js:812— FunctionTooLong — 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.
FunctionTooLong: moments.cmdShoot skills/taste-skill/scripts/moments.mjs:333— FunctionTooLong — cmdShoot 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.
mount::frame (cyclomatic 34) skills/taste-skill/assets/objects/exploded-layers/object.js:221— mount::frame has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mount::frame (cyclomatic 26) skills/taste-skill/assets/objects/product-turntable/object.js:363— mount::frame 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.
mount::frame (cyclomatic 23) skills/taste-skill/assets/objects/dither-sequence/object.js:170— mount::frame 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.
mount::frame (cyclomatic 21) skills/taste-skill/assets/objects/dot-object/object.js:249— mount::frame 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.
mount::frame (cyclomatic 20) skills/taste-skill/assets/objects/split-reveal/object.js:179— mount::frame 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.
Duplicated block (9 lines × 2 locations) skills/taste-skill/assets/effects/fluted-glass/effect.js:144— skills/taste-skill/assets/effects/fluted-glass/effect.js:144 · skills/taste-skill/assets/effects/grain-gradient/effect.js:118 — 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 (9 lines × 2 locations) skills/taste-skill/assets/effects/grid-pulse/effect.js:64— skills/taste-skill/assets/effects/grid-pulse/effect.js:64 · skills/taste-skill/assets/effects/ridgeline/effect.js:97 — 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 (9 lines × 2 locations) skills/taste-skill/scripts/consistency.mjs:1747— skills/taste-skill/scripts/consistency.mjs:1747 · skills/taste-skill/scripts/consistency.mjs:3945 — 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 (9 lines × 2 locations) skills/taste-skill/scripts/consistency.mjs:3510— skills/taste-skill/scripts/consistency.mjs:3510 · REDACTED:181 — 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 (9 lines × 2 locations) skills/taste-skill/scripts/consistency.mjs:9764— skills/taste-skill/scripts/consistency.mjs:9764 · skills/taste-skill/scripts/consistency.mjs:9906 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark skills/taste-skill/assets/backgrounds/check.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark skills/taste-skill/assets/icons/demo.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark skills/taste-skill/assets/moments/gallery.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark skills/taste-skill/assets/objects/_print-core/blank-ground.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
print3d.mountPrint::drawPoster (cyclomatic 23) skills/taste-skill/assets/objects/_print-core/print3d.js:1091— print3d.mountPrint::drawPoster 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. This shape REPEATS in the file: 4 other methods here (print3d.mountPrint, print3d.mountPrint::fit, print3d.mountPrint::advance, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
print3d.mountPrint::sync (cyclomatic 23) skills/taste-skill/assets/objects/_print-core/print3d.js:1596— print3d.mountPrint::sync has cyclomatic complexity 23 (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: 4 other methods here (print3d.mountPrint, print3d.mountPrint::drawPoster, print3d.mountPrint::fit, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
print3d.mountPrint::fit (cyclomatic 21) skills/taste-skill/assets/objects/_print-core/print3d.js:1332— print3d.mountPrint::fit 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. This shape REPEATS in the file: 4 other methods here (print3d.mountPrint, print3d.mountPrint::drawPoster, print3d.mountPrint::advance, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
print3d.mountPrint::advance (cyclomatic 16) skills/taste-skill/assets/objects/_print-core/print3d.js:1536— print3d.mountPrint::advance 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. This shape REPEATS in the file: 4 other methods here (print3d.mountPrint, print3d.mountPrint::drawPoster, print3d.mountPrint::fit, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
Duplicated block (10 lines × 2 locations) skills/taste-skill/assets/backgrounds/check.mjs:92— skills/taste-skill/assets/backgrounds/check.mjs:92 · skills/taste-skill/scripts/moments.mjs:355 — 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 (10 lines × 2 locations) skills/taste-skill/assets/effects/fx.js:492— skills/taste-skill/assets/effects/fx.js:492 · skills/taste-skill/assets/objects/photo-kit/photo.js:450 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (10 lines × 2 locations) skills/taste-skill/scripts/consistency.mjs:6588— skills/taste-skill/scripts/consistency.mjs:6588 · skills/taste-skill/scripts/consistency.mjs:6607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) skills/taste-skill/scripts/photos.mjs:117— skills/taste-skill/scripts/photos.mjs:117 · skills/taste-skill/scripts/start.mjs:85 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (9 matched lines × 2 locations) · ×4
Duplicated block with local edits (9 matched lines × 2 locations) skills/taste-skill/assets/effects/caustics/effect.js:14— skills/taste-skill/assets/effects/caustics/effect.js:14 · skills/taste-skill/assets/effects/dot-terrain/effect.js:21 — the two spans are one implementation copied and then locally edited — 96 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (9 matched lines × 2 locations) skills/taste-skill/assets/objects/_print-core/print3d.js:124— skills/taste-skill/assets/objects/_print-core/print3d.js:124 · skills/taste-skill/assets/objects/photo-kit/photo.js:505 — the two spans are one implementation copied and then locally edited — 130 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (9 matched lines × 2 locations) skills/taste-skill/assets/objects/dot-object/object.js:66— skills/taste-skill/assets/objects/dot-object/object.js:66 · skills/taste-skill/assets/objects/photo-kit/photo.js:166 — the two spans are one implementation copied and then locally edited — 135 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (9 matched lines × 2 locations) skills/taste-skill/scripts/moments.mjs:157— skills/taste-skill/scripts/moments.mjs:157 · skills/taste-skill/scripts/photos.mjs:292 — the two spans are one implementation copied and then locally edited — 164 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement skills/taste-skill/assets/components/base.css:74— `.cx-knock` 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 skills/taste-skill/assets/components/fx-search/component.css:19— `.cx-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 skills/taste-skill/assets/components/fx-prompt/component.css:17— `.cx-prompt__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.
mountPrint::render (cognitive 41) skills/taste-skill/assets/objects/_print-core/print3d.js:1433— mountPrint::render has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (17 pts), ternaries 13, boolean chains 9, loops 1, other 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.
mountPrint::fit (cognitive 28) skills/taste-skill/assets/objects/_print-core/print3d.js:1332— mountPrint::fit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mountPrint::act (cognitive 16) skills/taste-skill/assets/objects/_print-core/print3d.js:1658— mountPrint::act has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (6 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.
print3d.mountPrint::drawPoster (cognitive 29) skills/taste-skill/assets/objects/_print-core/print3d.js:1091— print3d.mountPrint::drawPoster has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 7, ternaries 5 (6 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (print3d.mountPrint, print3d.mountPrint::advance, print3d.mountPrint::sync) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
print3d.mountPrint::sync (cognitive 26) skills/taste-skill/assets/objects/_print-core/print3d.js:1596— print3d.mountPrint::sync has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 8 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: 3 other methods here (print3d.mountPrint, print3d.mountPrint::drawPoster, print3d.mountPrint::advance) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
print3d.mountPrint::advance (cognitive 16) skills/taste-skill/assets/objects/_print-core/print3d.js:1536— print3d.mountPrint::advance has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 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. This shape REPEATS in the file: 3 other methods here (print3d.mountPrint, print3d.mountPrint::drawPoster, print3d.mountPrint::sync) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
Weak hash algorithm skills/taste-skill/scripts/gate.mjs:308— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm skills/taste-skill/scripts/gate.mjs:736— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm skills/taste-skill/scripts/gate.mjs:743— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Swallowed exception (caught, then discarded) skills/taste-skill/scripts/consistency.mjs:570— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) skills/taste-skill/scripts/consistency.mjs:886— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) skills/taste-skill/scripts/consistency.mjs:1682— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
AC3 · Page structure· Heading level jumps from h2 to h5 · ×2
Heading level jumps from h2 to h5 skills/taste-skill/assets/layout/hero-statement.html:97— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h5 skills/taste-skill/assets/layout/hero-word.html:104— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
kit.stage::draw (cyclomatic 32) skills/taste-skill/assets/objects/_scenes/kit.js:686— kit.stage::draw 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. This shape REPEATS in the file: 2 other methods here (kit.stage, kit.stage::syncPause) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
kit.stage::syncPause (cyclomatic 16) skills/taste-skill/assets/objects/_scenes/kit.js:854— kit.stage::syncPause 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. This shape REPEATS in the file: 2 other methods here (kit.stage, kit.stage::draw) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
photos.pick::eligible (cyclomatic 26) skills/taste-skill/scripts/photos.mjs:402— photos.pick::eligible 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. This shape REPEATS in the file: 2 other methods here (photos.pick, photos.pick::chooseLead) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
photos.pick::chooseLead (cyclomatic 17) skills/taste-skill/scripts/photos.mjs:442— photos.pick::chooseLead has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (photos.pick, photos.pick::eligible) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 21) · ×2
mount (cyclomatic 21) skills/taste-skill/assets/scenes/letter-bar-floods-the-ground/scene.js:34— mount has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (update, measure, rest, …). 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.
mount (cyclomatic 21) skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:28— mount has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 78, update, near, …). 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.
build.mountProduct::renderStill (cyclomatic 20) skills/taste-skill/assets/objects/product-render/build.js:1257— build.mountProduct::renderStill 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. This shape REPEATS in the file: 2 other methods here (build.mountProduct, build.mountProduct::show) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
build.mountProduct::show (cyclomatic 19) skills/taste-skill/assets/objects/product-render/build.js:1311— build.mountProduct::show 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. This shape REPEATS in the file: 2 other methods here (build.mountProduct, build.mountProduct::renderStill) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 19) · ×2
mount (cyclomatic 19) skills/taste-skill/assets/scenes/descend-through-weather/scene.js:75— mount has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 9 function items inside it that branch (update, rest, a function literal at line 137, …). 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.
mount (cyclomatic 19) skills/taste-skill/assets/scenes/letter-physics/scene.js:24— mount has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 8 function items inside it that branch (update, a function literal at line 53, a function literal at line 38, …). 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.
effect.tones (cyclomatic 18) skills/taste-skill/assets/effects/orb-sphere/effect.js:169— effect.tones 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.
effect.tones (cyclomatic 18) skills/taste-skill/assets/effects/silk-folds/effect.js:162— effect.tones 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.
stage::draw (cognitive 41) skills/taste-skill/assets/objects/_scenes/kit.js:686— stage::draw has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 11, ternaries 2 (4 pts), error handling 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.
stage::syncPause (cognitive 18) skills/taste-skill/assets/objects/_scenes/kit.js:854— stage::syncPause has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4, boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.mountProduct::measureStill (cognitive 24) skills/taste-skill/assets/objects/product-render/build.js:1284— build.mountProduct::measureStill has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (build.mountProduct, build.mountProduct::renderStill) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
build.mountProduct::renderStill (cognitive 18) skills/taste-skill/assets/objects/product-render/build.js:1257— build.mountProduct::renderStill has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 5, error handling 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. This shape REPEATS in the file: 2 other methods here (build.mountProduct, build.mountProduct::measureStill) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
init (cognitive 23) skills/taste-skill/assets/components/fx-search/component.js:15— init has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11, boolean chains 9, ternaries 3. None of this is in the body itself: all 23 points belong to 19 function items inside it that branch (ensure, key, slash, …). 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.
init (cognitive 23) skills/taste-skill/assets/ui/slider/fragment.js:13— init has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 7 (8 pts), boolean chains 6 (nesting depth added 2). Of this number, 13 points are the body's own statements and 10 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.
D2 · Cognitive Complexity· mount (cognitive 21) · ×2
mount (cognitive 21) skills/taste-skill/assets/scenes/fly-into-the-shape/scene.js:53— mount has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7, ternaries 5 (7 pts), boolean chains 4, other 3 (nesting depth added 2). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (update, rest, destroy, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
mount (cognitive 21) skills/taste-skill/assets/scenes/letter-physics/scene.js:24— mount has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (12 pts), if/else 6, boolean chains 2, other 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 53, update, a function literal at line 38, …). 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.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×2
Duplicated block with local edits (33 matched lines × 2 locations) skills/taste-skill/assets/objects/_print-core/auto.js:41— skills/taste-skill/assets/objects/_print-core/auto.js:41 · skills/taste-skill/assets/objects/_scenes/auto.js:41 — the two spans are one implementation copied and then locally edited — 417 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (33 matched lines × 2 locations) skills/taste-skill/assets/ui/cursor/fragment.js:28— skills/taste-skill/assets/ui/cursor/fragment.js:28 · skills/taste-skill/assets/ui/integrations/fragment.js:18 — the two spans are one implementation copied and then locally edited — 316 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 (21 matched lines × 2 locations) · ×2
Duplicated block with local edits (21 matched lines × 2 locations) skills/taste-skill/assets/layout/check.mjs:108— skills/taste-skill/assets/layout/check.mjs:108 · skills/taste-skill/scripts/perf.mjs:385 — the two spans are one implementation copied and then locally edited — 508 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (21 matched lines × 2 locations) skills/taste-skill/scripts/perf.mjs:385— skills/taste-skill/scripts/perf.mjs:385 · REDACTED:317 — the two spans are one implementation copied and then locally edited — 522 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 (14 lines × 2 locations) skills/taste-skill/assets/effects/prism-dispersion/effect.js:177— skills/taste-skill/assets/effects/prism-dispersion/effect.js:177 · skills/taste-skill/assets/effects/spotlight-cone/effect.js:135 — 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 (14 lines × 2 locations) skills/taste-skill/scripts/effects.mjs:56— skills/taste-skill/scripts/effects.mjs:56 · skills/taste-skill/scripts/moments.mjs: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.
Duplicated block (12 lines × 2 locations) skills/taste-skill/assets/effects/fx.js:580— skills/taste-skill/assets/effects/fx.js:580 · skills/taste-skill/assets/effects/ridgeline/effect.js:47 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (12 lines × 2 locations) skills/taste-skill/assets/effects/grid-pulse/effect.js:24— skills/taste-skill/assets/effects/grid-pulse/effect.js:24 · skills/taste-skill/assets/effects/ridgeline/effect.js:47 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×2
Duplicated block with local edits (12 matched lines × 2 locations) skills/taste-skill/assets/effects/fx.js:227— skills/taste-skill/assets/effects/fx.js:227 · skills/taste-skill/assets/effects/pick.js:59 — the two spans are one implementation copied and then locally edited — 109 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (12 matched lines × 2 locations) skills/taste-skill/assets/moments/lib.js:114— skills/taste-skill/assets/moments/lib.js:114 · skills/taste-skill/assets/motion/motion.js:289 — the two spans are one implementation copied and then locally edited — 98 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 (10 matched lines × 2 locations) · ×2
Duplicated block with local edits (10 matched lines × 2 locations) skills/taste-skill/assets/components/fx-logos/component.js:10— skills/taste-skill/assets/components/fx-logos/component.js:10 · skills/taste-skill/assets/components/fx-stat/component.js:10 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (10 matched lines × 2 locations) skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94— skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94 · skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:99 — the two spans are one implementation copied and then locally edited — 82 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.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 skills/taste-skill/assets/diagrams/lab.html:83— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (1.0:1) skills/taste-skill/assets/system.css:488— `.pill` sets color: #ffffff on background-color: #ffffff — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
consistency.runWidth (cyclomatic 899) skills/taste-skill/scripts/consistency.mjs:10219— consistency.runWidth has cyclomatic complexity 899 (threshold 15). Of this number, 683 points are the body's own statements and 216 belong to 77 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
lyCheck (cyclomatic 178) skills/taste-skill/assets/layout/layout-check.js:34— lyCheck has cyclomatic complexity 178 (threshold 15). Of this number, 77 points are the body's own statements and 101 belong to 45 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.
photos.pick (cyclomatic 149) skills/taste-skill/scripts/photos.mjs:317— photos.pick has cyclomatic complexity 149 (threshold 15). To reduce it, separate the cases: extract each independent 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: 2 other methods here (photos.pick::eligible, photos.pick::chooseLead) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
build (cyclomatic 141) skills/taste-skill/assets/objects/product-render/build.js:812— build has cyclomatic complexity 141 (threshold 15). Of this number, 80 points are the body's own statements and 61 belong to 29 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.
Diagram.build (cyclomatic 136) skills/taste-skill/assets/diagrams/diagram.js:1174— Diagram.build has cyclomatic complexity 136 (threshold 15). To reduce it, separate the cases: extract each independent 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 (Diagram.build::attempt) 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.
consistency.moreFindings (cyclomatic 101) skills/taste-skill/scripts/consistency.mjs:9593— consistency.moreFindings has cyclomatic complexity 101 (threshold 15). Of this number, 82 points are the body's own statements and 19 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.copyChecks (cyclomatic 99) skills/taste-skill/scripts/consistency.mjs:9397— consistency.copyChecks has cyclomatic complexity 99 (threshold 15). Of this number, 74 points are the body's own statements and 25 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.helperLib (cyclomatic 97) skills/taste-skill/scripts/consistency.mjs:8994— consistency.helperLib has cyclomatic complexity 97 (threshold 15). Of this number, 46 points are the body's own statements and 51 belong to 14 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.hiddenProbe (cyclomatic 94) skills/taste-skill/scripts/consistency.mjs:9963— consistency.hiddenProbe has cyclomatic complexity 94 (threshold 15). Of this number, 74 points are the body's own statements and 20 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.extrasFindings (cyclomatic 91) skills/taste-skill/scripts/consistency.mjs:9524— consistency.extrasFindings has cyclomatic complexity 91 (threshold 15). Of this number, 74 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ui.loop (cyclomatic 77) skills/taste-skill/assets/ui/ui.js:329— ui.loop has cyclomatic complexity 77 (threshold 15). Of this number, 31 points are the body's own statements and 46 belong to 11 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.
photos.fetchCmd (cyclomatic 74) skills/taste-skill/scripts/photos.mjs:852— photos.fetchCmd has cyclomatic complexity 74 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
diagram.makeNode (cyclomatic 72) skills/taste-skill/assets/diagrams/diagram.js:352— diagram.makeNode has cyclomatic complexity 72 (threshold 15). Of this number, 66 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
icons.fetchCmd (cyclomatic 71) skills/taste-skill/scripts/icons.mjs:310— icons.fetchCmd has cyclomatic complexity 71 (threshold 15). Of this number, 68 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
moments.cmdShoot (cyclomatic 69) skills/taste-skill/scripts/moments.mjs:333— moments.cmdShoot has cyclomatic complexity 69 (threshold 15). Of this number, 50 points are the body's own statements and 19 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.
pick (cyclomatic 63) skills/taste-skill/assets/effects/pick.js:88— pick has cyclomatic complexity 63 (threshold 15). Of this number, 41 points are the body's own statements and 22 belong to 26 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.
photos.searchCmd (cyclomatic 59) skills/taste-skill/scripts/photos.mjs:654— photos.searchCmd has cyclomatic complexity 59 (threshold 15). Of this number, 54 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
lib.scene (cyclomatic 58) skills/taste-skill/assets/scenes/lib.js:113— lib.scene has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 7 of the 58 points are its own statements and the rest belongs to 13 function items inside it that branch (build, step, toRest, …). 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.
build.checkSpec (cyclomatic 57) skills/taste-skill/assets/objects/product-render/build.js:763— build.checkSpec has cyclomatic complexity 57 (threshold 15). Of this number, 46 points are the body's own statements and 11 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.
copy-lint.readHtml (cyclomatic 57) skills/taste-skill/scripts/copy-lint.mjs:79— copy-lint.readHtml has cyclomatic complexity 57 (threshold 15). Of this number, 53 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
perf.analyse (cyclomatic 55) skills/taste-skill/scripts/perf.mjs:256— perf.analyse has cyclomatic complexity 55 (threshold 15). Of this number, 24 points are the body's own statements and 31 belong to 18 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.
object.cutOut (cyclomatic 54) skills/taste-skill/assets/objects/dot-object/object.js:77— object.cutOut has cyclomatic complexity 54 (threshold 15). Of this number, 21 points are the body's own statements and 33 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
consistency.auditFindings (cyclomatic 54) skills/taste-skill/scripts/consistency.mjs:9485— consistency.auditFindings has cyclomatic complexity 54 (threshold 15). Of this number, 45 points are the body's own statements and 9 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
icons.resolve (cyclomatic 51) skills/taste-skill/scripts/icons.mjs:239— icons.resolve has cyclomatic complexity 51 (threshold 15). Of this number, 50 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.
moments.cmdCheck (cyclomatic 50) skills/taste-skill/scripts/moments.mjs:503— moments.cmdCheck has cyclomatic complexity 50 (threshold 15). Of this number, 48 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.
copy-lint.lintRead (cyclomatic 46) skills/taste-skill/scripts/copy-lint.mjs:270— copy-lint.lintRead has cyclomatic complexity 46 (threshold 15). Of this number, 44 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pick.deal (cyclomatic 44) skills/taste-skill/assets/backgrounds/pick.mjs:66— pick.deal has cyclomatic complexity 44 (threshold 15). Of this number, 32 points are the body's own statements and 12 belong to 6 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.
diagram.normalise (cyclomatic 44) skills/taste-skill/assets/diagrams/diagram.js:250— diagram.normalise has cyclomatic complexity 44 (threshold 15). Of this number, 25 points are the body's own statements and 19 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.
init (cyclomatic 44) skills/taste-skill/assets/ui/pipeline-board/fragment.js:25— init has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 11 of the 44 points are its own statements and the rest belongs to 25 function items inside it that branch (paint, a function literal at line 63, tick, …). 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.
component.init::draw::layout (cyclomatic 43) skills/taste-skill/assets/components/fx-map/component.js:111— component.init::draw::layout has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.mountProduct (cyclomatic 43) skills/taste-skill/assets/objects/product-render/build.js:1146— build.mountProduct has cyclomatic complexity 43 (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: 2 other methods here (build.mountProduct::renderStill, build.mountProduct::show) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
icons.contentBox (cyclomatic 43) skills/taste-skill/scripts/icons.mjs:211— icons.contentBox has cyclomatic complexity 43 (threshold 15). Of this number, 20 points are the body's own statements and 23 belong to 10 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.
icons.checkCmd (cyclomatic 43) skills/taste-skill/scripts/icons.mjs:439— icons.checkCmd has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
photos.list (cyclomatic 43) skills/taste-skill/scripts/photos.mjs:748— photos.list has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mountPrint::render (cyclomatic 42) skills/taste-skill/assets/objects/_print-core/print3d.js:1433— mountPrint::render has cyclomatic complexity 42 (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.
diagram.kindOf (cyclomatic 40) skills/taste-skill/assets/diagrams/diagram.js:319— diagram.kindOf 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.
photo.photoGL (cyclomatic 40) skills/taste-skill/assets/objects/photo-kit/photo.js:582— photo.photoGL has cyclomatic complexity 40 (threshold 15). Of this number, 32 points are the body's own statements and 8 belong to 6 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.
consistency.narrowProbe (cyclomatic 40) skills/taste-skill/scripts/consistency.mjs:11257— consistency.narrowProbe has cyclomatic complexity 40 (threshold 15). Of this number, 24 points are the body's own statements and 16 belong to 4 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
moments.deal (cyclomatic 40) skills/taste-skill/scripts/moments.mjs:193— moments.deal has cyclomatic complexity 40 (threshold 15). Of this number, 19 points are the body's own statements and 21 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.
effect.makeTones (cyclomatic 38) skills/taste-skill/assets/effects/duotone-grade/effect.js:225— effect.makeTones has cyclomatic complexity 38 (threshold 15). Of this number, 37 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.
print3d.glslProblems (cyclomatic 38) skills/taste-skill/assets/objects/_print-core/print3d.js:115— print3d.glslProblems has cyclomatic complexity 38 (threshold 15). Of this number, 27 points are the body's own statements and 11 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.
materialGlsl (cyclomatic 37) skills/taste-skill/assets/objects/product-render/build.js:103— materialGlsl has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
localSamples (cyclomatic 37) skills/taste-skill/assets/objects/product-render/build.js:421— localSamples has cyclomatic complexity 37 (threshold 15). Of this number, 35 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.
Diagram.build::attempt (cyclomatic 36) skills/taste-skill/assets/diagrams/diagram.js:1214— Diagram.build::attempt 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. This shape REPEATS in the file: one other method here (Diagram.build) 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.
consistency.copyTerms (cyclomatic 36) skills/taste-skill/scripts/consistency.mjs:9365— consistency.copyTerms 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
moments.validate (cyclomatic 36) skills/taste-skill/scripts/moments.mjs:94— moments.validate 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.
gate.copyChecks (cyclomatic 36) skills/taste-skill/scripts/gate.mjs:391— gate.copyChecks has cyclomatic complexity 36 (threshold 15). Of this number, 30 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
fx.lifecycle (cyclomatic 35) skills/taste-skill/assets/effects/fx.js:317— fx.lifecycle has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 6 function items inside it that branch (running, loop, sync, …). 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.
effect.tones (cyclomatic 35) skills/taste-skill/assets/effects/soft-light-bars/effect.js:172— effect.tones has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
print3d.mountPrint (cyclomatic 35) skills/taste-skill/assets/objects/_print-core/print3d.js:971— print3d.mountPrint has cyclomatic complexity 35 (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: 4 other methods here (print3d.mountPrint::drawPoster, print3d.mountPrint::fit, print3d.mountPrint::advance, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 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.
gate.browserChecks (cyclomatic 35) skills/taste-skill/scripts/gate.mjs:483— gate.browserChecks 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 35) · ×1
mount (cyclomatic 35) skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:27— mount has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (update, measure, rest, …). 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.
icons.measureCmd (cyclomatic 34) skills/taste-skill/scripts/icons.mjs:492— icons.measureCmd has cyclomatic complexity 34 (threshold 15). Of this number, 21 points are the body's own statements and 13 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
kit.glslLint (cyclomatic 32) skills/taste-skill/assets/objects/_scenes/kit.js:388— kit.glslLint has cyclomatic complexity 32 (threshold 15). Of this number, 27 points are the body's own statements and 5 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.
system.forms (cyclomatic 32) skills/taste-skill/assets/system.js:249— system.forms has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 281, 256, 250, …). 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.
gate.applyWaivers (cyclomatic 32) skills/taste-skill/scripts/gate.mjs:551— gate.applyWaivers has cyclomatic complexity 32 (threshold 15). Of this number, 27 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 32) · ×1
mount (cyclomatic 32) skills/taste-skill/assets/scenes/product-assembles-into-its-action/scene.js:30— mount has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 22 function items inside it that branch (update, rest, a function literal at line 56, …). 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.
effect.mountOne (cyclomatic 31) skills/taste-skill/assets/effects/duotone-grade/effect.js:510— effect.mountOne has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 645, 632, 644, …). 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.
consistency.reducedPass (cyclomatic 31) skills/taste-skill/scripts/consistency.mjs:9900— consistency.reducedPass has cyclomatic complexity 31 (threshold 15). Of this number, 30 points are the body's own statements and 1 belongs 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
component.init (cyclomatic 30) skills/taste-skill/assets/components/fx-progress/component.js:15— component.init has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (tick, resume, a function literal at line 38, …). 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.
shoot.tilesOf (cyclomatic 30) REDACTED:249— shoot.tilesOf 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
visuals (cyclomatic 30) skills/taste-skill/assets/system.js:464— visuals has cyclomatic complexity 30 (threshold 15). Of this number, 16 points are the body's own statements and 14 belong to 15 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 30) · ×1
mount (cyclomatic 30) skills/taste-skill/assets/scenes/dot-becomes-the-full-stop/scene.js:16— mount has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (update, measure, a function literal at line 50, …). 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.
pick.deal.valid (cyclomatic 29) skills/taste-skill/assets/backgrounds/pick.mjs:120— pick.deal.valid has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
effect.tones (cyclomatic 29) skills/taste-skill/assets/effects/dotted-globe/effect.js:314— effect.tones has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs 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.
photo.photoGL.init (cyclomatic 29) skills/taste-skill/assets/objects/photo-kit/photo.js:721— photo.photoGL.init has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 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.
build.resolveSpec (cyclomatic 29) skills/taste-skill/assets/objects/product-render/build.js:638— build.resolveSpec has cyclomatic complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 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.
system.openNow (cyclomatic 29) skills/taste-skill/assets/system.js:203— system.openNow has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 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.
fragment.init (cyclomatic 29) skills/taste-skill/assets/ui/files/fragment.js:8— fragment.init has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (say, clipBox, a function literal at line 36, …). 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.
pausable (cyclomatic 29) skills/taste-skill/assets/ui/ui.js:189— pausable has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 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.
photoGL.init (cyclomatic 29) skills/taste-skill/assets/objects/photo-kit/photo.js:721— photoGL.init has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 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.
shared.still.render (cyclomatic 28) skills/taste-skill/assets/components/shared.js:180— shared.still.render 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
diagram.putIcon (cyclomatic 28) skills/taste-skill/assets/diagrams/diagram.js:199— diagram.putIcon has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 205). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
consistency.glFallbackPass (cyclomatic 28) skills/taste-skill/scripts/consistency.mjs:9758— consistency.glFallbackPass has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
effects.publish (cyclomatic 28) skills/taste-skill/scripts/effects.mjs:300— effects.publish has cyclomatic complexity 28 (threshold 15). Of this number, 26 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.
still.render (cyclomatic 28) skills/taste-skill/assets/components/shared.js:180— still.render has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 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.
component.init (cyclomatic 27) skills/taste-skill/assets/components/fx-search/component.js:15— component.init has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 8 function items inside it that branch (slash, ensure, key, …). 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.
motion.counts (cyclomatic 27) skills/taste-skill/assets/motion/motion.js:124— motion.counts has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 130, 148, 155, …). 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.
photo.photoGL.draw (cyclomatic 27) skills/taste-skill/assets/objects/photo-kit/photo.js:874— photo.photoGL.draw 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.
consistency.hiddenWalk (cyclomatic 27) skills/taste-skill/scripts/consistency.mjs:10044— consistency.hiddenWalk has cyclomatic complexity 27 (threshold 15). Of this number, 26 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
effects.pick (cyclomatic 27) skills/taste-skill/scripts/effects.mjs:194— effects.pick has cyclomatic complexity 27 (threshold 15). Of this number, 26 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.
gate.codeOnly (cyclomatic 27) skills/taste-skill/scripts/gate.mjs:327— gate.codeOnly 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.
photoGL.draw (cyclomatic 27) skills/taste-skill/assets/objects/photo-kit/photo.js:874— photoGL.draw 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.
fragment.init (cyclomatic 26) skills/taste-skill/assets/ui/doc/fragment.js:8— fragment.init has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (place, noteOf, text, …). 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.
effects.validateMeta (cyclomatic 26) skills/taste-skill/scripts/effects.mjs:77— effects.validateMeta has cyclomatic complexity 26 (threshold 15). Of this number, 24 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.
icons.scanCmd (cyclomatic 26) skills/taste-skill/scripts/icons.mjs:562— icons.scanCmd has cyclomatic complexity 26 (threshold 15). Of this number, 14 points are the body's own statements and 12 belong to 2 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.
demo (cyclomatic 26) skills/taste-skill/assets/objects/_scenes/demo.js:15— demo has cyclomatic complexity 26 (threshold 15). Of this number, 16 points are the body's own statements and 10 belong to 19 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.
backgrounds.detect (cyclomatic 25) skills/taste-skill/assets/backgrounds/backgrounds.js:53— backgrounds.detect has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 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.
Diagram.pauseButton (cyclomatic 25) skills/taste-skill/assets/diagrams/diagram.js:1557— Diagram.pauseButton has cyclomatic complexity 25 (threshold 15). 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: 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.
fragment.init (cyclomatic 25) skills/taste-skill/assets/ui/terminal-run/fragment.js:15— fragment.init has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 95, meter, scroll, …). 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.
bake.sea (cyclomatic 24) skills/taste-skill/assets/components/fx-map/bake.mjs:190— bake.sea has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
consistency.narrowPass (cyclomatic 24) skills/taste-skill/scripts/consistency.mjs:11278— consistency.narrowPass 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
gate.refsOf (cyclomatic 24) skills/taste-skill/scripts/gate.mjs:259— gate.refsOf has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 24) · ×1
mount (cyclomatic 24) skills/taste-skill/assets/objects/split-reveal/object.js:92— mount 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.
lib.gl (cyclomatic 23) skills/taste-skill/assets/scenes/lib.js:283— lib.gl has cyclomatic complexity 23 (threshold 15). Of this number, 20 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.
fragment.init (cyclomatic 23) skills/taste-skill/assets/ui/slider/fragment.js:13— fragment.init has cyclomatic complexity 23 (threshold 15). 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: 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.
lockLines (cyclomatic 23) skills/taste-skill/assets/layout/layout.js:130— lockLines 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 14 function items inside it that branch (units::walk, lock, units, …). 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.
mount.step (cyclomatic 23) skills/taste-skill/assets/effects/grid-pulse/effect.js:211— mount.step 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.
resolveView (cyclomatic 23) skills/taste-skill/assets/objects/product-render/build.js:676— resolveView has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity· mount (cyclomatic 23) · ×1
mount (cyclomatic 23) skills/taste-skill/assets/scenes/fly-into-the-shape/scene.js:53— mount has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
deal::valid (cyclomatic 23) skills/taste-skill/assets/backgrounds/pick.mjs:120— deal::valid 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.
Diagram.applyFocus (cyclomatic 22) skills/taste-skill/assets/diagrams/diagram.js:1596— Diagram.applyFocus has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 4 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.
layout.letters (cyclomatic 22) skills/taste-skill/assets/layout/layout.js:76— layout.letters has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (walk, a function literal at line 111, a function literal at line 121, …). 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.
system.actionbar (cyclomatic 22) skills/taste-skill/assets/system.js:344— system.actionbar has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 359, update, set, …). 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.
moments.cmdPick (cyclomatic 22) skills/taste-skill/scripts/moments.mjs:253— moments.cmdPick has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 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.
effects.launch (cyclomatic 22) skills/taste-skill/scripts/effects.mjs:424— effects.launch has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 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.
gate.staticChecks (cyclomatic 22) skills/taste-skill/scripts/gate.mjs:353— gate.staticChecks 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.
shoot.decodePNG (cyclomatic 22) REDACTED:125— shoot.decodePNG 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.
init (cyclomatic 22) skills/taste-skill/assets/ui/stat/fragment.js:10— init has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to 14 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.
Diagram.state (cyclomatic 21) skills/taste-skill/assets/diagrams/diagram.js:1441— Diagram.state has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 1452). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
effect.mountGlobe.drawNetwork (cyclomatic 21) skills/taste-skill/assets/effects/dotted-globe/effect.js:871— effect.mountGlobe.drawNetwork 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.
effect.tones (cyclomatic 21) skills/taste-skill/assets/effects/ruled-grounds/effect.js:89— effect.tones has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
deal.dealOnce (cyclomatic 21) skills/taste-skill/assets/layout/deal.mjs:80— deal.dealOnce has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 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.
build.makeProduct (cyclomatic 21) skills/taste-skill/assets/objects/product-render/build.js:1076— build.makeProduct 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.
fragment.init (cyclomatic 21) skills/taste-skill/assets/ui/calendar/fragment.js:8— fragment.init has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 54, show, still, …). 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.
consistency.lintGLSL (cyclomatic 21) skills/taste-skill/scripts/consistency.mjs:9708— consistency.lintGLSL 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 one function literal inside it that branches (line 9717). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.slowPass (cyclomatic 21) skills/taste-skill/scripts/consistency.mjs:9814— consistency.slowPass has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
start.hueWord (cyclomatic 21) skills/taste-skill/scripts/start.mjs:143— start.hueWord 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.
D1 · Cyclomatic Complexity· enter (cyclomatic 21) · ×1
enter (cyclomatic 21) skills/taste-skill/assets/motion/motion.js:331— enter has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 14 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.
mountGlobe.drawNetwork (cyclomatic 21) skills/taste-skill/assets/effects/dotted-globe/effect.js:871— mountGlobe.drawNetwork 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.
mount.draw (cyclomatic 21) skills/taste-skill/assets/effects/ridgeline/effect.js:331— mount.draw 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.
demo (cyclomatic 21) skills/taste-skill/assets/objects/_print-core/demo.js:18— demo has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 8 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.
fx.shader.draw (cyclomatic 20) skills/taste-skill/assets/effects/fx.js:730— fx.shader.draw 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.
effect.mountOne.start (cyclomatic 20) skills/taste-skill/assets/effects/duotone-grade/effect.js:572— effect.mountOne.start has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (graded, a function literal at line 580, a function literal at line 589, …). 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.
effect.tones (cyclomatic 20) skills/taste-skill/assets/effects/film-light-leak/effect.js:106— effect.tones 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.
scene.placePath (cyclomatic 20) skills/taste-skill/assets/scenes/fly-into-the-shape/scene.js:34— scene.placePath 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.
consistency.sweepWidth (cyclomatic 20) skills/taste-skill/scripts/consistency.mjs:11218— consistency.sweepWidth has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 2 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. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
perf.measure (cyclomatic 20) skills/taste-skill/scripts/perf.mjs:197— perf.measure has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 203, 217). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
shader.draw (cyclomatic 20) skills/taste-skill/assets/effects/fx.js:730— shader.draw 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.
mountOne.start (cyclomatic 20) skills/taste-skill/assets/effects/duotone-grade/effect.js:572— mountOne.start has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (fallback, a function literal at line 604, graded, …). 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.
mount.drawPulse (cyclomatic 20) skills/taste-skill/assets/effects/grid-pulse/effect.js:293— mount.drawPulse 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.
auto.mountAll (cyclomatic 19) skills/taste-skill/assets/objects/_scenes/auto.js:41— auto.mountAll has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 57, 54). 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.
consistency.shaderLint (cyclomatic 19) skills/taste-skill/scripts/consistency.mjs:9733— consistency.shaderLint 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, separate the cases: extract each independent 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 file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
effects.buildIndex (cyclomatic 19) skills/taste-skill/scripts/effects.mjs:109— effects.buildIndex 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.
gate.findPage (cyclomatic 19) skills/taste-skill/scripts/gate.mjs:242— gate.findPage 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.
icons.listCmd (cyclomatic 19) skills/taste-skill/scripts/icons.mjs:420— icons.listCmd has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
photos.creditsCmd (cyclomatic 19) skills/taste-skill/scripts/photos.mjs:991— photos.creditsCmd 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, 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.
start.tokens (cyclomatic 19) skills/taste-skill/scripts/start.mjs:166— start.tokens 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.
D1 · Cyclomatic Complexity· mind (cyclomatic 19) · ×1
mind (cyclomatic 19) skills/taste-skill/assets/diagrams/diagram.js:782— mind has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 807, 800, 805, …). 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.
demo (cyclomatic 19) skills/taste-skill/assets/objects/photo-kit/demo.js:17— demo has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 14 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.
shared.pauser (cyclomatic 18) skills/taste-skill/assets/components/shared.js:485— shared.pauser has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 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.
bake.chains (cyclomatic 18) skills/taste-skill/assets/components/fx-map/bake.mjs:161— bake.chains has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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.
effect.mountAscii.draw (cyclomatic 18) skills/taste-skill/assets/effects/ascii-shade/effect.js:297— effect.mountAscii.draw 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.
effect.mountGlobe (cyclomatic 18) skills/taste-skill/assets/effects/dotted-globe/effect.js:450— effect.mountGlobe 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.
effect.layout (cyclomatic 18) skills/taste-skill/assets/effects/duotone-grade/effect.js:321— effect.layout 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 items inside it that branch (fit::shrink, a function literal at line 356, place, …). 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.
photo.blueNoise (cyclomatic 18) skills/taste-skill/assets/objects/photo-kit/photo.js:255— photo.blueNoise has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
kit.photoURL (cyclomatic 18) skills/taste-skill/assets/objects/_scenes/kit.js:132— kit.photoURL 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.
kit.stage (cyclomatic 18) skills/taste-skill/assets/objects/_scenes/kit.js:475— kit.stage 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. This shape REPEATS in the file: 2 other methods here (kit.stage::draw, kit.stage::syncPause) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
mountAscii (cyclomatic 18) skills/taste-skill/assets/effects/ascii-shade/effect.js:101— mountAscii has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 10 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.
mountAscii.draw (cyclomatic 18) skills/taste-skill/assets/effects/ascii-shade/effect.js:297— mountAscii.draw 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.
creditsBlock (cyclomatic 18) skills/taste-skill/assets/objects/photo-kit/photo.js:1125— creditsBlock has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 1131, srcOf, a function literal at line 1126, …). 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.
check.decodePNG (cyclomatic 17) skills/taste-skill/assets/backgrounds/check.mjs:49— check.decodePNG 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.
fx.shader.init (cyclomatic 17) skills/taste-skill/assets/effects/fx.js:658— fx.shader.init 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, 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.
effect.mountGlobe.fit (cyclomatic 17) skills/taste-skill/assets/effects/dotted-globe/effect.js:679— effect.mountGlobe.fit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
effect.mountGlobe.draw (cyclomatic 17) skills/taste-skill/assets/effects/dotted-globe/effect.js:922— effect.mountGlobe.draw 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.
effect.uniforms (cyclomatic 17) skills/taste-skill/assets/effects/film-light-leak/effect.js:165— effect.uniforms 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.
ui.bakeDraw (cyclomatic 17) skills/taste-skill/assets/ui/ui.js:593— ui.bakeDraw has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ui.grounds (cyclomatic 17) skills/taste-skill/assets/ui/ui.js:701— ui.grounds 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.
photo.photoPalette (cyclomatic 17) skills/taste-skill/assets/objects/photo-kit/photo.js:178— photo.photoPalette has cyclomatic complexity 17 (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.
photo.photoGL.step (cyclomatic 17) skills/taste-skill/assets/objects/photo-kit/photo.js:838— photo.photoGL.step 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.
consistency.sameFault (cyclomatic 17) skills/taste-skill/scripts/consistency.mjs:10208— consistency.sameFault has cyclomatic complexity 17 (threshold 15). 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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 86 of the 266 methods over the threshold — including the worst — and 3606 of the 6381 points over it (57%), 12.5× the next-largest file (skills/taste-skill/assets/diagrams/diagram.js at 289). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
icons.findCmd (cyclomatic 17) skills/taste-skill/scripts/icons.mjs:398— icons.findCmd has cyclomatic complexity 17 (threshold 15). Of this number, 13 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.
hub.link (cyclomatic 17) skills/taste-skill/assets/diagrams/diagram.js:724— hub.link 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.
shader.init (cyclomatic 17) skills/taste-skill/assets/effects/fx.js:658— shader.init has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mountGlobe.fit (cyclomatic 17) skills/taste-skill/assets/effects/dotted-globe/effect.js:679— mountGlobe.fit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
mountGlobe.draw (cyclomatic 17) skills/taste-skill/assets/effects/dotted-globe/effect.js:922— mountGlobe.draw 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.
photoGL.step (cyclomatic 17) skills/taste-skill/assets/objects/photo-kit/photo.js:838— photoGL.step 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.
component.init (cyclomatic 16) skills/taste-skill/assets/components/fx-tabs/component.js:8— component.init has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (key, place, a function literal at line 31, …). 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.
fonts.html.fontLink (cyclomatic 16) skills/taste-skill/assets/layout/fonts.html:65— fonts.html.fontLink has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (add, add::put). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ui.sweep (cyclomatic 16) skills/taste-skill/assets/ui/ui.js:253— ui.sweep has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
fragment.init.sync (cyclomatic 16) skills/taste-skill/assets/ui/voice/fragment.js:37— fragment.init.sync 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.
lanes (cyclomatic 16) skills/taste-skill/assets/diagrams/diagram.js:532— lanes has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 16 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.
hub (cyclomatic 16) skills/taste-skill/assets/diagrams/diagram.js:668— hub has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 17 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.
bindCard (cyclomatic 16) skills/taste-skill/assets/diagrams/diagram.js:1128— bindCard has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (onEnter, onFocus, onLeave). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
scene::build (cyclomatic 16) skills/taste-skill/assets/scenes/lib.js:169— scene::build 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.
D1 · Cyclomatic Complexity· mount (cyclomatic 16) · ×1
mount (cyclomatic 16) skills/taste-skill/assets/scenes/fixed-hero-object/scene.js:32— mount has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 43, near, a function literal at line 63, …). 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.
init.sync (cyclomatic 16) skills/taste-skill/assets/ui/voice/fragment.js:37— init.sync 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.
consistency.runWidth (cognitive 1499) skills/taste-skill/scripts/consistency.mjs:10219— consistency.runWidth has cognitive complexity 1499 (threshold 15). Drivers by points: if/else 240 (552 pts), ternaries 152 (458 pts), boolean chains 271, loops 107 (215 pts), error handling 3 (nesting depth added 726). Of this number, 1260 points are the body's own statements and 239 belong to 77 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
photos.pick (cognitive 262) skills/taste-skill/scripts/photos.mjs:317— photos.pick has cognitive complexity 262 (threshold 15). Drivers by points: if/else 93 (183 pts), boolean chains 113, ternaries 47 (98 pts), loops 16 (45 pts), error handling 1 (2 pts) (nesting depth added 171). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (photos.pick::chooseLead) 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.
lyCheck (cognitive 200) skills/taste-skill/assets/layout/layout-check.js:34— lyCheck has cognitive complexity 200 (threshold 15). Drivers by points: if/else 51 (93 pts), boolean chains 66, ternaries 21 (27 pts), loops 10 (13 pts), other 1 (nesting depth added 51). Of this number, 95 points are the body's own statements and 105 belong to 45 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.
build (cognitive 192) skills/taste-skill/assets/objects/product-render/build.js:812— build has cognitive complexity 192 (threshold 15). Drivers by points: loops 23 (54 pts), ternaries 37 (54 pts), boolean chains 46, if/else 22 (30 pts), other 8 (nesting depth added 56). Of this number, 127 points are the body's own statements and 65 belong to 29 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.
build (cognitive 139) skills/taste-skill/assets/diagrams/diagram.js:1174— build has cognitive complexity 139 (threshold 15). Drivers by points: boolean chains 67, if/else 35 (55 pts), ternaries 40 (55 pts), loops 9 (13 pts), other 2, error handling 1 (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.
consistency.moreFindings (cognitive 136) skills/taste-skill/scripts/consistency.mjs:9593— consistency.moreFindings has cognitive complexity 136 (threshold 15). Drivers by points: ternaries 25 (59 pts), if/else 22 (37 pts), boolean chains 33, loops 4 (7 pts) (nesting depth added 52). Of this number, 110 points are the body's own statements and 26 belong to 8 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.hiddenProbe (cognitive 127) skills/taste-skill/scripts/consistency.mjs:9963— consistency.hiddenProbe has cognitive complexity 127 (threshold 15). Drivers by points: if/else 29 (71 pts), boolean chains 35, loops 6 (10 pts), ternaries 4 (7 pts), error handling 1 (4 pts) (nesting depth added 52). Of this number, 103 points are the body's own statements and 24 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.copyChecks (cognitive 124) skills/taste-skill/scripts/consistency.mjs:9397— consistency.copyChecks has cognitive complexity 124 (threshold 15). Drivers by points: if/else 24 (42 pts), boolean chains 40, ternaries 12 (32 pts), loops 8 (10 pts) (nesting depth added 40). Of this number, 107 points are the body's own statements and 17 belong to 5 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
copy-lint.readHtml (cognitive 118) skills/taste-skill/scripts/copy-lint.mjs:79— copy-lint.readHtml has cognitive complexity 118 (threshold 15). Drivers by points: if/else 38 (100 pts), boolean chains 14, ternaries 2 (3 pts), loops 1 (nesting depth added 63). Of this number, 113 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
moments.cmdShoot (cognitive 116) skills/taste-skill/scripts/moments.mjs:333— moments.cmdShoot has cognitive complexity 116 (threshold 15). Drivers by points: ternaries 15 (41 pts), if/else 16 (26 pts), boolean chains 24, error handling 7 (13 pts), loops 5 (12 pts) (nesting depth added 49). Of this number, 96 points are the body's own statements and 20 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.
consistency.extrasFindings (cognitive 112) skills/taste-skill/scripts/consistency.mjs:9524— consistency.extrasFindings has cognitive complexity 112 (threshold 15). Drivers by points: ternaries 29 (54 pts), boolean chains 24, if/else 16 (21 pts), loops 12 (13 pts) (nesting depth added 31). Of this number, 98 points are the body's own statements and 14 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
icons.fetchCmd (cognitive 112) skills/taste-skill/scripts/icons.mjs:310— icons.fetchCmd has cognitive complexity 112 (threshold 15). Drivers by points: ternaries 22 (57 pts), boolean chains 26, if/else 16 (25 pts), error handling 2 (3 pts), loops 1 (nesting depth added 45). Of this number, 104 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
photos.fetchCmd (cognitive 111) skills/taste-skill/scripts/photos.mjs:852— photos.fetchCmd has cognitive complexity 111 (threshold 15). Drivers by points: if/else 26 (54 pts), ternaries 12 (31 pts), boolean chains 13, loops 4 (10 pts), error handling 2 (3 pts) (nesting depth added 54). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
consistency.auditFindings (cognitive 103) skills/taste-skill/scripts/consistency.mjs:9485— consistency.auditFindings has cognitive complexity 103 (threshold 15). Drivers by points: ternaries 16 (43 pts), if/else 12 (24 pts), loops 14 (24 pts), boolean chains 12 (nesting depth added 49). Of this number, 94 points are the body's own statements and 9 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
build.checkSpec (cognitive 100) skills/taste-skill/assets/objects/product-render/build.js:763— build.checkSpec has cognitive complexity 100 (threshold 15). Drivers by points: if/else 19 (46 pts), boolean chains 27, loops 8 (23 pts), error handling 1 (3 pts), ternaries 1 (nesting depth added 44). Of this number, 90 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
consistency.copyTerms (cognitive 92) skills/taste-skill/scripts/consistency.mjs:9365— consistency.copyTerms has cognitive complexity 92 (threshold 15). Drivers by points: if/else 14 (52 pts), loops 12 (33 pts), boolean chains 7 (nesting depth added 59). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
makeNode (cognitive 90) skills/taste-skill/assets/diagrams/diagram.js:352— makeNode has cognitive complexity 90 (threshold 15). Drivers by points: if/else 30 (49 pts), boolean chains 26, ternaries 8 (15 pts) (nesting depth added 26). Of this number, 81 points are the body's own statements and 9 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.
pick (cognitive 90) skills/taste-skill/assets/effects/pick.js:88— pick has cognitive complexity 90 (threshold 15). Drivers by points: if/else 21 (37 pts), ternaries 16 (24 pts), boolean chains 19, loops 5 (9 pts), other 1 (nesting depth added 28). Of this number, 59 points are the body's own statements and 31 belong to 26 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.
photos.searchCmd (cognitive 85) skills/taste-skill/scripts/photos.mjs:654— photos.searchCmd has cognitive complexity 85 (threshold 15). Drivers by points: if/else 14 (30 pts), ternaries 11 (22 pts), boolean chains 19, error handling 3 (8 pts), loops 4 (6 pts) (nesting depth added 34). Of this number, 82 points are the body's own statements and 3 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.
start.hueWord (cognitive 84) skills/taste-skill/scripts/start.mjs:143— start.hueWord has cognitive complexity 84 (threshold 15). Drivers by points: ternaries 18 (82 pts), boolean chains 1, if/else 1 (nesting depth added 64). 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.
loop (cognitive 83) skills/taste-skill/assets/ui/ui.js:329— loop has cognitive complexity 83 (threshold 15). Drivers by points: if/else 40 (54 pts), boolean chains 18, ternaries 5, error handling 2 (3 pts), loops 3 (nesting depth added 15). Most of this is not in the body itself: 7 of the 83 points are its own statements and the rest belongs to 44 function items inside it that branch (a function literal at line 480, tween::(anonymous)::step, a function literal at line 417, …). 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.
moments.cmdCheck (cognitive 77) skills/taste-skill/scripts/moments.mjs:503— moments.cmdCheck has cognitive complexity 77 (threshold 15). Drivers by points: if/else 22 (45 pts), boolean chains 15, ternaries 4 (12 pts), loops 4 (5 pts) (nesting depth added 32). Of this number, 72 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
photos.list (cognitive 74) skills/taste-skill/scripts/photos.mjs:748— photos.list has cognitive complexity 74 (threshold 15). Drivers by points: ternaries 25 (54 pts), boolean chains 8, if/else 5 (6 pts), loops 3 (6 pts) (nesting depth added 33). Of this number, 72 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.
makeTones (cognitive 73) skills/taste-skill/assets/effects/duotone-grade/effect.js:225— makeTones has cognitive complexity 73 (threshold 15). Drivers by points: ternaries 12 (34 pts), if/else 21 (32 pts), boolean chains 6, loops 1 (nesting depth added 33). Of this number, 72 points are the body's own statements and 1 belongs 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.
icons.checkCmd (cognitive 67) skills/taste-skill/scripts/icons.mjs:439— icons.checkCmd has cognitive complexity 67 (threshold 15). Drivers by points: if/else 22 (48 pts), boolean chains 13, loops 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tones (cognitive 64) skills/taste-skill/assets/effects/soft-light-bars/effect.js:172— tones has cognitive complexity 64 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 10 (19 pts), loops 7 (19 pts), boolean chains 6 (nesting depth added 33). Of this number, 61 points are the body's own statements and 3 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.
lib.scene (cognitive 62) skills/taste-skill/assets/scenes/lib.js:113— lib.scene has cognitive complexity 62 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 18, error handling 7 (10 pts), ternaries 5 (8 pts) (nesting depth added 8). Most of this is not in the body itself: 6 of the 62 points are its own statements and the rest belongs to 13 function items inside it that branch (build, step, toRest, …). 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.
consistency.reducedPass (cognitive 60) skills/taste-skill/scripts/consistency.mjs:9900— consistency.reducedPass has cognitive complexity 60 (threshold 15). Drivers by points: if/else 8 (22 pts), ternaries 6 (18 pts), loops 7 (11 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 32). Of this number, 58 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
copy-lint.lintRead (cognitive 60) skills/taste-skill/scripts/copy-lint.mjs:270— copy-lint.lintRead has cognitive complexity 60 (threshold 15). Drivers by points: if/else 27 (35 pts), ternaries 6 (10 pts), boolean chains 8, loops 4 (7 pts) (nesting depth added 15). Of this number, 58 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.
icons.contentBox (cognitive 60) skills/taste-skill/scripts/icons.mjs:211— icons.contentBox has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 5 (21 pts), loops 9 (19 pts), if/else 10 (14 pts), boolean chains 6 (nesting depth added 30). Of this number, 25 points are the body's own statements and 35 belong to 10 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.
print3d.glslProblems (cognitive 58) skills/taste-skill/assets/objects/_print-core/print3d.js:115— print3d.glslProblems has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (37 pts), boolean chains 13, loops 5 (8 pts) (nesting depth added 23). Of this number, 45 points are the body's own statements and 13 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.
normalise (cognitive 57) skills/taste-skill/assets/diagrams/diagram.js:250— normalise has cognitive complexity 57 (threshold 15). Drivers by points: boolean chains 17, ternaries 10 (17 pts), if/else 13 (15 pts), loops 5 (8 pts) (nesting depth added 12). Of this number, 30 points are the body's own statements and 27 belong to 15 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.
mountOne (cognitive 57) skills/taste-skill/assets/effects/duotone-grade/effect.js:510— mountOne has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (31 pts), ternaries 5 (10 pts), boolean chains 9, error handling 3 (7 pts) (nesting depth added 27). Most of this is not in the body itself: 14 of the 57 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 645, 632, 644, …). 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.
consistency.hiddenWalk (cognitive 54) skills/taste-skill/scripts/consistency.mjs:10044— consistency.hiddenWalk has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 11 (33 pts), if/else 7 (12 pts), loops 4 (6 pts), boolean chains 2, error handling 1 (nesting depth added 29). Of this number, 53 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
init::draw::layout (cognitive 54) skills/taste-skill/assets/components/fx-map/component.js:111— init::draw::layout has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 9, ternaries 7 (8 pts), loops 2 (4 pts), error handling 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pick.deal (cognitive 51) skills/taste-skill/assets/backgrounds/pick.mjs:66— pick.deal has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 16, ternaries 7 (9 pts), loops 4 (6 pts) (nesting depth added 12). Of this number, 39 points are the body's own statements and 12 belong to 6 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.
icons.resolve (cognitive 51) skills/taste-skill/scripts/icons.mjs:239— icons.resolve has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 16, ternaries 13 (16 pts) (nesting depth added 8). Of this number, 50 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.
consistency.glFallbackPass (cognitive 49) skills/taste-skill/scripts/consistency.mjs:9758— consistency.glFallbackPass has cognitive complexity 49 (threshold 15). Drivers by points: if/else 6 (19 pts), ternaries 3 (14 pts), boolean chains 11, loops 2 (4 pts), error handling 1 (nesting depth added 26). Of this number, 43 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
gate.refsOf (cognitive 48) skills/taste-skill/scripts/gate.mjs:259— gate.refsOf has cognitive complexity 48 (threshold 15). Drivers by points: loops 9 (24 pts), if/else 9 (18 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 25). Of this number, 43 points are the body's own statements and 5 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.
gate.browserChecks (cognitive 48) skills/taste-skill/scripts/gate.mjs:483— gate.browserChecks has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 15, ternaries 8 (12 pts), if/else 9 (11 pts), loops 3 (9 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pausable (cognitive 47) skills/taste-skill/assets/ui/ui.js:189— pausable has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (28 pts), ternaries 7 (12 pts), boolean chains 7 (nesting depth added 20). Of this number, 34 points are the body's own statements and 13 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.
fragment.init (cognitive 46) skills/taste-skill/assets/ui/pipeline-board/fragment.js:25— fragment.init has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 15 (24 pts), if/else 14, boolean chains 7, loops 1 (nesting depth added 9). Most of this is not in the body itself: 9 of the 46 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 63, paint, tick, …). 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.
mount.step (cognitive 46) skills/taste-skill/assets/effects/grid-pulse/effect.js:211— mount.step has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 7 (19 pts), boolean chains 2, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gate.copyChecks (cognitive 45) skills/taste-skill/scripts/gate.mjs:391— gate.copyChecks has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 17, ternaries 8 (14 pts), if/else 5 (8 pts), loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 12). Of this number, 37 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.
bake.sea (cognitive 44) skills/taste-skill/assets/components/fx-map/bake.mjs:190— bake.sea has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 6 (12 pts), boolean chains 5 (nesting depth added 21). Of this number, 41 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.
perf.analyse (cognitive 44) skills/taste-skill/scripts/perf.mjs:256— perf.analyse has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 24, if/else 14, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 21 points are the body's own statements and 23 belong to 18 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.
tones (cognitive 42) skills/taste-skill/assets/effects/dotted-globe/effect.js:314— tones has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 13 (24 pts), if/else 7 (10 pts), boolean chains 8 (nesting depth added 14). Of this number, 41 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.
localSamples (cognitive 42) skills/taste-skill/assets/objects/product-render/build.js:421— localSamples has cognitive complexity 42 (threshold 15). Drivers by points: loops 10 (24 pts), other 11, ternaries 2 (4 pts), if/else 1 (2 pts), match/switch 1 (nesting depth added 17). Of this number, 40 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.
consistency.narrowProbe (cognitive 41) skills/taste-skill/scripts/consistency.mjs:11257— consistency.narrowProbe has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 14, loops 5, ternaries 1 (2 pts), error handling 1 (nesting depth added 10). Of this number, 27 points are the body's own statements and 14 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
build::attempt (cognitive 41) skills/taste-skill/assets/diagrams/diagram.js:1214— build::attempt has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 12, if/else 5 (9 pts), loops 3, error handling 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.
photoGL (cognitive 41) skills/taste-skill/assets/objects/photo-kit/photo.js:582— photoGL has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 18, if/else 11 (15 pts), other 3, ternaries 3, error handling 1 (2 pts) (nesting depth added 5). Of this number, 25 points are the body's own statements and 16 belong to 13 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.
resolveSpec (cognitive 41) skills/taste-skill/assets/objects/product-render/build.js:638— resolveSpec has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 7 (17 pts), boolean chains 13, if/else 7 (11 pts) (nesting depth added 14). Of this number, 22 points are the body's own statements and 19 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.
kit.glslLint (cognitive 40) skills/taste-skill/assets/objects/_scenes/kit.js:388— kit.glslLint has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 9, loops 4 (5 pts), ternaries 1 (nesting depth added 11). Of this number, 35 points are the body's own statements and 5 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.
build.mountProduct (cognitive 40) skills/taste-skill/assets/objects/product-render/build.js:1146— build.mountProduct has cognitive complexity 40 (threshold 15). Drivers by points: if/else 57 (76 pts), boolean chains 51, ternaries 16 (17 pts), loops 3 (4 pts), error handling 2 (3 pts) (nesting depth added 22). 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: 2 other methods here (build.mountProduct::renderStill, build.mountProduct::measureStill) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
moments.deal (cognitive 40) skills/taste-skill/scripts/moments.mjs:193— moments.deal has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 15, loops 3 (4 pts), ternaries 2 (4 pts) (nesting depth added 8). Of this number, 25 points are the body's own statements and 15 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.
diagram.kindOf (cognitive 39) skills/taste-skill/assets/diagrams/diagram.js:319— diagram.kindOf has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 8 (18 pts), boolean chains 13, if/else 6 (7 pts), match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
placePath (cognitive 39) skills/taste-skill/assets/scenes/fly-into-the-shape/scene.js:34— placePath has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 9 (27 pts), if/else 5 (7 pts), boolean chains 4, loops 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.
gate.applyWaivers (cognitive 38) skills/taste-skill/scripts/gate.mjs:551— gate.applyWaivers has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 13, ternaries 3 (6 pts), loops 2 (nesting depth added 10). Of this number, 35 points are the body's own statements and 3 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.
effects.publish (cognitive 37) skills/taste-skill/scripts/effects.mjs:300— effects.publish has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 6, loops 4 (5 pts), ternaries 2 (3 pts) (nesting depth added 12). Of this number, 35 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.
gate.codeOnly (cognitive 37) skills/taste-skill/scripts/gate.mjs:327— gate.codeOnly has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 9, loops 3 (7 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gate.staticChecks (cognitive 37) skills/taste-skill/scripts/gate.mjs:353— gate.staticChecks has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 4 (6 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
icons.scanCmd (cognitive 37) skills/taste-skill/scripts/icons.mjs:562— icons.scanCmd has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 7 (13 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 13). Of this number, 23 points are the body's own statements and 14 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.
openNow (cognitive 37) skills/taste-skill/assets/system.js:203— openNow has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 7 (10 pts), boolean chains 9, loops 2 (3 pts), error handling 1 (nesting depth added 12). Of this number, 23 points are the body's own statements and 14 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.
photoGL.init (cognitive 37) skills/taste-skill/assets/objects/photo-kit/photo.js:721— photoGL.init has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 5, loops 2 (4 pts), ternaries 3 (nesting depth added 12). Of this number, 30 points are the body's own statements and 7 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.
effects.validateMeta (cognitive 36) skills/taste-skill/scripts/effects.mjs:77— effects.validateMeta has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 9, loops 6 (8 pts), ternaries 1 (nesting depth added 10). Of this number, 34 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
effects.buildIndex (cognitive 36) skills/taste-skill/scripts/effects.mjs:109— effects.buildIndex has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (24 pts), error handling 2 (5 pts), boolean chains 4, loops 2, 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.
shared.still.render (cognitive 35) skills/taste-skill/assets/components/shared.js:180— shared.still.render has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 8, error handling 1, loops 1 (nesting depth added 11). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
photo.photoGL.draw (cognitive 35) skills/taste-skill/assets/objects/photo-kit/photo.js:874— photo.photoGL.draw has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 6, loops 3 (6 pts), ternaries 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.
icons.measureCmd (cognitive 35) skills/taste-skill/scripts/icons.mjs:492— icons.measureCmd has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 9, error handling 3 (5 pts), loops 4, ternaries 3 (nesting depth added 6). Of this number, 25 points are the body's own statements and 10 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
shoot.tilesOf (cognitive 35) REDACTED:249— shoot.tilesOf has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (9 pts), loops 5 (8 pts), boolean chains 6, error handling 3 (nesting depth added 11). Of this number, 34 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.
still.render (cognitive 35) skills/taste-skill/assets/components/shared.js:180— still.render has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 8, error handling 1, loops 1 (nesting depth added 11). Of this number, 34 points are the body's own statements and 1 belongs 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.
photoGL.draw (cognitive 35) skills/taste-skill/assets/objects/photo-kit/photo.js:874— photoGL.draw has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 6, loops 3 (6 pts), ternaries 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.
consistency.shaderLint (cognitive 34) skills/taste-skill/scripts/consistency.mjs:9733— consistency.shaderLint has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 6 (10 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 15). Of this number, 33 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
consistency.narrowPass (cognitive 34) skills/taste-skill/scripts/consistency.mjs:11278— consistency.narrowPass has cognitive complexity 34 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 4 (9 pts), boolean chains 8, loops 5 (7 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
moments.validate (cognitive 34) skills/taste-skill/scripts/moments.mjs:94— moments.validate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 13, 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.
D2 · Cognitive Complexity· mind (cognitive 33) · ×1
mind (cognitive 33) skills/taste-skill/assets/diagrams/diagram.js:782— mind has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 7 (13 pts), boolean chains 2, loops 2 (nesting depth added 14). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 800, 807, 805, …). 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.
free.program (cognitive 33) skills/taste-skill/assets/diagrams/diagram.js:975— free.program has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 4 (11 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 20). Of this number, 17 points are the body's own statements and 16 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.
mount.draw (cognitive 33) skills/taste-skill/assets/effects/ridgeline/effect.js:331— mount.draw has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 5 (11 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pick.deal.valid (cognitive 32) skills/taste-skill/assets/backgrounds/pick.mjs:120— pick.deal.valid has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 13, loops 4 (5 pts) (nesting depth added 5). Of this number, 26 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.
fx.lifecycle (cognitive 32) skills/taste-skill/assets/effects/fx.js:317— fx.lifecycle has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 8, ternaries 4 (6 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 32 points are its own statements and the rest belongs to 6 function items inside it that branch (sync, loop, a function literal at line 348, …). 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.
photo.photoGL.init (cognitive 32) skills/taste-skill/assets/objects/photo-kit/photo.js:721— photo.photoGL.init has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (nesting depth added 10). Of this number, 29 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.
object.cutOut (cognitive 32) skills/taste-skill/assets/objects/dot-object/object.js:77— object.cutOut has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (33 pts), loops 21 (28 pts), ternaries 10 (18 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (object.cutOut::finish) 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.
component.init (cognitive 31) skills/taste-skill/assets/components/fx-progress/component.js:15— component.init has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 7 (8 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (tick, a function literal at line 38, setState, …). 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.
print3d.mountPrint (cognitive 31) skills/taste-skill/assets/objects/_print-core/print3d.js:971— print3d.mountPrint has cognitive complexity 31 (threshold 15). Drivers by points: if/else 148 (173 pts), boolean chains 114, ternaries 34 (41 pts), loops 5 (6 pts), error handling 4 (nesting depth added 33). 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: 3 other methods here (print3d.mountPrint::drawPoster, print3d.mountPrint::advance, print3d.mountPrint::sync) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
system.forms (cognitive 31) skills/taste-skill/assets/system.js:249— system.forms has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 13, if/else 11, ternaries 3 (6 pts), error handling 1 (nesting depth added 3). None of this is in the body itself: all 31 points belong to 10 function literals inside it that branch (lines 281, 256, 250, …). 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.
fragment.init (cognitive 31) skills/taste-skill/assets/ui/files/fragment.js:8— fragment.init has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 7, ternaries 3, loops 2 (nesting depth added 5). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (say, clipBox, a function literal at line 45, …). 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.
pauseButton (cognitive 31) skills/taste-skill/assets/diagrams/diagram.js:1557— pauseButton has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 10, if/else 6 (8 pts) (nesting depth added 7). Of this number, 29 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.
tones (cognitive 31) skills/taste-skill/assets/effects/ruled-grounds/effect.js:89— tones has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (21 pts), if/else 4 (5 pts), boolean chains 4, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
init (cognitive 31) skills/taste-skill/assets/ui/terminal-run/fragment.js:15— init has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5, ternaries 2 (5 pts), loops 2 (nesting depth added 10). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 95, meter, scroll, …). 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.
decodePNG (cognitive 31) skills/taste-skill/assets/backgrounds/check.mjs:49— decodePNG has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 6 (9 pts), loops 4 (6 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.
effects.pick (cognitive 30) skills/taste-skill/scripts/effects.mjs:194— effects.pick has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 9, ternaries 4 (6 pts), loops 2 (3 pts), error handling 1 (nesting depth added 4). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
shoot.decodePNG (cognitive 30) REDACTED:125— shoot.decodePNG has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (9 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mountAscii.draw (cognitive 30) skills/taste-skill/assets/effects/ascii-shade/effect.js:297— mountAscii.draw has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 6 (9 pts), ternaries 2 (7 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mountGlobe.drawNetwork (cognitive 30) skills/taste-skill/assets/effects/dotted-globe/effect.js:871— mountGlobe.drawNetwork has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 4 (8 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 12). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
materialGlsl (cognitive 30) skills/taste-skill/assets/objects/product-render/build.js:103— materialGlsl has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (12 pts), if/else 2, match/switch 1, other 1 (nesting depth added 4). 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.
layout.lockLines::units::walk (cognitive 29) skills/taste-skill/assets/layout/layout.js:133— layout.lockLines::units::walk has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fx-gallery.template.html.setGroupGround (cognitive 29) skills/taste-skill/scripts/fx-gallery.template.html:889— fx-gallery.template.html.setGroupGround has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 3 (9 pts), boolean chains 4, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scene.mount (cognitive 28) skills/taste-skill/assets/scenes/parts-lock-into-the-whole/scene.js:27— scene.mount has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 4, boolean chains 3 (nesting depth added 5). 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: 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.
D2 · Cognitive Complexity· state (cognitive 28) · ×1
state (cognitive 28) skills/taste-skill/assets/diagrams/diagram.js:1441— state has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, ternaries 2 (4 pts), loops 2 (nesting depth added 9). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 1452). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
mount.drawPulse (cognitive 28) skills/taste-skill/assets/effects/grid-pulse/effect.js:293— mount.drawPulse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 3 (5 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
effect.mountAscii.draw (cognitive 27) skills/taste-skill/assets/effects/ascii-shade/effect.js:297— effect.mountAscii.draw has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 6 (9 pts), ternaries 1 (4 pts), boolean chains 3 (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.
effect.pickHubs (cognitive 27) skills/taste-skill/assets/effects/dotted-globe/effect.js:240— effect.pickHubs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 5 (10 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fragment.init (cognitive 27) skills/taste-skill/assets/ui/doc/fragment.js:8— fragment.init has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 7 (8 pts), boolean chains 7, loops 2 (nesting depth added 3). Most of this is not in the body itself: 6 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (place, noteOf, a function literal at line 44, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
visuals (cognitive 27) skills/taste-skill/assets/system.js:464— visuals has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, if/else 7 (8 pts), ternaries 3, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 466, opts, run, …). 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.
bake.chains (cognitive 26) skills/taste-skill/assets/components/fx-map/bake.mjs:161— bake.chains has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 9, loops 3 (4 pts), ternaries 1 (3 pts) (nesting depth added 9). Of this number, 17 points are the body's own statements and 9 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.
effect.mountGlobe.drawNetwork (cognitive 26) skills/taste-skill/assets/effects/dotted-globe/effect.js:871— effect.mountGlobe.drawNetwork has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 10). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
effect.placeOrb (cognitive 26) skills/taste-skill/assets/effects/orb-sphere/effect.js:209— effect.placeOrb has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (6 pts), ternaries 2, boolean chains 1 (nesting depth added 14). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
photo.photoPalette (cognitive 26) skills/taste-skill/assets/objects/photo-kit/photo.js:178— photo.photoPalette has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 4 (9 pts), boolean chains 4, error handling 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
icons.listCmd (cognitive 26) skills/taste-skill/scripts/icons.mjs:420— icons.listCmd has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 8, loops 4 (8 pts), ternaries 4 (8 pts), if/else 2 (nesting depth added 8). Of this number, 22 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.
hub.link (cognitive 26) skills/taste-skill/assets/diagrams/diagram.js:724— hub.link has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (18 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
deal::valid (cognitive 26) skills/taste-skill/assets/backgrounds/pick.mjs:120— deal::valid has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, loops 4 (5 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.
scene.mount (cognitive 25) skills/taste-skill/assets/scenes/dot-becomes-the-full-stop/scene.js:16— scene.mount has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5, ternaries 4, 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, 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.
putIcon (cognitive 25) skills/taste-skill/assets/diagrams/diagram.js:199— putIcon has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 205, (anonymous)::onerror). 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.
bakeDraw (cognitive 25) skills/taste-skill/assets/ui/ui.js:593— bakeDraw has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3, error handling 1, loops 1, ternaries 1 (nesting depth added 9). Of this number, 20 points are the body's own statements and 5 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.
mountAscii.makeField (cognitive 25) skills/taste-skill/assets/effects/ascii-shade/effect.js:206— mountAscii.makeField has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 4 (8 pts), loops 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 251, a function literal at line 277, a function literal at line 230, …). 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.
D2 · Cognitive Complexity· mount (cognitive 25) · ×1
mount (cognitive 25) skills/taste-skill/assets/scenes/letter-bar-floods-the-ground/scene.js:34— mount has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 5 (6 pts), boolean chains 5, loops 1 (2 pts), other 1 (nesting depth added 5). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (update, measure, rest, …). 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.
Diagram.render (cognitive 24) skills/taste-skill/assets/diagrams/diagram.js:1467— Diagram.render has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (9 pts), loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 1470, 1478). 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.
Diagram.applyFocus (cognitive 24) skills/taste-skill/assets/diagrams/diagram.js:1596— Diagram.applyFocus has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), loops 4 (6 pts) (nesting depth added 6). Of this number, 19 points are the body's own statements and 5 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.
lib.gl (cognitive 24) skills/taste-skill/assets/scenes/lib.js:283— lib.gl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4, error handling 3, loops 1 (nesting depth added 2). Of this number, 21 points are the body's own statements and 3 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.
system.actionbar (cognitive 24) skills/taste-skill/assets/system.js:344— system.actionbar has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8, loops 2 (4 pts), ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 375, a function literal at line 359, update, …). 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.
consistency.runSweep (cognitive 24) skills/taste-skill/scripts/consistency.mjs:11325— consistency.runSweep has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 6 (9 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
moments.auditPage (cognitive 24) skills/taste-skill/scripts/moments.mjs:479— moments.auditPage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
effects.launch (cognitive 24) skills/taste-skill/scripts/effects.mjs:424— effects.launch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9, error handling 2 (3 pts), loops 1, ternaries 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
gate.mergeFamilies (cognitive 24) skills/taste-skill/scripts/gate.mjs:533— gate.mergeFamilies has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
detect (cognitive 24) skills/taste-skill/assets/backgrounds/backgrounds.js:53— detect has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 9, if/else 9, ternaries 3 (6 pts) (nesting depth added 3). Of this number, 22 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.
tones (cognitive 24) skills/taste-skill/assets/effects/orb-sphere/effect.js:169— tones has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (16 pts), boolean chains 4, if/else 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.
blueNoise (cognitive 24) skills/taste-skill/assets/objects/photo-kit/photo.js:255— blueNoise has cognitive complexity 24 (threshold 15). Drivers by points: loops 10 (12 pts), if/else 4 (7 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 7). Of this number, 13 points are the body's own statements and 11 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.
photoGL.step (cognitive 24) skills/taste-skill/assets/objects/photo-kit/photo.js:838— photoGL.step has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (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.
init (cognitive 24) skills/taste-skill/assets/ui/calendar/fragment.js:8— init has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 5 (7 pts), boolean chains 4, loops 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 54, show, still, …). 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.
bake.kindOf (cognitive 23) skills/taste-skill/assets/components/fx-map/bake.mjs:264— bake.kindOf has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (19 pts), boolean chains 4 (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.
diagram.auto (cognitive 23) skills/taste-skill/assets/diagrams/diagram.js:1654— diagram.auto has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 2 (5 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
object.cutOut::finish (cognitive 23) skills/taste-skill/assets/objects/dot-object/object.js:158— object.cutOut::finish has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3, ternaries 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (object.cutOut) 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.
scene.mount (cognitive 23) skills/taste-skill/assets/scenes/product-assembles-into-its-action/scene.js:30— scene.mount has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, loops 4, ternaries 2 (nesting depth added 2). Of this number, 21 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.
moments.cmdPick (cognitive 23) skills/taste-skill/scripts/moments.mjs:253— moments.cmdPick has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 6, ternaries 3 (5 pts), error handling 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 5 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.
gate.findPage (cognitive 23) skills/taste-skill/scripts/gate.mjs:242— gate.findPage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, error handling 2, loops 2, 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.
pauser (cognitive 23) skills/taste-skill/assets/components/shared.js:485— pauser has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (8 pts), boolean chains 3, loops 1 (2 pts), error handling 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (set, add, a function literal at line 498, …). 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.
tones (cognitive 23) skills/taste-skill/assets/effects/film-light-leak/effect.js:106— tones has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 5). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolveView (cognitive 23) skills/taste-skill/assets/objects/product-render/build.js:676— resolveView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, other 5, ternaries 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ui.grounds (cognitive 22) skills/taste-skill/assets/ui/ui.js:701— ui.grounds has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, loops 1 (nesting depth added 7). 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.
photo.photoGL.step (cognitive 22) skills/taste-skill/assets/objects/photo-kit/photo.js:838— photo.photoGL.step has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
photos.pick::chooseLead (cognitive 22) skills/taste-skill/scripts/photos.mjs:442— photos.pick::chooseLead has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, ternaries 1 (3 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. This shape REPEATS in the file: one other method here (photos.pick) 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.
shader.draw (cognitive 22) skills/taste-skill/assets/effects/fx.js:730— shader.draw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (6 pts), boolean chains 3, ternaries 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
counts (cognitive 22) skills/taste-skill/assets/motion/motion.js:124— counts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, boolean chains 7, loops 1, ternaries 1. Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 130, (anonymous)::arm, a function literal at line 155, …). 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.
fx.shader.draw (cognitive 21) skills/taste-skill/assets/effects/fx.js:730— fx.shader.draw has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bake.lb (cognitive 21) skills/taste-skill/assets/components/fx-map/bake.mjs:79— bake.lb has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kit.paletteOf (cognitive 21) skills/taste-skill/assets/objects/_scenes/kit.js:88— kit.paletteOf has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 3 (10 pts), if/else 5 (9 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
consistency.slowPass (cognitive 21) skills/taste-skill/scripts/consistency.mjs:9814— consistency.slowPass has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, loops 4 (6 pts), error handling 1 (nesting depth added 6). Of this number, 18 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
mountOne.start (cognitive 21) skills/taste-skill/assets/effects/duotone-grade/effect.js:572— mountOne.start has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (fallback, graded, a function literal at line 580, …). 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.
mountAll (cognitive 21) skills/taste-skill/assets/objects/_scenes/auto.js:41— mountAll has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 2, ternaries 1 (2 pts), error handling 1 (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 5 function literals inside it that branch (lines 57, 54, 42, …). 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.
demo (cognitive 21) skills/taste-skill/assets/objects/_scenes/demo.js:15— demo has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, ternaries 9, if/else 2, error handling 1. Of this number, 12 points are the body's own statements and 9 belong to 19 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.
mount.build (cognitive 21) skills/taste-skill/assets/objects/dot-object/object.js:193— mount.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 2, 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.
init (cognitive 21) skills/taste-skill/assets/ui/notify/fragment.js:7— init has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (5 pts), loops 2 (3 pts), boolean chains 2, other 1 (nesting depth added 7). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 23, a function literal at line 48, a function literal at line 12, …). 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.
component.init (cognitive 20) skills/taste-skill/assets/components/fx-tabs/component.js:8— component.init has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 8, boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (key, place, a function literal at line 31, …). 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.
layout.letters::walk (cognitive 20) skills/taste-skill/assets/layout/layout.js:84— layout.letters::walk has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.makeProduct (cognitive 20) skills/taste-skill/assets/objects/product-render/build.js:1076— build.makeProduct has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 5 (6 pts), if/else 4, error handling 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.
consistency.helperLib (cognitive 20) skills/taste-skill/scripts/consistency.mjs:8994— consistency.helperLib has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 19, ternaries 1. Of this number, 19 points are the body's own statements and 1 belongs to 14 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
hub (cognitive 20) skills/taste-skill/assets/diagrams/diagram.js:668— hub has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (5 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 4 belong to 17 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.
photoURL (cognitive 20) skills/taste-skill/assets/objects/_scenes/kit.js:132— photoURL has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
placeProp (cognitive 20) skills/taste-skill/assets/objects/product-render/build.js:612— placeProp has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 1 (3 pts), loops 2 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (a function literal at line 615, T, a function literal at line 618). 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.
D2 · Cognitive Complexity· mount (cognitive 20) · ×1
mount (cognitive 20) skills/taste-skill/assets/objects/split-reveal/object.js:92— mount has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 22, if/else 18 (19 pts), ternaries 12 (16 pts), other 4, error handling 1, loops 1 (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, 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.
effect.uniforms (cognitive 19) skills/taste-skill/assets/effects/film-light-leak/effect.js:165— effect.uniforms has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 5, boolean chains 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.
fonts.html.fontLink (cognitive 19) skills/taste-skill/assets/layout/fonts.html:65— fonts.html.fontLink has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (add, add::put). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
kit.stage::init (cognitive 19) skills/taste-skill/assets/objects/_scenes/kit.js:552— kit.stage::init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, loops 2 (3 pts), error handling 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. This shape REPEATS in the file: one other method here (kit.stage) 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.
consistency.sweepWidth (cognitive 19) skills/taste-skill/scripts/consistency.mjs:11218— consistency.sweepWidth has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 6, loops 3 (5 pts), error handling 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 4 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. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
copy-lint.lintRead.slopIn (cognitive 19) skills/taste-skill/scripts/copy-lint.mjs:295— copy-lint.lintRead.slopIn has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (13 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.
copy-lint.crossFile (cognitive 19) skills/taste-skill/scripts/copy-lint.mjs:417— copy-lint.crossFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (7 pts), boolean chains 3 (nesting depth added 9). 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.
icons.rank (cognitive 19) skills/taste-skill/scripts/icons.mjs:387— icons.rank has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (14 pts), boolean chains 2, if/else 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
icons.findCmd (cognitive 19) skills/taste-skill/scripts/icons.mjs:398— icons.findCmd has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), loops 2 (3 pts) (nesting depth added 3). Of this number, 16 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.
start.fontLink (cognitive 19) skills/taste-skill/scripts/start.mjs:261— start.fontLink has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (add, add::put). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
start.dealTypes (cognitive 19) skills/taste-skill/scripts/start.mjs:347— start.dealTypes has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 6, ternaries 3 (6 pts), if/else 2 (4 pts), loops 2 (3 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 5 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.
mountGlobe.draw (cognitive 19) skills/taste-skill/assets/effects/dotted-globe/effect.js:922— mountGlobe.draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· mount (cognitive 19) · ×1
mount (cognitive 19) skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:28— mount has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 4, ternaries 2, other 1. Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 78, update, near, …). 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.
build.frameView (cognitive 18) skills/taste-skill/assets/objects/product-render/build.js:708— build.frameView has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). Of this number, 9 points are the body's own statements and 9 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.
fragment.init (cognitive 18) skills/taste-skill/assets/ui/window/fragment.js:8— fragment.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 31, word, a function literal at line 16, …). 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.
consistency.lintGLSL (cognitive 18) skills/taste-skill/scripts/consistency.mjs:9708— consistency.lintGLSL has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 12, if/else 6. None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 9717). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
effects.shot (cognitive 18) skills/taste-skill/scripts/effects.mjs:490— effects.shot has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gate.sourceFiles (cognitive 18) skills/taste-skill/scripts/gate.mjs:289— gate.sourceFiles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 3, error handling 2 (nesting depth added 4). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (go). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
perf.measure (cognitive 18) skills/taste-skill/scripts/perf.mjs:197— perf.measure has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 8, loops 1. Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 203, 217). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
photos.creditsCmd (cognitive 18) skills/taste-skill/scripts/photos.mjs:991— photos.creditsCmd has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 2, error handling 1. 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: 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.
start.tokens (cognitive 18) skills/taste-skill/scripts/start.mjs:166— start.tokens has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 9. 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, 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.
lanes (cognitive 18) skills/taste-skill/assets/diagrams/diagram.js:532— lanes has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (12 pts), if/else 3, loops 2, boolean chains 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 6 belong to 16 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.
problems (cognitive 18) skills/taste-skill/assets/diagrams/diagram.js:1092— problems has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (5 pts), boolean chains 2, 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.
mountAscii (cognitive 18) skills/taste-skill/assets/effects/ascii-shade/effect.js:101— mountAscii has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 2 (3 pts), other 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 7 belong to 10 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.
demo (cognitive 18) skills/taste-skill/assets/objects/_print-core/demo.js:18— demo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, loops 2, ternaries 2, error handling 1, other 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 4 belong to 8 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.
mount.fitFor (cognitive 18) skills/taste-skill/assets/objects/exploded-layers/object.js:175— mount.fitFor has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), ternaries 4 (7 pts), if/else 1 (nesting depth added 9). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (box). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity· mount (cognitive 18) · ×1
mount (cognitive 18) skills/taste-skill/assets/scenes/descend-through-weather/scene.js:75— mount has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, ternaries 6 (8 pts), boolean chains 1, other 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 9 function items inside it that branch (update, rest, a function literal at line 137, …). 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.
init (cognitive 18) skills/taste-skill/assets/ui/stat/fragment.js:10— init has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 5, other 1. Of this number, 9 points are the body's own statements and 9 belong to 14 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.
effect.mountAscii.makeField (cognitive 17) skills/taste-skill/assets/effects/ascii-shade/effect.js:206— effect.mountAscii.makeField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 8). 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 251, 230). 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.
effect.mountGlobe.draw (cognitive 17) skills/taste-skill/assets/effects/dotted-globe/effect.js:922— effect.mountGlobe.draw has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (2 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.
lib.split (cognitive 17) skills/taste-skill/assets/moments/lib.js:100— lib.split has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 114, 117). 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.
kit.stage (cognitive 17) skills/taste-skill/assets/objects/_scenes/kit.js:475— kit.stage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 68 (90 pts), boolean chains 57, loops 7 (11 pts), ternaries 8 (10 pts), error handling 5 (6 pts) (nesting depth added 29). 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 (kit.stage::init) 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.
system.daySet (cognitive 17) skills/taste-skill/assets/system.js:163— system.daySet has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
consistency.launch.close (cognitive 17) skills/taste-skill/scripts/consistency.mjs:4639— consistency.launch.close has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: skills/taste-skill/scripts/consistency.mjs holds 96 of the 314 methods over the threshold — including the worst — and 5773 of the 10038 points over it (58%), 12× the next-largest file (skills/taste-skill/scripts/photos.mjs at 483). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity· enter (cognitive 17) · ×1
enter (cognitive 17) skills/taste-skill/assets/motion/motion.js:331— enter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 4, ternaries 3, error handling 2, other 1. Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 360, done, 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.
scene::build (cognitive 17) skills/taste-skill/assets/scenes/lib.js:169— scene::build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (5 pts), if/else 4, boolean chains 3, other 3, error handling 1 (2 pts) (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.
D2 · Cognitive Complexity· day (cognitive 17) · ×1
day (cognitive 17) skills/taste-skill/assets/components/fx-feature-card/component.js:52— day has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve (cognitive 17) skills/taste-skill/assets/objects/_print-core/print3d.js:311— resolve has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 2 (4 pts), boolean chains 2, other 2, 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.
acquire (cognitive 17) skills/taste-skill/assets/objects/_print-core/print3d.js:906— acquire has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs 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.
demo (cognitive 17) skills/taste-skill/assets/objects/photo-kit/demo.js:17— demo has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, ternaries 4, if/else 3, error handling 1. Of this number, 12 points are the body's own statements and 5 belong to 14 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.
mountProduct::show (cognitive 17) skills/taste-skill/assets/objects/product-render/build.js:1311— mountProduct::show has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 6, boolean chains 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dealOnce (cognitive 17) skills/taste-skill/assets/layout/deal.mjs:80— dealOnce has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 2 (4 pts) (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 belong to 6 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.
component.init::draw (cognitive 16) skills/taste-skill/assets/components/fx-map/component.js:54— component.init::draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 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.
effect.mountGlobe (cognitive 16) skills/taste-skill/assets/effects/dotted-globe/effect.js:450— effect.mountGlobe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 5 (6 pts), boolean chains 2 (nesting depth added 1). 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, 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.
ui.hostListen (cognitive 16) skills/taste-skill/assets/ui/ui.js:286— ui.hostListen has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (5 pts) (nesting depth added 8). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function items inside it that branch (enter, a function literal at line 294, a function literal at line 298, …). 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.
photo.creditsBlock (cognitive 16) skills/taste-skill/assets/objects/photo-kit/photo.js:1125— photo.creditsBlock has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 6, if/else 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (srcOf, a function literal at line 1131, a function literal at line 1126, …). 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.
fragment.init.sync (cognitive 16) skills/taste-skill/assets/ui/voice/fragment.js:37— fragment.init.sync has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, 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.
fx-gallery.template.html.setKind (cognitive 16) skills/taste-skill/scripts/fx-gallery.template.html:1272— fx-gallery.template.html.setKind has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 4 (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.
photos.download (cognitive 16) skills/taste-skill/scripts/photos.mjs:792— photos.download has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 3, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
shoot.settleProbe (cognitive 16) REDACTED:223— shoot.settleProbe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 6). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 225). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
shader.init (cognitive 16) skills/taste-skill/assets/effects/fx.js:658— shader.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3, boolean chains 2, error handling 1, loops 1. Of this number, 13 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, 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.
init (cognitive 16) skills/taste-skill/assets/components/fx-chart/component.js:12— init has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 6, boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 15 function items inside it that branch (key, a function literal at line 35, a function literal at line 91, …). 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.
mount.glLine (cognitive 16) skills/taste-skill/assets/effects/ridgeline/effect.js:252— mount.glLine has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 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.
tones (cognitive 16) skills/taste-skill/assets/effects/silk-folds/effect.js:162— tones has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 5, if/else 3, loops 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.
init.sync (cognitive 16) skills/taste-skill/assets/ui/voice/fragment.js:37— init.sync has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, 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.
Fake-async — async method never awaits skills/taste-skill/scripts/effects.mjs:300— `publish` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
No structured logging — No logging call was found in the 143 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 23 sibling directories (32 clone groups) skills/taste-skill/assets/effects/bayer-dither/effect.js:112— 32 duplicated blocks under skills/taste-skill/assets/effects/ have copies in at least two of the sibling directories ascii-shade, aurora-curtains, bayer-dither, caustics, contour-lines, dot-terrain (+17 more sibling(s) not listed) — 23 of them are reported below, and 9 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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 8 sibling directories (22 clone groups) skills/taste-skill/assets/moments/moments.js:30— 22 duplicated blocks under skills/taste-skill/assets/ have copies in at least two of the sibling directories components, effects, layout, moments, motion, objects (+2 more sibling(s) not listed) — 19 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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 13 sibling directories (15 clone groups) skills/taste-skill/assets/objects/_print-core/auto.js:41— 15 duplicated blocks under skills/taste-skill/assets/objects/ have copies in at least two of the sibling directories _print-core, _scenes, dither-sequence, dot-object, exploded-layers, photo-dither (+7 more sibling(s) not listed) — 13 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 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 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 15 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 2 sibling directories (13 clone groups) skills/taste-skill/assets/layout/check.mjs:108— 13 duplicated blocks under skills/taste-skill/ have copies in at least two of the sibling directories assets, scripts — 12 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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 13 sibling directories (8 clone groups) skills/taste-skill/assets/components/fx-logos/component.js:10— 8 duplicated blocks under skills/taste-skill/assets/components/ have copies in at least two of the sibling directories fx-avatar, fx-band, fx-bars, fx-chart, fx-headline, fx-icon-tiles (+7 more sibling(s) not listed) — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (6 clone groups) skills/taste-skill/assets/scenes/object-through-giant-type/scene.js:94— 6 duplicated blocks under skills/taste-skill/assets/scenes/ have copies in at least two of the sibling directories descend-through-weather, dot-becomes-the-full-stop, fixed-hero-object, fly-into-the-shape, letter-bar-floods-the-ground, object-through-giant-type (+3 more sibling(s) not listed) — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) skills/taste-skill/assets/moments/moments.js:30— skills/taste-skill/assets/moments/moments.js:30 · skills/taste-skill/assets/scenes/scenes.js:25 — the two spans are one implementation copied and then locally edited — 552 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) skills/taste-skill/assets/components/fx-feature-card/component.js:173— skills/taste-skill/assets/components/fx-feature-card/component.js:173 · skills/taste-skill/assets/components/fx-feature-card/component.js:201 — the two spans are one implementation copied and then locally edited — 173 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 (19 lines × 2 locations) skills/taste-skill/scripts/consistency.mjs:3590— skills/taste-skill/scripts/consistency.mjs:3590 · REDACTED:212 — 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 (17 lines × 2 locations) skills/taste-skill/assets/effects/fx.js:698— skills/taste-skill/assets/effects/fx.js:698 · skills/taste-skill/assets/objects/photo-kit/photo.js:775 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (13 lines × 2 locations) skills/taste-skill/assets/effects/dotted-globe/effect.js:129— skills/taste-skill/assets/effects/dotted-globe/effect.js:129 · skills/taste-skill/assets/objects/print-globe/object.js:121 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (13 lines × 3 locations) skills/taste-skill/assets/moments/moments.js:31— skills/taste-skill/assets/moments/moments.js:31 · skills/taste-skill/assets/scenes/scenes.js:26 · skills/taste-skill/assets/ui/ui.js:48 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) skills/taste-skill/assets/objects/_print-core/print3d.js:116— skills/taste-skill/assets/objects/_print-core/print3d.js:116 · skills/taste-skill/assets/objects/_scenes/kit.js:391 — the two spans are one implementation copied and then locally edited — 174 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 (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) skills/taste-skill/assets/effects/fx.js:25— skills/taste-skill/assets/effects/fx.js:25 · skills/taste-skill/assets/objects/_print-core/print3d.js:174 — the two spans are one implementation copied and then locally edited — 206 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 (10 lines × 3 locations) skills/taste-skill/assets/effects/fx.js:190— skills/taste-skill/assets/effects/fx.js:190 · skills/taste-skill/assets/objects/_print-core/print3d.js:238 · skills/taste-skill/assets/system.js:388 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Complex function runWidth (cyclomatic 693, cognitive 1310) skills/taste-skill/scripts/consistency.mjs:10219— runWidth has cyclomatic complexity 693 and cognitive complexity 1310; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 extras (cyclomatic 333, cognitive 478) skills/taste-skill/scripts/consistency.mjs:8190— extras has cyclomatic complexity 333 and cognitive complexity 478; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 pageInfo (cyclomatic 282, cognitive 373) skills/taste-skill/scripts/consistency.mjs:7207— pageInfo has cyclomatic complexity 282 and cognitive complexity 373; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 measure (cyclomatic 202, cognitive 279) skills/taste-skill/scripts/consistency.mjs:1868— measure has cyclomatic complexity 202 and cognitive complexity 279; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 moreChecks (cyclomatic 193, cognitive 329) skills/taste-skill/scripts/consistency.mjs:8718— moreChecks has cyclomatic complexity 193 and cognitive complexity 329; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 148, cognitive 225) skills/taste-skill/scripts/consistency.mjs:2660— (anonymous) has cyclomatic complexity 148 and cognitive complexity 225; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 pick (cyclomatic 147, cognitive 266) skills/taste-skill/scripts/photos.mjs:317— pick has cyclomatic complexity 147 and cognitive complexity 266; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 pageProbe (cyclomatic 146, cognitive 219) skills/taste-skill/scripts/consistency.mjs:4113— pageProbe has cyclomatic complexity 146 and cognitive complexity 219; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 138, cognitive 268) · ×1
Complex function run (cyclomatic 138, cognitive 268) skills/taste-skill/scripts/consistency.mjs:4355— run has cyclomatic complexity 138 and cognitive complexity 268; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 134, cognitive 139) skills/taste-skill/assets/diagrams/diagram.js:1174— build has cyclomatic complexity 134 and cognitive complexity 139; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 scan (cyclomatic 130, cognitive 180) skills/taste-skill/scripts/consistency.mjs:1385— scan has cyclomatic complexity 130 and cognitive complexity 180; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 audit (cyclomatic 127, cognitive 159) skills/taste-skill/scripts/consistency.mjs:7601— audit has cyclomatic complexity 127 and cognitive complexity 159; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 effectFindings (cyclomatic 119, cognitive 171) skills/taste-skill/scripts/consistency.mjs:1135— effectFindings has cyclomatic complexity 119 and cognitive complexity 171; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 visualProbe (cyclomatic 119, cognitive 157) skills/taste-skill/scripts/consistency.mjs:700— visualProbe has cyclomatic complexity 119 and cognitive complexity 157; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 areaProbe (cyclomatic 115, cognitive 217) skills/taste-skill/scripts/consistency.mjs:3777— areaProbe has cyclomatic complexity 115 and cognitive complexity 217; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 checkCollide (cyclomatic 114, cognitive 189) skills/taste-skill/scripts/consistency.mjs:6099— checkCollide has cyclomatic complexity 114 and cognitive complexity 189; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 buttonLook (cyclomatic 102, cognitive 106) skills/taste-skill/scripts/consistency.mjs:5185— buttonLook has cyclomatic complexity 102 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 90, cognitive 155) skills/taste-skill/scripts/consistency.mjs:2463— (anonymous) has cyclomatic complexity 90 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 80, cognitive 127) skills/taste-skill/assets/objects/product-render/build.js:812— build has cyclomatic complexity 80 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 moreFindings (cyclomatic 80, cognitive 106) skills/taste-skill/scripts/consistency.mjs:9593— moreFindings has cyclomatic complexity 80 and cognitive complexity 106; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 lyCheck (cyclomatic 77, cognitive 95) skills/taste-skill/assets/layout/layout-check.js:34— lyCheck has cyclomatic complexity 77 and cognitive complexity 95; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 cutLines (cyclomatic 75, cognitive 151) skills/taste-skill/scripts/consistency.mjs:5498— cutLines has cyclomatic complexity 75 and cognitive complexity 151; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 fetchCmd (cyclomatic 74, cognitive 141) skills/taste-skill/scripts/photos.mjs:852— fetchCmd has cyclomatic complexity 74 and cognitive complexity 141; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 checkSpill (cyclomatic 74, cognitive 103) skills/taste-skill/scripts/consistency.mjs:5416— checkSpill has cyclomatic complexity 74 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 hiddenProbe (cyclomatic 73, cognitive 102) skills/taste-skill/scripts/consistency.mjs:9963— hiddenProbe has cyclomatic complexity 73 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 extrasFindings (cyclomatic 73, cognitive 98) skills/taste-skill/scripts/consistency.mjs:9524— extrasFindings has cyclomatic complexity 73 and cognitive complexity 98; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 copyChecks (cyclomatic 72, cognitive 105) skills/taste-skill/scripts/consistency.mjs:9397— copyChecks has cyclomatic complexity 72 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchCmd (cyclomatic 68, cognitive 94) skills/taste-skill/scripts/icons.mjs:310— fetchCmd has cyclomatic complexity 68 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 makeNode (cyclomatic 66, cognitive 81) skills/taste-skill/assets/diagrams/diagram.js:352— makeNode has cyclomatic complexity 66 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 (anonymous) (cyclomatic 63, cognitive 101) skills/taste-skill/scripts/consistency.mjs:2560— (anonymous) has cyclomatic complexity 63 and cognitive complexity 101; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 buttonExtras (cyclomatic 62, cognitive 94) skills/taste-skill/scripts/consistency.mjs:6503— buttonExtras has cyclomatic complexity 62 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 gridCands (cyclomatic 61, cognitive 88) skills/taste-skill/scripts/consistency.mjs:5610— gridCands has cyclomatic complexity 61 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 probe (cyclomatic 59, cognitive 120) skills/taste-skill/scripts/consistency.mjs:6742— probe has cyclomatic complexity 59 and cognitive complexity 120; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 57, cognitive 90) · ×1
Complex function run (cyclomatic 57, cognitive 90) skills/taste-skill/scripts/consistency.mjs:3661— run has cyclomatic complexity 57 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 visualCands (cyclomatic 57, cognitive 70) skills/taste-skill/scripts/consistency.mjs:7921— visualCands has cyclomatic complexity 57 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 fadeCands (cyclomatic 55, cognitive 87) skills/taste-skill/scripts/consistency.mjs:7798— fadeCands has cyclomatic complexity 55 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 checkFold (cyclomatic 55, cognitive 59) skills/taste-skill/scripts/consistency.mjs:6017— checkFold has cyclomatic complexity 55 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function readHtml (cyclomatic 54, cognitive 121) skills/taste-skill/scripts/copy-lint.mjs:79— readHtml has cyclomatic complexity 54 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 searchCmd (cyclomatic 54, cognitive 85) skills/taste-skill/scripts/photos.mjs:654— searchCmd has cyclomatic complexity 54 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 checkTaps (cyclomatic 54, cognitive 82) skills/taste-skill/scripts/consistency.mjs:6195— checkTaps has cyclomatic complexity 54 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· skills/taste-skill/assets/objects/_print-core/print3d.js · ×1
skills/taste-skill/assets/objects/_print-core/print3d.js: 1728 lines of code skills/taste-skill/assets/objects/_print-core/print3d.js:1— skills/taste-skill/assets/objects/_print-core/print3d.js has 1728 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· skills/taste-skill/assets/diagrams/diagram.js · ×1
skills/taste-skill/assets/diagrams/diagram.js: 1633 lines of code skills/taste-skill/assets/diagrams/diagram.js:1— skills/taste-skill/assets/diagrams/diagram.js has 1633 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· skills/taste-skill/assets/objects/product-render/build.js · ×1
skills/taste-skill/assets/objects/product-render/build.js: 1350 lines of code skills/taste-skill/assets/objects/product-render/build.js:1— skills/taste-skill/assets/objects/product-render/build.js has 1350 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· skills/taste-skill/assets/objects/photo-kit/photo.js · ×1
skills/taste-skill/assets/objects/photo-kit/photo.js: 1084 lines of code skills/taste-skill/assets/objects/photo-kit/photo.js:1— skills/taste-skill/assets/objects/photo-kit/photo.js has 1084 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· skills/taste-skill/assets/effects/dotted-globe/effect.js · ×1
skills/taste-skill/assets/effects/dotted-globe/effect.js: 970 lines of code skills/taste-skill/assets/effects/dotted-globe/effect.js:1— skills/taste-skill/assets/effects/dotted-globe/effect.js has 970 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· skills/taste-skill/assets/objects/_scenes/kit.js · ×1
skills/taste-skill/assets/objects/_scenes/kit.js: 909 lines of code skills/taste-skill/assets/objects/_scenes/kit.js:1— skills/taste-skill/assets/objects/_scenes/kit.js has 909 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· skills/taste-skill/assets/effects/fx.js · ×1
skills/taste-skill/assets/effects/fx.js: 894 lines of code skills/taste-skill/assets/effects/fx.js:1— skills/taste-skill/assets/effects/fx.js has 894 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· skills/taste-skill/assets/ui/ui.js · ×1
skills/taste-skill/assets/ui/ui.js: 706 lines of code skills/taste-skill/assets/ui/ui.js:1— skills/taste-skill/assets/ui/ui.js has 706 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· skills/taste-skill/assets/effects/duotone-grade/effect.js · ×1
skills/taste-skill/assets/effects/duotone-grade/effect.js: 670 lines of code skills/taste-skill/assets/effects/duotone-grade/effect.js:1— skills/taste-skill/assets/effects/duotone-grade/effect.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· skills/taste-skill/assets/system.js · ×1
skills/taste-skill/assets/system.js: 585 lines of code skills/taste-skill/assets/system.js:1— skills/taste-skill/assets/system.js has 585 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· skills/taste-skill/assets/components/shared.js · ×1
skills/taste-skill/assets/components/shared.js: 534 lines of code skills/taste-skill/assets/components/shared.js:1— skills/taste-skill/assets/components/shared.js has 534 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· skills/taste-skill/assets/components/fx-map/bake.mjs · ×1
skills/taste-skill/assets/components/fx-map/bake.mjs: 470 lines of code skills/taste-skill/assets/components/fx-map/bake.mjs:1— skills/taste-skill/assets/components/fx-map/bake.mjs has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· skills/taste-skill/assets/components/fx-dither-object/component.js · ×1
skills/taste-skill/assets/components/fx-dither-object/component.js: 461 lines of code skills/taste-skill/assets/components/fx-dither-object/component.js:1— skills/taste-skill/assets/components/fx-dither-object/component.js has 461 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· skills/taste-skill/assets/objects/product-turntable/object.js · ×1
skills/taste-skill/assets/objects/product-turntable/object.js: 415 lines of code skills/taste-skill/assets/objects/product-turntable/object.js:1— skills/taste-skill/assets/objects/product-turntable/object.js has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
X24 · Document value interpolated into markup unescaped· Document value reaches a markup attribute unescaped · ×1
Document value reaches a markup attribute unescaped skills/taste-skill/assets/scenes/letter-bar-floods-the-ground/scene.js:41— `t[best]` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `t[best]` at this site, or validate it against the shape the position accepts before interpolating it.
Duplicated predicate skills/taste-skill/assets/objects/_print-core/print3d.js:790— `!gl.getProgramParameter(p, gl.LINK_STATUS) && !gl.isContextLost()` appears character-identically in 2 files — skills/taste-skill/assets/objects/_print-core/print3d.js, skills/taste-skill/assets/objects/_scenes/kit.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 skills/taste-skill/assets/effects/fx.js:687— `!gl.getProgramParameter(prog, gl.LINK_STATUS) && !gl.isContextLost()` appears character-identically in 2 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/photo-kit/photo.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 skills/taste-skill/assets/effects/fx.js:520— `!gl.getShaderParameter(sh, gl.COMPILE_STATUS) && !gl.isContextLost()` appears character-identically in 2 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/_scenes/kit.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 skills/taste-skill/assets/moments/headline-arrives/moment.js:21— `!heading || lib.reduced() || document.documentElement.classList.contains('mo-safe')` appears character-identically in 2 files — skills/taste-skill/assets/moments/headline-arrives/moment.js, skills/taste-skill/assets/moments/lines-rise/moment.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 skills/taste-skill/assets/layout/check.mjs:40— `!path.isAbsolute(p) && (rel === '..' || rel.startsWith('..' + path.sep) || path.isAbsolute(rel))` appears character-identically in 5 files — skills/taste-skill/assets/layout/check.mjs, skills/taste-skill/scripts/effects.mjs, skills/taste-skill/scripts/gate.mjs, skills/taste-skill/scripts/icons.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 skills/taste-skill/assets/effects/fx.js:545— `(typeof window !== 'undefined' && window.__tpGl) || 0` appears character-identically in 2 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/_print-core/print3d.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 skills/taste-skill/assets/effects/fx.js:546— `(typeof window !== 'undefined' && window.__tpGlMax) || 4` appears character-identically in 2 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/_print-core/print3d.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 skills/taste-skill/assets/backgrounds/check.mjs:89— `MIME[path.extname(file).toLowerCase()] || 'application/octet-stream'` appears character-identically in 2 files — skills/taste-skill/assets/backgrounds/check.mjs, skills/taste-skill/scripts/effects.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 skills/taste-skill/assets/backgrounds/check.mjs:25— `args[i + 1] && !args[i + 1].startsWith('--')` appears character-identically in 5 files — skills/taste-skill/assets/backgrounds/check.mjs, skills/taste-skill/assets/backgrounds/pick.mjs, skills/taste-skill/assets/layout/check.mjs, skills/taste-skill/assets/objects/product-render/make-posters.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 skills/taste-skill/assets/effects/fx.js:674— `canvas.getContext('webgl', attrs) || canvas.getContext('experimental-webgl', attrs)` appears character-identically in 3 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/moments/liquid-hover/moment.js, skills/taste-skill/assets/objects/photo-kit/photo.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 skills/taste-skill/assets/effects/fx.js:783— `canvas.width !== W || canvas.height !== H` appears character-identically in 5 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/effects/ridgeline/effect.js, skills/taste-skill/assets/objects/_print-core/print3d.js, skills/taste-skill/assets/objects/photo-kit/photo.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 skills/taste-skill/assets/diagrams/diagram.js:86— `document.documentElement.dataset.type === 'place' || (!!m && m.content.trim().toLowerCase() === 'other')` appears character-identically in 4 files — skills/taste-skill/assets/diagrams/diagram.js, skills/taste-skill/assets/layout/layout.js, skills/taste-skill/assets/moments/picture-develops/moment.js, skills/taste-skill/assets/system.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 skills/taste-skill/assets/diagrams/diagram.js:1082— `document.fonts && document.fonts.status !== 'loaded'` appears character-identically in 2 files — skills/taste-skill/assets/diagrams/diagram.js, skills/taste-skill/assets/scenes/lib.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 skills/taste-skill/assets/motion/motion.js:201— `el.closest('[data-ui-pause-host], .panel__screen, .panel, .frame') || el` appears character-identically in 2 files — skills/taste-skill/assets/motion/motion.js, skills/taste-skill/assets/objects/_scenes/kit.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 skills/taste-skill/assets/effects/fx.js:585— `el.dataset.fxOwnBg || !bg || bg === 'transparent' || /rgba\(.*,\s*0\)$/.test(bg)` appears character-identically in 3 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/effects/grid-pulse/effect.js, skills/taste-skill/assets/effects/ridgeline/effect.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 skills/taste-skill/assets/layout/check.mjs:57— `fs.existsSync(file) && fs.statSync(file).isDirectory()` appears character-identically in 2 files — skills/taste-skill/assets/layout/check.mjs, skills/taste-skill/scripts/effects.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 skills/taste-skill/scripts/effects.mjs:475— `m.sessionId === sessionId && m.method === 'Page.loadEventFired'` appears character-identically in 2 files — skills/taste-skill/scripts/effects.mjs, skills/taste-skill/scripts/perf.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 skills/taste-skill/assets/layout/layout-check.js:160— `n.nodeType === 3 && n.textContent.trim()` appears character-identically in 3 files — skills/taste-skill/assets/layout/layout-check.js, skills/taste-skill/assets/moments/lib.js, skills/taste-skill/assets/motion/motion.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 skills/taste-skill/assets/backgrounds/check.mjs:98— `parseInt(fs.readFileSync(portFile, 'utf8'), 10) || null` appears character-identically in 4 files — skills/taste-skill/assets/backgrounds/check.mjs, skills/taste-skill/assets/layout/check.mjs, skills/taste-skill/assets/objects/product-render/make-posters.mjs, skills/taste-skill/scripts/perf.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 skills/taste-skill/assets/backgrounds/check.mjs:109— `r.exceptionDetails.exception?.description || r.exceptionDetails.text` appears character-identically in 2 files — skills/taste-skill/assets/backgrounds/check.mjs, skills/taste-skill/assets/layout/check.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 skills/taste-skill/assets/layout/check.mjs:62— `rel.split(path.sep)[0] === '..' || path.isAbsolute(rel)` appears character-identically in 2 files — skills/taste-skill/assets/layout/check.mjs, skills/taste-skill/scripts/perf.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 skills/taste-skill/assets/components/fx-avatar/component.js:22— `root.dataset.cxEffect || 'gradient-mesh'` appears character-identically in 2 files — skills/taste-skill/assets/components/fx-avatar/component.js, skills/taste-skill/assets/components/fx-pricing/component.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 skills/taste-skill/assets/components/fx-bars/component.js:23— `root.dataset.cxEffect || 'grain-gradient'` appears character-identically in 4 files — skills/taste-skill/assets/components/fx-bars/component.js, skills/taste-skill/assets/components/fx-icon-tiles/component.js, skills/taste-skill/assets/components/fx-progress/component.js, skills/taste-skill/assets/components/fx-tabs/component.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 skills/taste-skill/assets/effects/fx.js:495— `typeof v === 'number' || typeof v === 'boolean'` appears character-identically in 3 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/_scenes/kit.js, skills/taste-skill/assets/objects/photo-kit/photo.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 skills/taste-skill/assets/effects/fx.js:15— `typeof window !== 'undefined' && typeof document !== 'undefined'` appears character-identically in 4 files — skills/taste-skill/assets/effects/fx.js, skills/taste-skill/assets/objects/_print-core/print3d.js, skills/taste-skill/assets/objects/photo-kit/photo.js, skills/taste-skill/assets/objects/product-render/build.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.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/consistency.mjs:533— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/consistency.mjs:589— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/consistency.mjs:590— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/consistency.mjs:1737— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/copy-lint.mjs:80— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/gate.mjs:269— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/gate.mjs:270— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/gate.mjs:371— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/icons.mjs:576— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/photos.mjs:981— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/photos.mjs:1006— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/scripts/photos.mjs:1009— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/taste-skill/assets/diagrams/diagram.js:1647— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Silent fallback default in catch skills/taste-skill/assets/diagrams/diagram.js:129— `relOut` swallows every exception into `return 'assets/icons'` — 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 skills/taste-skill/assets/objects/product-render/auto.js:117— `targets` 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 skills/taste-skill/scripts/consistency.mjs:9211— `pageExists` swallows every exception into `return true` — 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 skills/taste-skill/scripts/consistency.mjs:9735— `shaderLint` 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 skills/taste-skill/scripts/copy-lint.mjs:53— `decode` 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 skills/taste-skill/scripts/moments.mjs:165— `readHistory` 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 skills/taste-skill/scripts/gate.mjs:186— `lastTouch` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch skills/taste-skill/scripts/icons.mjs:102— `loadBoxes` 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 skills/taste-skill/scripts/photos.mjs:127— `readRecent` 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 skills/taste-skill/scripts/start.mjs:94— `readRecent` 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 skills/taste-skill/assets/components/fx-map/bake.mjs:263— "what the card calls the stop: metro, train, tram, ferry or bus" repeats the code it sits on: 7 of its 8 words (calls, stop, metro, train, tram, ferry, bus) are already in `const kindOf = t => (t.station === 'subway' || t.subway === 'yes' || t.railway === 'subway_entrance') ? 'metro'`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment skills/taste-skill/scripts/consistency.mjs:9674— "fact-agree: one day, two opening hours" repeats the code it sits on: 6 of its 6 words (fact, agree, day, two, opening, hours) are already in `if (first) for (const h of M.hours.slice(0, 2)) push('fact-agree', h.two ? 'FAIL' : 'WARN', h, `the opening hours disagr …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies skills/taste-skill/scripts/effects.mjs:375— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 3/14 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
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) — `skills/taste-skill/scripts/copy-lint.mjs`, `skills/taste-skill/scripts/moments.mjs` — 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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1d58e-b4bb-7405-8bda-14699cdec030 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 5 · Warnings: 925 · Recommendations: 57 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 15:37 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.