Public report of xuanyustudio/LocalMiniDrama, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 14:26 UTC · Survey ID cd_fdf8599d904844d4b6f758442048bd9b

xuanyustudio/LocalMiniDrama

Measured 17 November 2026, 14:21 UTC, at code version 1edfa4c

First survey, so nothing to compare with yet
CAI score 25.6out of 100 At risk

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 59,547 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Code Health, 14.3

Findings by how serious they are

141 critical 1026 serious 128 minor

16 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 14:21 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

68of 68 dimensions measured by tools.
1267of 1295 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
68dimensions across 7 lenses, read from 59,547 lines of product code in 2 projects.
Chapters

Executive summary

xuanyustudio/LocalMiniDrama is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 25.6 out of 100, which the At risk rating leaves unchanged.

Code Health, at 14.3, is the weakest lens and counts most in the score. The best first steps are simplifying the most tangled methods and simplifying the hardest methods, each worth about 5.4 points. Raising Code Health to 70 would lift the score to about 35.4.

Thirty-four known security holes in the packages the code depends on can be used by attackers. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and thirty-seven controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The 23 images with no text description need a text description.

The product code is 59,547 lines, about €53,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 for The 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.
Code Health 14.3 · counts for 46%Security and Compliance 25.9 · counts for 25%Production Readiness 30.9 · counts for 14%Accessibility 40.0 · counts for 8%Performance 60.0 · counts for 4%Maturity 67.4 · counts for 2%Architecture 96.5 · counts for 1%

If Code Health rose from 14.3 to 70, the lowest score rated Strong, the score would rise from 25.6 to about 35.4.

Code composition: what the lines of code are
Product code 95%Tests 5%
Rebuild cost: about €53,000 · Estimate
Cost to rebuild€18,000 to €89,000, for 295 to 937 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, 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 26. 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.
SizeMedium: 59,547 lines of product code
What it is notNot 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
Bring the 61 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with processImageGeneration (cyclomatic 345), videoClient.pollVideoTask (cyclomatic 191), buildUniversalSegmentUserPromptBundle (cyclomatic 146).
Raises the score by about 5.4 points · High effort · Cyclomatic Complexity
2
Bring the 77 bodies over 30 down to 30 or less in Cognitive Complexity — start with processImageGeneration (cognitive 760), pollVideoTask (cognitive 288), safeJson.safeParseAIJSON (cognitive 263).
Raises the score by about 5.4 points · High effort · Cognitive Complexity
3
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Raises the score by about 3.9 points · Medium effort · Access Controls

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €53,000 to build again, about 0.4 person-years of work. Its weakest lens is Code Health, at 14.3 (Critical). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
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 2.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 15% to 34% on every change. The history of the code shows how much it changes: about 7,497 lines over the last 90 days, which is about 30,404 lines a year. At that pace, the extra work comes to an estimated 11.4 to 68.4 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 · 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.
If you do one thing first · First action
Bring the 61 bodies over 30 down to 30 or less in Cyclomatic Complexity. Of all the actions in this report, it raises the score most for the work it takes: about 5.4 points for high effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

At a glance — Code Health · 14.3 · Critical · gated by D1, D2, R1, R10, R2, R3, R7 ·

At a glance — Architecture · 96.5 · Exemplary ·

At a glance — Maturity · 67.4 · Adequate · gated by M2 ·

At a glance — Readiness · 30.9 · Weak · gated by D14, R6, P3, P7 ·

At a glance — Security · 25.9 · Weak · gated by D29, D36, C2 ·

At a glance — Accessibility · 40.0 · Weak · gated by AC1, AC4 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection178High / Critical
A03:2025 — Software Supply Chain Failures54High / Critical
A02:2025 — Security Misconfiguration1Medium

Roadmap

Top priorities: Bring the 61 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with processImageGeneration (cyclomatic 345), videoClient.pollVideoTask (cyclomatic 191), buildUniversalSegmentUserPromptBundle (cyclomatic 146); Bring the 77 bodies over 30 down to 30 or less in Cognitive Complexity — start with processImageGeneration (cognitive 760), pollVideoTask (cognitive 288), safeJson.safeParseAIJSON (cognitive 263); Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Bring the 61 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with processImageGeneration (cyclomatic 345), videoClient.pollVideoTask (cyclomatic 191), buildUniversalSegmentUserPromptBundle (cyclomatic 146).+5.4 ptsHighCyclomatic Complexity
Bring the 77 bodies over 30 down to 30 or less in Cognitive Complexity — start with processImageGeneration (cognitive 760), pollVideoTask (cognitive 288), safeJson.safeParseAIJSON (cognitive 263).+5.4 ptsHighCognitive Complexity
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.+3.9 ptsMediumAccess Controls
Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED.+1.9 ptsLowVulnerability-disclosure Policy
Resolve the 47 FunctionTooLong finding(s) in God Classes — start with videoClient.js (11), imageClient.js (5), REDACTED (3).+3.5 ptsHighGod Classes
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14).+3.4 ptsMediumLicense Compliance
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.+3.1 ptsMediumType Safety
Resolve the 40 finding(s) in Cyclomatic Complexity.+3.1 ptsMediumCyclomatic Complexity

File quality

Per-file score 0–10 — a quality signature. Of 82 files carrying findings, judged against the Production bar: 7% slop · 77% mixed · 16% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopLicense Compliance: Banned license: @img/sharp-libvips-darwin-arm64
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.3SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
backend-node/src/services/episodeStoryboardService.js3.5SlopChange Coupling: Boundary-crossing change coupling: episodeStoryboardService.js ↔ FilmCreate.vue
backend-node/src/services/characterLibraryService.js3.5SlopChange Coupling: Boundary-crossing change coupling: characterLibraryService.js ↔ FilmCreate.vue
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
backend-node/src/services/aiConfigService.js4.0MixedChange Coupling: Boundary-crossing change coupling: aiConfigService.js ↔ AIConfigContent.vue
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): High: REDACTED
backend-node/src/services/imageService.js5.0MixedChange Coupling: Boundary-crossing change coupling: imageService.js ↔ FilmCreate.vue
backend-node/src/services/dramaService.js5.0MixedChange Coupling: Boundary-crossing change coupling: dramaService.js ↔ FilmCreate.vue
backend-node/src/services/framePromptService.js5.0MixedChange Coupling: Boundary-crossing change coupling: framePromptService.js ↔ FilmCreate.vue
backend-node/src/services/aiClient.js5.0MixedChange Coupling: Boundary-crossing change coupling: aiClient.js ↔ FilmCreate.vue
backend-node/src/services/videoService.js5.1MixedChange Coupling: Boundary-crossing change coupling: videoService.js ↔ FilmCreate.vue
backend-node/src/services/promptI18n.js5.4MixedChange Coupling: Boundary-crossing change coupling: promptI18n.js ↔ FilmCreate.vue
backend-node/src/db/migrate.js6.5MixedChange Coupling: Boundary-crossing change coupling: migrate.js ↔ FilmCreate.vue

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 141

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 — 1026

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 — 128

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 16

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 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 68 dimensions across the health lenses
D1D2D3D5D10D12D13D14D15D19D20D21D26D27D28D29D30D34D35D36D37D43AC1AC2AC3AC4AC5AC6AX10AX3AX4C2GD1IC1M1M2M3M4P1P10P2P3P4P6P7PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X16X2X21X24X25X28X29X3

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
  1. 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, 1267 of 1295 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e9e2-c8a6-76e0-82ec-7a1152436f3a.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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: test source is present (.js) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but no package.json in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .js runner and not a verdict that this repository runs no tests.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.js) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but no package.json in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .js runner and not a verdict that this repository runs no tests.
  • 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 (9 contributor(s) across 269 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 8 hold 1.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.
  • D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • 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 a COLLECTOR gap, not an environment fault: it declares a published package (desktop/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • 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.
  • AC4 Keyboard semantics — 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. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
  • 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.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The package `js-yaml` is declared in package.json but was not installed in our sandbox, so the dependency install did not complete here. This is a limit of our sandbox, not of your repository. (rule: dependency-not-installed). The renderer reported: the dev server (`npm run dev` in backend-node/) kept running but served no page within 2 minutes. Likely cause (our sandbox): the package `js-yaml` is declared in package.json but was not installed in our sandbox, so the dependency install did not complete here. This is a limit of our sandbox, not of your repository. Last output: "at Module.require (node:internal/modules/cjs/loader:1335:12) / at require (node:internal/modules/helpers:136:16) / at Object.<anonymous> (<repo>/backend-node/src/config/index.js:3:14) / at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) { / code: 'MODULE_NOT_FOUND', / requireStack: [ / '<repo>/backend-node/src/config/index.js', / '<repo>/backend-node/src/server.js' / ] / } / Node.js v22.13.0 / Failed running 'src/server.js'" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev` in backend-node/) kept running but served no page within 2 minutes. Likely cause (our sandbox): the package `js-yaml` is declared in package.json but was not installed in our sandbox, so the dependency install did not complete here. This is a limit of our sandbox, not of your repository. Last output: "at Module.require (node:internal/modules/cjs/loader:1335:12) / at require (node:internal/modules/helpers:136:16) / at Object.<anonymous> (<repo>/backend-node/src/config/index.js:3:14) / at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) { / code: 'MODULE_NOT_FOUND', / requireStack: [ / '<repo>/backend-node/src/config/index.js', / '<repo>/backend-node/src/server.js' / ] / } / Node.js v22.13.0 / Failed running 'src/server.js'" No runtime evidence was gathered.
  • C1 Data Protection — 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. 'better-sqlite3' is imported (backend-node/src/db/index.js:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C3 Audit Trail — 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. 'better-sqlite3' is imported (backend-node/src/db/index.js:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — 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. 'better-sqlite3' is imported (backend-node/src/db/index.js:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — 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. 'better-sqlite3' is imported (backend-node/src/db/index.js:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • 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 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
  • 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.
  • 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. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
  • 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. 242 further occurrence(s) are not listed individually; the score already reflects all 282.
  • 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. 270 further occurrence(s) are not listed individually; the score already reflects all 310.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 66 further occurrence(s) are not listed individually; the score already reflects all 106.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
  • 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. 217 further occurrence(s) are not listed individually; the score already reflects all 257.
  • 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, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Vue components is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

310 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was processImageGeneration at 345.

processImageGeneration (cyclomatic 345)backend-node/src/services/imageService.js:586
videoClient.pollVideoTask (cyclomatic 191)backend-node/src/services/videoClient.js:4506
buildUniversalSegmentUserPromptBundle (cyclomatic 146)backend-node/src/services/universalSegmentPromptBundle.js:9
_doImport (cyclomatic 142)backend-node/src/services/dramaImportService.js:154
testConnection (cyclomatic 115)backend-node/src/services/aiConfigService.js:261

+ 177 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 61 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with processImageGeneration (cyclomatic 345), videoClient.pollVideoTask (cyclomatic 191), buildUniversalSegmentUserPromptBundle (cyclomatic 146). — 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 61 together lifts Cyclomatic Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

336 method(s) exceeded the cognitive complexity threshold of 15; the worst was processImageGeneration at 760.

processImageGeneration (cognitive 760)backend-node/src/services/imageService.js:586
pollVideoTask (cognitive 288)backend-node/src/services/videoClient.js:4506
safeJson.safeParseAIJSON (cognitive 263)backend-node/src/utils/safeJson.js:180
_doImport (cognitive 207)backend-node/src/services/dramaImportService.js:154
universalSegmentPromptBundle.buildUniversalSegmentUserPromptBundle (cognitive 171)backend-node/src/services/universalSegmentPromptBundle.js:9

+ 192 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 77 bodies over 30 down to 30 or less in Cognitive Complexity — start with processImageGeneration (cognitive 760), pollVideoTask (cognitive 288), safeJson.safeParseAIJSON (cognitive 263). — 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 77 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.0 / 10Adequate✓ 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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Prevented

61 god class(es) detected.

FunctionTooLong: storyboards.routes · ×47REDACTED:240
FileTooLong: services/videoClient.js · ×11backend-node/src/services/videoClient.js
ClassTooLong: useCharacters · ×3frontweb/src/composables/filmCreate/useCharacters.js:1

What to do

  1. Resolve the 47 FunctionTooLong finding(s) in God Classes — start with videoClient.js (11), imageClient.js (5), REDACTED (3). — One of this dimension's main actionable groups (47 warning-level).
  2. Resolve the 11 FileTooLong finding(s) in God Classes — start with videoClient.js, imageClient.js, episodeStoryboardService.js. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 3 ClassTooLong finding(s) in God Classes — start with useCharacters.js, useProps.js, useScenes.js. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 171 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D12 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Verified

16 outdated direct production npm dependency(ies) of 25 graded, 1 pinning defect(s), across 3 package.json (3 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: multer · ×4backend-node/package.json:27
One package at two majors across the workspace: better-sqlite3
Deprecated: lodash.get · ×6REDACTED:2784
Outdated (npm): uuidbackend-node/package.json:29
Outdated (npm): @mastra/core · ×15

What to do

  1. Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
  2. Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with package.json (4). — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance0.0 / 10Critical✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

14 of 418 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 425 package(s) this repository's committed lockfile installs for a consumer — its 25 production, optional and peer dependency(ies), across 3 product package.json manifest(s), and everything those install in turn. Its 4 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. A further 7 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT, which is its own choice and is not judged here.

Banned license: @img/sharp-libvips-darwin-arm64 · ×14REDACTED:299

What to do

  1. Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).

Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots6.3 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.3 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: backend-node/src/services/videoClient.js (7×191=1337); backend-node/src/services/imageClient.js (3×76=228); backend-node/src/services/videoService.js (3×50=150)

Hotspot: backend-node/src/services/videoClient.js · ×6backend-node/src/services/videoClient.js:4506

What to do

  1. Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with videoClient.js, imageClient.js, videoService.js. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 15 document(s) read across 3 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundfrontweb/package.json:7

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency9.0 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Verified

3 naming inconsistencies among 288 declarations measured against a convention their peers follow.

`taskID` spells `ID` where 253 names in the project spell it `Id` · ×2backend-node/src/services/backgroundExtractionService.js:60
`dramaAPI` spells `API` where 32 names in the project spell it `Api`frontweb/src/constants/styleOptions.js:275

What to do

  1. Resolve the 2 `taskID` spells `ID` where 253 names in the project spell it `Id` finding(s) in Naming Consistency — start with backgroundExtractionService.js, characterGenerationService.js. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 `dramaAPI` spells `API` where 32 names in the project spell it `Api` finding(s) in Naming Consistency — start with styleOptions.js. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 2 build units (npm) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

5 % 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.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

179 finding(s): 0 critical, 8 high, 171 medium, 0 low. 5 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 2 file(s) — `backend-node/src/services/imageService.js`, `backend-node/src/services/videoClient.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

48 finding(s): 4 critical, 30 high, 14 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 30 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (30). — One of this dimension's main actionable groups (30 issue-level).
  2. Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

5 of 120 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is frontweb/src/components/SceneModelMap.vue. Counted over 120 of the 179 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×5frontweb/src/components/SceneModelMap.vue:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling8.1 / 10Adequategated by 12 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.1 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: aiConfigService.js↔AIConfigContent.vue 85%; dramaService.js↔FilmCreate.vue 82%; aiClient.js↔FilmCreate.vue 70%

Boundary-crossing change coupling: aiConfigService.js ↔ AIConfigContent.vue · ×12backend-node/src/services/aiConfigService.js:1
Change coupling: DramaDetail.vue ↔ FilmCreate.vue · ×5frontweb/src/views/DramaDetail.vue:1

What to do

  1. Resolve the 12 Boundary-crossing change coupling finding(s) in Change Coupling — start with aiConfigService.js (2), dramaService.js, aiClient.js. — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 5 Change coupling finding(s) in Change Coupling — start with DramaDetail.vue (2), AIConfigContent.vue, characterLibraryService.js. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy4.0 / 10Weak✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (REDACTED or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a REDACTED (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 4.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d37_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives3.4 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×23) — frontweb/src/views/DramaDetail.vue:307, frontweb/src/views/DramaDetail.vue:341, frontweb/src/views/DramaDetail.vue:368, …
  • Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×3) — frontweb/src/views/FilmCreate.vue:1654, frontweb/src/views/FreeCreate.vue:107, frontweb/src/views/MediaLibrary.vue:111

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.7 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This editable region is named only by a placeholder, which is not a name. An element made editable (contenteditable, or role="textbox"/"searchbox" with a tab stop or key handling) is a text-entry control, and it has no aria-label, no aria-labelledby and no title, so assistive tech announces an unnamed edit field. Point aria-labelledby at its visible caption, or add an aria-label. — frontweb/src/components/UniversalSegmentOmniAtEditor.vue:3
  • This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — frontweb/src/views/FilmCreate.vue:577, frontweb/src/views/FilmCreate.vue:674, frontweb/src/views/FilmCreate.vue:775, …
  • 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. (×3) — frontweb/src/views/FilmCreate.vue:810, frontweb/src/views/FilmCreate.vue:816, frontweb/src/views/FilmCreate.vue:822
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — frontweb/src/views/FreeCreate.vue:35
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — index.html:188

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.
AC3 · Page structure6.2 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — frontweb/src/views/FilmList.vue:57, index.html:666
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — index.html:3

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.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×37) — frontweb/src/components/StylePickerButton.vue:4, frontweb/src/views/AiConfig.vue:5, frontweb/src/views/DramaCanvas.vue:5, …
  • This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. (×3) — frontweb/src/views/FilmCreate.vue:559, frontweb/src/views/FilmCreate.vue:657, frontweb/src/views/FilmCreate.vue:758

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety5.1 / 10Adequate✓ Tool-verified

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.

  • The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — frontweb/src/views/FilmCreate.vue:2466
  • `html.light .cover-placeholder` sets color: #9ca3af on background-color: #f3f4f6 — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/views/FilmCreate.vue:9537
  • `html.light .cover-placeholder.error` sets color: #dc2626 on background-color: #fef2f2 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/views/FilmCreate.vue:9541
  • `html.light .sb-ctrl-mode-btn.el-button:hover` sets color: #fff on background-color: #16a34a — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/views/FilmCreate.vue:10024
  • `.check-icon` sets color: #409eff on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/views/MediaLibrary.vue:373
  • `.one-key-not-recommended` sets color: #e6a23c on background-color: #fdf6ec — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/components/AIConfigContent.vue:2540
  • `.ep-auto-badge` sets color: #409eff on background-color: #e6f1ff — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/components/AIConfigContent.vue:2740
  • `.ep-badge-gemini` sets color: #b8860b on background-color: #fef6e0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontweb/src/components/AIConfigContent.vue:2791
  • `.res-tab` 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. — frontweb/src/views/DramaDetail.vue:1462
  • `.episode-card` moves (`transition: border-color 0.25s, transform 0.2s, box-shadow 0.25s, background 0.2s`) 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. — frontweb/src/views/DramaDetail.vue:1348
  • `.episode-enter-icon` moves (`transition: transform 0.2s`) 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. — frontweb/src/views/DramaDetail.vue:1390
  • `.header` moves (`transition: margin-left 0.25s cubic-bezier(.4,0,.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. — frontweb/src/views/FilmCreate.vue:8318
  • `.quick-nav` moves (`transition: width 0.25s cubic-bezier(.4,0,.2,1), padding 0.25s cubic-bezier(.4,0,.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. — frontweb/src/views/FilmCreate.vue:8442
  • `.atp-spin-dot` moves (`animation: atp-pulse 1.2s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontweb/src/views/FilmCreate.vue:8504
  • `.atp-item-dot` moves (`animation: atp-pulse 1.6s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontweb/src/views/FilmCreate.vue:8538
  • `.spin` moves (`animation: navSpin 1s 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. — frontweb/src/views/FilmCreate.vue:8779
  • `.main` moves (`transition: margin-left 0.25s cubic-bezier(.4,0,.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. — frontweb/src/views/FilmCreate.vue:8823
  • `.card` moves (`transition: border-color 0.3s ease, box-shadow 0.3s ease, transform 0.3s 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. — frontweb/src/views/FilmCreate.vue:8837
  • `.pipeline-task-dot` moves (`animation: pipeline-dot-pulse 1.2s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontweb/src/views/FilmCreate.vue:8931
  • `html.light .asset-item:hover` moves (`transition: box-shadow 0.25s, transform 0.2s, border-color 0.25s`) 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. — frontweb/src/views/FilmCreate.vue:9524
  • `.storyboard-row` moves (`transition: border-color 0.25s ease, box-shadow 0.25s ease, transform 0.25s 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. — frontweb/src/views/FilmCreate.vue:9629
  • `.storyboard-row` moves (`animation: sb-fade-in 0.35s 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. — frontweb/src/views/FilmCreate.vue:9630
  • `.sb-gen-dot` moves (`animation: sb-dot-bounce 1.2s infinite ease-in-out 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. — frontweb/src/views/FilmCreate.vue:10477
  • `.project-card` moves (`transition: border-color 0.25s, background 0.25s, transform 0.25s, box-shadow 0.25s`) 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. — frontweb/src/views/FilmList.vue:994
  • `html.light .project-card` moves (`transition: transform 0.2s ease, box-shadow 0.2s ease, border-color 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontweb/src/styles/theme.css:288
  • `html.light .episode-card` moves (`transition: transform 0.15s, box-shadow 0.15s`) 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. — frontweb/src/styles/theme.css:408
  • `.spd-item` moves (`transition: border-color 0.15s, transform 0.1s`) 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. — frontweb/src/components/StylePickerButton.vue:306
  • `.spinner` moves (`animation: spin 0.75s 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. (×3) — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:372, frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue:220, frontweb/src/components/dramaCanvas/CanvasNodeStatusOverlay.vue:45

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.
AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

C2 · Access Controls0.0 / 10Critical✓ 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.

  • This repository serves requests — express() (REDACTED:28) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — REDACTED:28

What to do

  • Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs7.5 / 10Strong✓ Tool-verified

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.

  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — backend-node/src/services/aiConfigService.js:314, backend-node/src/services/videoClient.js:4606
  • The guard above `return 1;` also returns `1`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — backend-node/src/services/imageService.js:77
  • The guard above `return 'cn-beijing';` also returns `'cn-beijing'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — backend-node/src/services/modelArkAssetProxyService.js:63
  • The guard above `return '720p';` also returns `'720p'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — backend-node/src/services/videoClient.js:3477
  • The guard above `return '768P';` also returns `'768P'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — backend-node/src/services/videoClient.js:3884

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.
M1 · Documentation (README)9.3 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

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.

P1 · CI/CD gates8.5 / 10Strong✓ 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.

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.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • `REDACTED` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:55
  • `REDACTED` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:70
  • `backend-node/src/server.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/server.js:12
  • `backend-node/src/utils/safeJson.js` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/utils/safeJson.js:185
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 360 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:360
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 382 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:382
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 404 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:404
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 455 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:455
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 516 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:516
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 525 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:525
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 568 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:568
  • `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 570 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/aiConfigService.js:570
  • `backend-node/src/services/backgroundExtractionService.js` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/backgroundExtractionService.js:42
  • `backend-node/src/services/backgroundExtractionService.js` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/backgroundExtractionService.js:43
  • `backend-node/src/services/characterGenerationService.js` reports through `console.*` at line 88 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/characterGenerationService.js:88
  • `backend-node/src/services/characterGenerationService.js` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/services/characterGenerationService.js:96
  • `REDACTED` reports through `console.*` at line 148 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:148
  • `backend-node/src/routes/agent.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/routes/agent.js:18
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:22
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:26
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:29
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:39
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:70
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 80 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:80
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 85 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:85
  • `backend-node/src/db/migrate.js` reports through `console.*` at line 534 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-node/src/db/migrate.js:534

What to do

  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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.
  • `backend-node/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — backend-node/package.json:15

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.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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. (×32) — backend-node/src/services/aiConfigService.js:276, backend-node/src/services/aiConfigService.js:295, backend-node/src/services/aiConfigService.js:319, …

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.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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.existsSync` in `app.get("/favicon.ico")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:77
  • `fs.mkdirSync` in `initAgent` 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. — backend-node/src/mastra/index.mjs:210
  • `fs.existsSync` in `sd2VoiceUpload` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:351
  • `fs.mkdirSync` in `sd2VoiceUpload` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:351
  • `fs.writeFileSync` in `sd2VoiceUpload` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:355
  • `fs.existsSync` in `generateTextWithVision` 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. — backend-node/src/services/aiClient.js:660
  • `fs.readFileSync` in `generateTextWithVision` 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. — backend-node/src/services/aiClient.js:663
  • `fs.readFileSync` in `splitQuadGridToImages` 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. — backend-node/src/services/imageService.js:110
  • `fs.writeFileSync` in `splitQuadGridToImages` 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. — backend-node/src/services/imageService.js:145
  • `fs.readFileSync` in `splitNineGridToImages` 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. — backend-node/src/services/imageService.js:328
  • `fs.writeFileSync` in `splitNineGridToImages` 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. — backend-node/src/services/imageService.js:363
  • `fs.existsSync` in `normalizeLocalImageToTargetSize` 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. — backend-node/src/services/imageService.js:426
  • `fs.readFileSync` in `normalizeLocalImageToTargetSize` 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. — backend-node/src/services/imageService.js:435
  • `fs.writeFileSync` in `normalizeLocalImageToTargetSize` 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. — backend-node/src/services/imageService.js:456
  • `fs.existsSync` in `normalizeSavedImageToTargetPixels` 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) — backend-node/src/services/imageService.js:475, backend-node/src/services/imageService.js:516
  • `fs.unlinkSync` in `normalizeSavedImageToTargetPixels` 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) — backend-node/src/services/imageService.js:510, backend-node/src/services/imageService.js:516
  • `fs.renameSync` in `normalizeSavedImageToTargetPixels` 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. — backend-node/src/services/imageService.js:511
  • `fs.existsSync` in `runMergedEpisodePostProcess` 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. (×7) — backend-node/src/services/mergedEpisodePostProcess.js:212, backend-node/src/services/mergedEpisodePostProcess.js:262, backend-node/src/services/mergedEpisodePostProcess.js:290, …
  • `fs.mkdirSync` in `runMergedEpisodePostProcess` 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. — backend-node/src/services/mergedEpisodePostProcess.js:227
  • `fs.copyFileSync` in `runMergedEpisodePostProcess` 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) — backend-node/src/services/mergedEpisodePostProcess.js:294, backend-node/src/services/mergedEpisodePostProcess.js:310, backend-node/src/services/mergedEpisodePostProcess.js:316
  • `fs.writeFileSync` in `runMergedEpisodePostProcess` 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) — backend-node/src/services/mergedEpisodePostProcess.js:338, backend-node/src/services/mergedEpisodePostProcess.js:355
  • `fs.unlinkSync` in `runMergedEpisodePostProcess` 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) — backend-node/src/services/mergedEpisodePostProcess.js:410, backend-node/src/services/mergedEpisodePostProcess.js:425
  • `fs.readdirSync` in `runMergedEpisodePostProcess` 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. — backend-node/src/services/mergedEpisodePostProcess.js:423
  • `fs.rmdirSync` in `runMergedEpisodePostProcess` 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. — backend-node/src/services/mergedEpisodePostProcess.js:428
  • `fs.existsSync` in `runNarrationSubtitlePostProcess` 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) — backend-node/src/services/narrationVideoPostProcess.js:215, backend-node/src/services/narrationVideoPostProcess.js:268
  • `fs.mkdirSync` in `runNarrationSubtitlePostProcess` 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. — backend-node/src/services/narrationVideoPostProcess.js:229
  • `fs.copyFileSync` in `runNarrationSubtitlePostProcess` 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. — backend-node/src/services/narrationVideoPostProcess.js:272

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.
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 · 215 plain JS — the untyped files are REDACTED, backend-node/src/config/index.js, backend-node/src/config/videoGeneration.js, backend-node/src/constants/generationStylePresets.js, backend-node/src/db/index.js, backend-node/src/db/migrate.js (+209 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.
R10 · Code Duplication2.7 / 10Weak✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 9 duplicated blocks under backend-node/src/ have copies in at least two of the sibling directories routes, services, utils — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:456
  • 9 duplicated blocks under frontweb/src/ have copies in at least two of the sibling directories components, composables, utils, views — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — frontweb/src/composables/filmCreate/useProps.js:570
  • frontweb/src/composables/filmCreate/useProps.js:70 · frontweb/src/composables/filmCreate/useScenes.js:63 — the two spans are one implementation copied and then locally edited — 2424 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. — frontweb/src/composables/filmCreate/useProps.js:70
  • backend-node/src/services/mergedEpisodePostProcess.js:9 · backend-node/src/services/narrationVideoPostProcess.js:9 — the two spans are one implementation copied and then locally edited — 1978 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. — backend-node/src/services/mergedEpisodePostProcess.js:9
  • frontweb/src/composables/filmCreate/useCharacters.js:343 · frontweb/src/composables/filmCreate/useProps.js:305 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — frontweb/src/composables/filmCreate/useCharacters.js:343
  • backend-node/src/services/propLibraryService.js:12 · backend-node/src/services/sceneLibraryService.js:14 — the two spans are one implementation copied and then locally edited — 1372 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. — backend-node/src/services/propLibraryService.js:12
  • frontweb/src/composables/filmCreate/useCharacters.js:24 · frontweb/src/composables/filmCreate/useScenes.js:24 — the two spans are one implementation copied and then locally edited — 720 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. — frontweb/src/composables/filmCreate/useCharacters.js:24
  • backend-node/src/services/aiClient.js:377 · backend-node/src/services/aiClient.js:494 — the two spans are one implementation copied and then locally edited — 618 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. — backend-node/src/services/aiClient.js:377
  • backend-node/src/services/jimengMaterialHubService.js:158 · backend-node/src/services/modelArkAssetConfigService.js:110 — the two spans are one implementation copied and then locally edited — 531 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. — backend-node/src/services/jimengMaterialHubService.js:158
  • backend-node/src/services/backgroundExtractionService.js:60 · backend-node/src/services/propExtractionService.js:9 — the two spans are one implementation copied and then locally edited — 503 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. — backend-node/src/services/backgroundExtractionService.js:60
  • backend-node/src/services/imageService.js:86 · backend-node/src/services/imageService.js:307 — the two spans are one implementation copied and then locally edited — 530 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. — backend-node/src/services/imageService.js:86
  • frontweb/src/views/FilmCreate.vue:7690 · frontweb/src/views/FilmCreate.vue:8031 — 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. — frontweb/src/views/FilmCreate.vue:7690
  • backend-node/src/routes/characterLibrary.js:4 · backend-node/src/routes/propLibrary.js:4 · backend-node/src/routes/sceneLibrary.js:4 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 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. — backend-node/src/routes/characterLibrary.js:4
  • frontweb/src/components/Sd2AssetManagement.vue:626 · frontweb/src/components/Sd2AssetManagement.vue:722 — 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. — frontweb/src/components/Sd2AssetManagement.vue:626
  • REDACTED:456 · backend-node/src/services/imageService.js:1213 — the two spans are one implementation copied and then locally edited — 447 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:456
  • backend-node/src/utils/seedance2AssetGuards.js:21 · backend-node/src/utils/seedance2AssetGuards.js:85 — the two spans are one implementation copied and then locally edited — 266 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. — backend-node/src/utils/seedance2AssetGuards.js:21
  • frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:195 · frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue:240 — the two spans are one implementation copied and then locally edited — 307 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. — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:195
  • frontweb/src/composables/useCanvasEpisodeGenerate.js:148 · frontweb/src/composables/useCanvasEpisodeGenerate.js:199 — 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. — frontweb/src/composables/useCanvasEpisodeGenerate.js:148
  • backend-node/src/routes/assets.js:8 · backend-node/src/routes/characterLibrary.js:8 · backend-node/src/routes/propLibrary.js:8 · backend-node/src/routes/sceneLibrary.js:8 — the 4 copies are spread across 4 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. — backend-node/src/routes/assets.js:8
  • backend-node/src/services/characterLibraryService.js:125 · backend-node/src/services/propLibraryService.js:49 · backend-node/src/services/sceneLibraryService.js:50 — the 3 copies are spread across 3 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. — backend-node/src/services/characterLibraryService.js:125
  • backend-node/src/routes/aiConfig.js:4 · backend-node/src/routes/prop.js:5 — the two spans are one implementation copied and then locally edited — 335 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. — backend-node/src/routes/aiConfig.js:4
  • backend-node/src/services/sceneService.js:203 · backend-node/src/services/sceneService.js:260 — 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. — backend-node/src/services/sceneService.js:203
  • REDACTED:599 · REDACTED:721 · REDACTED:978 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:599
  • backend-node/src/services/dramaService.js:349 · backend-node/src/services/storyboardService.js:157 — the two spans are one implementation copied and then locally edited — 216 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. — backend-node/src/services/dramaService.js:349
  • backend-node/src/services/propService.js:182 · backend-node/src/services/sceneService.js:464 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — backend-node/src/services/propService.js:182
  • backend-node/src/services/aiConfigService.js:146 · backend-node/src/services/propService.js:66 — the two spans are one implementation copied and then locally edited — 409 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. — backend-node/src/services/aiConfigService.js:146
  • backend-node/src/services/dramaService.js:570 · backend-node/src/services/dramaService.js:602 — 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. — backend-node/src/services/dramaService.js:570
  • frontweb/src/views/FilmList.vue:450 · frontweb/src/views/FilmList.vue:497 · frontweb/src/views/FilmList.vue:545 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontweb/src/views/FilmList.vue:450
  • backend-node/src/services/sceneService.js:323 · backend-node/src/services/sceneService.js:399 — 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. — backend-node/src/services/sceneService.js:323
  • frontweb/src/views/FilmCreate.vue:5923 · frontweb/src/views/FilmCreate.vue:5968 — 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. — frontweb/src/views/FilmCreate.vue:5923
  • frontweb/src/views/FilmCreate.vue:5579 · frontweb/src/views/FilmCreate.vue:5611 — 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. — frontweb/src/views/FilmCreate.vue:5579
  • backend-node/src/services/characterLibraryService.js:859 · backend-node/src/services/characterLibraryService.js:925 — the two spans are one implementation copied and then locally edited — 217 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. — backend-node/src/services/characterLibraryService.js:859
  • backend-node/src/utils/safeJson.js:226 · backend-node/src/utils/safeJson.js:254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — backend-node/src/utils/safeJson.js:226
  • frontweb/src/views/FilmCreate.vue:7634 · frontweb/src/views/FilmCreate.vue:7990 — 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. — frontweb/src/views/FilmCreate.vue:7634
  • backend-node/src/services/assetService.js:1 · backend-node/src/services/imageService.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — backend-node/src/services/assetService.js:1
  • backend-node/src/services/imageClient.js:468 · backend-node/src/services/imageClient.js:654 — 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. — backend-node/src/services/imageClient.js:468
  • frontweb/src/composables/filmCreate/useCharacters.js:72 · frontweb/src/composables/filmCreate/useProps.js:73 · frontweb/src/composables/filmCreate/useScenes.js:66 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 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. — frontweb/src/composables/filmCreate/useCharacters.js:72
  • backend-node/src/services/aiClient.js:225 · backend-node/src/services/imageClient.js:135 — the two spans are one implementation copied and then locally edited — 156 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. — backend-node/src/services/aiClient.js:225
  • backend-node/src/services/characterLibraryService.js:494 · backend-node/src/services/characterLibraryService.js:551 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — backend-node/src/services/characterLibraryService.js:494
  • frontweb/src/views/DramaDetail.vue:649 · frontweb/src/views/DramaDetail.vue:719 · frontweb/src/views/DramaDetail.vue:791 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontweb/src/views/DramaDetail.vue:649

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.
R11 · Import Boundaries9.4 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • frontweb/src/main.js:9 imports element-plus/dist/locale/zh-cn.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — frontweb/src/main.js:9

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity0.0 / 10Critical✓ Tool-verified

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.

  • processImageGeneration has cyclomatic complexity 338 and cognitive complexity 730; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/imageService.js:586
  • pollVideoTask has cyclomatic complexity 186 and cognitive complexity 283; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:4506
  • _doImport has cyclomatic complexity 142 and cognitive complexity 207; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/dramaImportService.js:154
  • buildUniversalSegmentUserPromptBundle has cyclomatic complexity 131 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. — backend-node/src/services/universalSegmentPromptBundle.js:9
  • testConnection has cyclomatic complexity 115 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. — backend-node/src/services/aiConfigService.js:261
  • (anonymous) has cyclomatic complexity 103 and cognitive complexity 108; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontweb/src/components/AIConfigContent.vue:1586
  • callVideoApi has cyclomatic complexity 100 and cognitive complexity 131; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:4071
  • callSoraVideoApi has cyclomatic complexity 95 and cognitive complexity 147; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:2952
  • safeParseAIJSON has cyclomatic complexity 89 and cognitive complexity 259; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/utils/safeJson.js:180
  • callNanoBananaImageApi has cyclomatic complexity 87 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. — backend-node/src/services/imageClient.js:568
  • callImageApi has cyclomatic complexity 79 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. — backend-node/src/services/imageClient.js:1456
  • saveStoryboards has cyclomatic complexity 75 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. — backend-node/src/services/episodeStoryboardService.js:638
  • callDashScopeImageApi 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. — backend-node/src/services/imageClient.js:910
  • runMergedEpisodePostProcess has cyclomatic complexity 66 and cognitive complexity 130; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/mergedEpisodePostProcess.js:204
  • callViduVideoApi has cyclomatic complexity 64 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:2100
  • runOneClickPipeline has cyclomatic complexity 64 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. — frontweb/src/views/FilmCreate.vue:7340
  • polishClassicVideoPromptStream has cyclomatic complexity 61 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:777
  • runRepairPipeline has cyclomatic complexity 60 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. — frontweb/src/views/FilmCreate.vue:7781
  • generateStoryboard 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. — backend-node/src/services/episodeStoryboardService.js:1126
  • callVolcengineOmniVideoApi has cyclomatic complexity 56 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. — backend-node/src/services/videoClient.js:634
  • callJimengAiApiVideo has cyclomatic complexity 56 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:3330
  • callAgnesVideoApi has cyclomatic complexity 55 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:2711
  • polishPrompt has cyclomatic complexity 54 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:410
  • (anonymous) has cyclomatic complexity 52 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/imageClient.js:1744
  • pickProxyVideoUrl has cyclomatic complexity 52 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:1359
  • processPropImageGeneration has cyclomatic complexity 52 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/propImageGenerationService.js:21
  • onGenerateSbVideo has cyclomatic complexity 50 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontweb/src/views/FilmCreate.vue:6482
  • processVideoGeneration has cyclomatic complexity 50 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoService.js:472
  • saveCharacters has cyclomatic complexity 49 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/dramaService.js:558
  • exportDrama has cyclomatic complexity 49 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. — backend-node/src/services/dramaExportService.js:80
  • processStoryboardGeneration has cyclomatic complexity 48 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/episodeStoryboardService.js:862
  • callDashScopeVideoApi has cyclomatic complexity 48 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:1641
  • callXaiVideoApi has cyclomatic complexity 47 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. — backend-node/src/services/videoClient.js:3515
  • videoWorker has cyclomatic complexity 46 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontweb/src/views/FilmCreate.vue:6957
  • createConfig has cyclomatic complexity 45 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/aiConfigService.js:75
  • runGenerateStoryFromPremise has cyclomatic complexity 44 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontweb/src/composables/useStoryGeneration.js:12
  • callGeminiImageApi has cyclomatic complexity 43 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/imageClient.js:1215
  • processVideoMerge has cyclomatic complexity 43 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoMergeService.js:190
  • callMinimaxH3VideoApi has cyclomatic complexity 43 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:3942
  • callKlingVideoApi has cyclomatic complexity 42 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-node/src/services/videoClient.js:1481
R3 · Large Files1.7 / 10Critical✓ 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.

  • frontweb/src/views/FilmCreate.vue has 10394 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/FilmCreate.vue:1
  • backend-node/src/services/videoClient.js has 4637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/videoClient.js:1
  • frontweb/src/components/AIConfigContent.vue has 2759 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/AIConfigContent.vue:1
  • backend-node/src/services/imageClient.js has 1872 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/imageClient.js:1
  • backend-node/src/services/imageService.js has 1593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/imageService.js:1
  • backend-node/src/services/episodeStoryboardService.js has 1575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/episodeStoryboardService.js:1
  • frontweb/src/views/DramaDetail.vue has 1470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/DramaDetail.vue:1
  • backend-node/src/services/promptI18n.js has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/promptI18n.js:1
  • frontweb/src/views/FilmList.vue has 1279 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/FilmList.vue:1
  • frontweb/src/views/DramaCanvas.vue has 1053 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/DramaCanvas.vue:1
  • REDACTED has 1052 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • backend-node/src/services/characterLibraryService.js has 978 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/characterLibraryService.js:1
  • backend-node/src/services/dramaService.js has 832 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/dramaService.js:1
  • frontweb/src/composables/filmCreate/useCharacters.js has 814 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/composables/filmCreate/useCharacters.js:1
  • frontweb/src/components/Sd2AssetManagement.vue has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/Sd2AssetManagement.vue:1
  • backend-node/src/services/aiClient.js has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/aiClient.js:1
  • frontweb/src/components/UniversalSegmentOmniAtEditor.vue has 679 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/UniversalSegmentOmniAtEditor.vue:1
  • backend-node/src/services/framePromptService.js has 643 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/framePromptService.js:1
  • frontweb/src/composables/filmCreate/useProps.js has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/composables/filmCreate/useProps.js:1
  • frontweb/src/composables/filmCreate/useScenes.js has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/composables/filmCreate/useScenes.js:1
  • backend-node/src/services/videoService.js has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/videoService.js:1
  • frontweb/src/stores/generationTaskStore.js has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/stores/generationTaskStore.js:1
  • backend-node/src/services/aiConfigService.js has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/aiConfigService.js:1
  • frontweb/src/views/FreeCreate.vue has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/FreeCreate.vue:1
  • backend-node/src/db/migrate.js has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/db/migrate.js:1
  • frontweb/src/utils/dramaCanvasAdapter.js has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/utils/dramaCanvasAdapter.js:1
  • frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue:1
  • backend-node/src/services/universalSegmentPromptBundle.js has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/universalSegmentPromptBundle.js:1
  • backend-node/src/services/sceneService.js has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/sceneService.js:1
  • frontweb/src/views/MediaLibrary.vue has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/views/MediaLibrary.vue:1
  • backend-node/src/services/dramaImportService.js has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/dramaImportService.js:1
  • frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:1
  • backend-node/src/utils/safeJson.js has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/utils/safeJson.js:1
  • backend-node/src/services/dramaExportService.js has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/dramaExportService.js:1
  • backend-node/src/services/angleService.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/angleService.js:1
  • backend-node/src/services/mergedEpisodePostProcess.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend-node/src/services/mergedEpisodePostProcess.js:1
  • frontweb/src/components/SceneModelMap.vue has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontweb/src/components/SceneModelMap.vue:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage4.0 / 10Weak✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — frontweb/src/views/FilmCreate.vue:1, frontweb/src/components/AIConfigContent.vue:1, frontweb/src/views/DramaDetail.vue:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.5 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 41 application, 1 tooling and 38 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×32) — frontweb/src/views/FilmCreate.vue, frontweb/src/components/AIConfigContent.vue, frontweb/src/views/DramaDetail.vue, …
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasStoryboardNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasAssetNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/utils/dramaCanvasAdapter.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — frontweb/src/utils/storyboardMedia.js, frontweb/src/utils/canvasWorkflow.js
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasScriptNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontweb/src/components/dramaCanvas/CanvasScriptPanel.vue
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasMediaNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue
  • no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontweb/src/utils/canvasWorkflow.js, frontweb/src/utils/dramaCanvasAdapter.js, frontweb/src/utils/storyboardMedia.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontweb/src/utils/canvasLayout.js

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

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. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://cdn.tailwindcss.com` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — index.html:28
  • `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — backend-node/src/server.js:33

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
  • Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X2 · Cancellation propagation4.8 / 10Weak✓ Tool-verified

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 4/30 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.
  • `streamAgent` 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 })`. — frontweb/src/api/agent.js:13
  • `testConnection` 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 })`. — backend-node/src/services/aiConfigService.js:261
  • `callKlingImageApi` 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 })`. — backend-node/src/services/imageClient.js:426
  • `callNanoBananaImageApi` 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 })`. — backend-node/src/services/imageClient.js:568
  • `callGeminiImageApi` 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 })`. — backend-node/src/services/imageClient.js:1215
  • `hubJson` 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 })`. — backend-node/src/services/jimengMaterialHubService.js:206
  • `fetchSignedOpenApi` 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 })`. — backend-node/src/services/modelArkAssetProxyService.js:116
  • `fetchBearer` 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 })`. — backend-node/src/services/modelArkAssetProxyService.js:166
  • `callVolcengineOmniVideoApi` 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 })`. — backend-node/src/services/videoClient.js:634
  • `callKlingOmniVideoApi` 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 })`. — backend-node/src/services/videoClient.js:840
  • `callKlingVideoApi` 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 })`. — backend-node/src/services/videoClient.js:1481
  • `callDashScopeVideoApi` 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 })`. — backend-node/src/services/videoClient.js:1641
  • `callGeminiVideoApi` 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 })`. — backend-node/src/services/videoClient.js:1811
  • `callViduVideoApi` 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 })`. — backend-node/src/services/videoClient.js:2100
  • `resolveVeo3ImageForApi` 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 })`. — backend-node/src/services/videoClient.js:2322
  • `callVeo3VideoApi` 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 })`. — backend-node/src/services/videoClient.js:2420
  • `callAgnesVideoApi` 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 })`. — backend-node/src/services/videoClient.js:2711
  • `resolveSoraImageToDataUrl` 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 })`. — backend-node/src/services/videoClient.js:2908
  • `callSoraVideoApi` 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 })`. — backend-node/src/services/videoClient.js:2952
  • `resolveJimengApiImageBuffer` 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 })`. — backend-node/src/services/videoClient.js:3272
  • `callXaiVideoApi` 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 })`. — backend-node/src/services/videoClient.js:3515
  • `callMinimaxH3VideoApi` 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 })`. — backend-node/src/services/videoClient.js:3942
  • `callVideoApi` 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 })`. — backend-node/src/services/videoClient.js:4071
  • `pollVideoTask` 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 })`. — backend-node/src/services/videoClient.js:4506
  • `resolveVideoToLocalPath` 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 })`. — backend-node/src/services/videoMergeService.js:84
  • `downloadVideoToLocal` 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 })`. — backend-node/src/services/videoService.js:111

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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.

X25 · Inert configuration knob7.6 / 10Strong✓ Tool-verified

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

  • `callImageApi` accepts `opts.drama_id` from the caller and keeps it in `drama_id` on line 1462, where only it can read the value — but nothing ever reads `drama_id`. Setting `opts.drama_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `drama_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.drama_id` from the accepted options so callers stop setting a knob that does nothing. — backend-node/src/services/imageClient.js:1462
  • `callImageApi` accepts `opts.character_id` from the caller and keeps it in `character_id` on line 1464, where only it can read the value — but nothing ever reads `character_id`. Setting `opts.character_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `character_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.character_id` from the accepted options so callers stop setting a knob that does nothing. — backend-node/src/services/imageClient.js:1464
  • `callImageApi` accepts `opts.image_type` from the caller and keeps it in `image_type` on line 1465, where only it can read the value — but nothing ever reads `image_type`. Setting `opts.image_type` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `image_type` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.image_type` from the accepted options so callers stop setting a knob that does nothing. — backend-node/src/services/imageClient.js:1465
  • `callXaiVideoApi` accepts `opts.files_base_url` from the caller and keeps it in `files_base_url` on line 3524, where only it can read the value — but nothing ever reads `files_base_url`. Setting `opts.files_base_url` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `files_base_url` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.files_base_url` from the accepted options so callers stop setting a knob that does nothing. — backend-node/src/services/videoClient.js:3524

What to do

  • Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
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.

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.

X3 · Exception handling4.6 / 10Weak✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×14) — frontweb/src/views/DramaCanvas.vue:743, frontweb/src/views/DramaCanvas.vue:755, frontweb/src/views/FilmCreate.vue:2858, …
  • `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. (×15) — frontweb/src/views/DramaCanvas.vue:770, frontweb/src/views/DramaDetail.vue:957, frontweb/src/views/DramaDetail.vue:1033, …
  • `.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. (×11) — frontweb/src/views/DramaCanvas.vue:893, frontweb/src/views/FilmCreate.vue:4698, frontweb/src/views/FilmCreate.vue:4741, …

What to do

  • Swallowed exception (empty catch)

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).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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.

LensScoreRatingImpact
Code Health14.3Critical — gated by D1, D2, R1, R10, R2, R3, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96.5ExemplaryStrongest area.
Maturity67.4Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness30.9Weak — gated by D14, R6, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security25.9Weak — gated by D29, D36, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility40.0Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 39 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.

  • C3 Audit Trail — Not assessed: this repository stores data through 'better-sqlite3' (backend-node/src/db/index.js:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through 'better-sqlite3' (backend-node/src/db/index.js:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through 'better-sqlite3' (backend-node/src/db/index.js:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 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
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev` in backend-node/) kept running but served no page within 2 minutes. Likely cause (our sandbox): the package `js-yaml` is declared in package.json but was not installed in our sandbox, so the dependency install did not complete here. This is a limit of our sandbox, not of your repository. Last output: "at Module.require (node:internal/modules/cjs/loader:1335:12) / at require (node:internal/modules/helpers:136:16) / at Object.<anonymous> (<repo>/backend-node/src/config/index.js:3:14) / at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) { / code: 'MODULE_NOT_FOUND', / requireStack: [ / '<repo>/backend-node/src/config/index.js', / '<repo>/backend-node/src/server.js' / ] / } / Node.js v22.13.0 / Failed running 'src/server.js'" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: this repository stores data through 'better-sqlite3' (backend-node/src/db/index.js:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • D11 Test Reliability — Test reliability not included — no test command the analyzer could start
  • 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.
  • 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"]`.
  • D24 Comment Value — 744 of 821 comment blocks were not judged (721 in a non-Latin script, 23 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
  • D25 ADR Conformance — no ADRs to check
  • 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) — 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.
  • 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
  • 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 — no test command the analyzer could start
  • 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • 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.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 141 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×30
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 5 more in this group — see findings.md.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×27
  • Click handler on a non-interactive <div> frontweb/src/components/StylePickerButton.vue:4 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaCanvas.vue:152 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaCanvas.vue:167 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaCanvas.vue:182 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaCanvas.vue:195 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:84 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:306 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:340 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:367 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:394 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:421 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:449 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:485 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/DramaDetail.vue:519 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:53 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:60 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:97 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:341 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:447 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:454 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:603 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:702 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:1669 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:1710 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> frontweb/src/views/FilmCreate.vue:1860 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • + 2 more in this group — see findings.md.
AC1 · Text alternatives · <img> without a text alternative · ×23
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:307 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:341 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:368 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:395 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:422 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/DramaDetail.vue:450 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1670 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1712 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1714 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1718 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1861 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1862 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1865 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1920 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1921 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmCreate.vue:1924 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmList.vue:186 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmList.vue:240 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FilmList.vue:295 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FreeCreate.vue:114 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/FreeCreate.vue:142 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/MediaLibrary.vue:55 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative frontweb/src/views/MediaLibrary.vue:118 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D14 · License Compliance · Banned license · ×14
  • Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:299 — `@img/sharp-libvips-darwin-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-darwin-x64 REDACTED:315 — `@img/sharp-libvips-darwin-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-arm REDACTED:331 — `@img/sharp-libvips-linux-arm` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-arm64 REDACTED:347 — `@img/sharp-libvips-linux-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:363 — `@img/sharp-libvips-linux-ppc64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:379 — `@img/sharp-libvips-linux-riscv64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-s390x REDACTED:395 — `@img/sharp-libvips-linux-s390x` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-x64 REDACTED:411 — `@img/sharp-libvips-linux-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:427 — `@img/sharp-libvips-linuxmusl-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:443 — `@img/sharp-libvips-linuxmusl-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-wasm32 REDACTED:635 — `@img/sharp-wasm32` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-arm64 REDACTED:654 — `@img/sharp-win32-arm64` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-ia32 REDACTED:673 — `@img/sharp-win32-ia32` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-x64 REDACTED:692 — `@img/sharp-win32-x64` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
D35 · Change Coupling · Boundary-crossing change coupling · ×12
  • Boundary-crossing change coupling: aiConfigService.js ↔ AIConfigContent.vue backend-node/src/services/aiConfigService.js:1 — `backend-node/src/services/aiConfigService.js` (context backend-node) and `frontweb/src/components/AIConfigContent.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `755192a7` feat: 接入低价 Seedance2 视频厂商与全能多图; `baa692e4` 增加agnes厂商; `fe788485` Update DeepSeek model configuration — run `git show` on any of them.
  • Boundary-crossing change coupling: dramaService.js ↔ FilmCreate.vue backend-node/src/services/dramaService.js:1 — `backend-node/src/services/dramaService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 82% of the time (14 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `b9f21b16` 增加负面提示词。剧本生成时检测如果已有剧本可以选择覆盖和续集模式。; `ce07fb36` 角色认证 进一步优化。; `aac10c1e` 即梦提示词进一步优化,分镜长短根据即梦做了一部分优化。 — run `git show` on any of them.
  • Boundary-crossing change coupling: aiClient.js ↔ FilmCreate.vue backend-node/src/services/aiClient.js:1 — `backend-node/src/services/aiClient.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `72cc5271` 全能模式润色增强; `6a6b943b` 风格提示词优化,场景提示词优化,分镜提示词优化。优化长度和风格放到前面强调。; `58a09663` feat: v1.2.1 ref_image independent field + vision AI compatibility fixes — run `git show` on any of them.
  • Boundary-crossing change coupling: migrate.js ↔ FilmCreate.vue backend-node/src/db/migrate.js:1 — `backend-node/src/db/migrate.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 68% of the time (13 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `baa692e4` 增加agnes厂商; `cc6de648` 修复素材库和本剧库重复加入; `b9f21b16` 增加负面提示词。剧本生成时检测如果已有剧本可以选择覆盖和续集模式。 — run `git show` on any of them.
  • Boundary-crossing change coupling: promptI18n.js ↔ FilmCreate.vue backend-node/src/services/promptI18n.js:1 — `backend-node/src/services/promptI18n.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 67% of the time (12 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `83e456fa` 优化界面。分镜润色调整。; `72cc5271` 全能模式润色增强; `21240b9a` 全能模式下,提交参考图,不上传传统分镜的图片。 — run `git show` on any of them.
  • Boundary-crossing change coupling: imageService.js ↔ FilmCreate.vue backend-node/src/services/imageService.js:1 — `backend-node/src/services/imageService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 65% of the time (13 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `6a6b943b` 风格提示词优化,场景提示词优化,分镜提示词优化。优化长度和风格放到前面强调。; `7230f00e` 角色风格进一步强化,提示词bug修复; `23656502` 优化内部目录结构。 — run `git show` on any of them.
  • Boundary-crossing change coupling: videoService.js ↔ FilmCreate.vue backend-node/src/services/videoService.js:1 — `backend-node/src/services/videoService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 64% of the time (9 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `755192a7` feat: 接入低价 Seedance2 视频厂商与全能多图; `7b6c1a74` 支持h3,错误后能继续之前的查询; `baa692e4` 增加agnes厂商 — run `git show` on any of them.
  • Boundary-crossing change coupling: episodeStoryboardService.js ↔ FilmCreate.vue backend-node/src/services/episodeStoryboardService.js:1 — `backend-node/src/services/episodeStoryboardService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 64% of the time (14 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `aac10c1e` 即梦提示词进一步优化,分镜长短根据即梦做了一部分优化。; `7230f00e` 角色风格进一步强化,提示词bug修复; `b2f3d4dd` 对白烧录,字幕功能,水印。 — run `git show` on any of them.
  • Boundary-crossing change coupling: REDACTED ↔ FilmCreate.vue REDACTED:1 — `REDACTED` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7b6c1a74` 支持h3,错误后能继续之前的查询; `72cc5271` 全能模式润色增强; `8545bd88` 全能模式 — run `git show` on any of them.
  • Boundary-crossing change coupling: aiConfigService.js ↔ FilmCreate.vue backend-node/src/services/aiConfigService.js:1 — `backend-node/src/services/aiConfigService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `755192a7` feat: 接入低价 Seedance2 视频厂商与全能多图; `baa692e4` 增加agnes厂商; `63e38d67` 修复谷歌协议的bug,界面显示,优化取图片的方式。 — run `git show` on any of them.
  • Boundary-crossing change coupling: characterLibraryService.js ↔ FilmCreate.vue backend-node/src/services/characterLibraryService.js:1 — `backend-node/src/services/characterLibraryService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `baa692e4` 增加agnes厂商; `cc6de648` 修复素材库和本剧库重复加入; `b9f21b16` 增加负面提示词。剧本生成时检测如果已有剧本可以选择覆盖和续集模式。 — run `git show` on any of them.
  • Boundary-crossing change coupling: framePromptService.js ↔ FilmCreate.vue backend-node/src/services/framePromptService.js:1 — `backend-node/src/services/framePromptService.js` (context backend-node) and `frontweb/src/views/FilmCreate.vue` (context frontweb) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a6b943b` 风格提示词优化,场景提示词优化,分镜提示词优化。优化长度和风格放到前面强调。; `7230f00e` 角色风格进一步强化,提示词bug修复; `84aa550a` feat: UI优化、流水线状态同步、分镜截断检测与任务悬浮面板 — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <img> · ×4
  • Custom control with no accessible name on <img> frontweb/src/views/FilmCreate.vue:577 — This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <img> frontweb/src/views/FilmCreate.vue:674 — This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <img> frontweb/src/views/FilmCreate.vue:775 — This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <img> frontweb/src/views/FreeCreate.vue:114 — This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <h1> · ×4
  • Click handler on a non-interactive <h1> frontweb/src/views/AiConfig.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <h1> frontweb/src/views/DramaCanvas.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <h1> frontweb/src/views/DramaDetail.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <h1> frontweb/src/views/FilmCreate.vue:6 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities · Critical CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <label> that labels no control · ×3
  • <label> that labels no control frontweb/src/views/FilmCreate.vue:810 — 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.
  • <label> that labels no control frontweb/src/views/FilmCreate.vue:816 — 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.
  • <label> that labels no control frontweb/src/views/FilmCreate.vue:822 — 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 <span> · ×3
  • Click handler on a non-interactive <span> frontweb/src/views/FilmCreate.vue:538 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> frontweb/src/views/FilmCreate.vue:636 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> frontweb/src/views/FilmCreate.vue:737 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Focusable <div> isn't keyboard-operable · ×3
  • Focusable <div> isn't keyboard-operable frontweb/src/views/FilmCreate.vue:559 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
  • Focusable <div> isn't keyboard-operable frontweb/src/views/FilmCreate.vue:657 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
  • Focusable <div> isn't keyboard-operable frontweb/src/views/FilmCreate.vue:758 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×3
  • Click handler on a non-interactive <img> frontweb/src/views/FilmCreate.vue:577 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <img> frontweb/src/views/FilmCreate.vue:674 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <img> frontweb/src/views/FilmCreate.vue:775 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels · Editable <div> without an accessible name · ×1
  • Editable <div> without an accessible name frontweb/src/components/UniversalSegmentOmniAtEditor.vue:3 — This editable region is named only by a placeholder, which is not a name. An element made editable (contenteditable, or role="textbox"/"searchbox" with a tab stop or key handling) is a text-entry control, and it has no aria-label, no aria-labelledby and no title, so assistive tech announces an unnamed edit field. Point aria-labelledby at its visible caption, or add an aria-label.
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×1
  • Custom control with no accessible name on <div> frontweb/src/views/FreeCreate.vue:35 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · <button> with no accessible text · ×1
  • <button> with no accessible text index.html:188 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 1026 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 137 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×47
  • FunctionTooLong: storyboards.routes REDACTED:240 — FunctionTooLong — routes runs 696 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 596 over it, 6.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useCharacters.useCharacters frontweb/src/composables/filmCreate/useCharacters.js:23 — FunctionTooLong — useCharacters runs 656 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 556 over it, 6.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: episodeStoryboardService.tryIncrementalSave backend-node/src/services/episodeStoryboardService.js:588 — FunctionTooLong — tryIncrementalSave runs 552 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 452 over it, 5.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useProps.useProps frontweb/src/composables/filmCreate/useProps.js:21 — FunctionTooLong — useProps runs 485 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 385 over it, 4.85× 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: useScenes.useScenes frontweb/src/composables/filmCreate/useScenes.js:23 — FunctionTooLong — useScenes runs 480 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 380 over it, 4.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: generationTaskStore.useGenerationTaskStore frontweb/src/stores/generationTaskStore.js:71 — FunctionTooLong — useGenerationTaskStore runs 426 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 326 over it, 4.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: universalSegmentPromptBundle.buildUniversalSegmentUserPromptBundle backend-node/src/services/universalSegmentPromptBundle.js:9 — FunctionTooLong — buildUniversalSegmentUserPromptBundle runs 396 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 296 over it, 3.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: migrate.ensureAllColumns backend-node/src/db/migrate.js:99 — FunctionTooLong — ensureAllColumns runs 369 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 269 over it, 3.69× 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: videoClient.pollVideoTask backend-node/src/services/videoClient.js:4506 — FunctionTooLong — pollVideoTask runs 344 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 244 over it, 3.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: videoClient.callVideoApi backend-node/src/services/videoClient.js:4071 — FunctionTooLong — callVideoApi runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: characters.routes REDACTED:8 — FunctionTooLong — routes runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: dramaExportService.exportDrama backend-node/src/services/dramaExportService.js:80 — FunctionTooLong — exportDrama runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.setupRouter REDACTED:25 — FunctionTooLong — setupRouter runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: videoClient.callSoraVideoApi backend-node/src/services/videoClient.js:2952 — FunctionTooLong — callSoraVideoApi runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: dramaImportService._doImport backend-node/src/services/dramaImportService.js:154 — FunctionTooLong — _doImport runs 234 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 134 over it, 2.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: storyboards.routes.polishClassicVideoPromptStream REDACTED:777 — FunctionTooLong — routes.polishClassicVideoPromptStream runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: imageClient.callNanoBananaImageApi backend-node/src/services/imageClient.js:568 — FunctionTooLong — callNanoBananaImageApi runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× 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: generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode frontweb/src/stores/generationTaskStore.js:397 — FunctionTooLong — useGenerationTaskStore.recoverPendingForEpisode runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: imageClient.createAndGenerateImage backend-node/src/services/imageClient.js:1686 — FunctionTooLong — createAndGenerateImage runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: episodeStoryboardService.processStoryboardGeneration backend-node/src/services/episodeStoryboardService.js:862 — FunctionTooLong — processStoryboardGeneration runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useCanvasEpisodeGenerate.useCanvasEpisodeGenerate frontweb/src/composables/useCanvasEpisodeGenerate.js:31 — FunctionTooLong — useCanvasEpisodeGenerate runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: videoClient.callViduVideoApi backend-node/src/services/videoClient.js:2100 — FunctionTooLong — callViduVideoApi runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: imageClient.callDashScopeImageApi backend-node/src/services/imageClient.js:910 — FunctionTooLong — callDashScopeImageApi runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× 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: imageClient.callImageApi backend-node/src/services/imageClient.js:1456 — FunctionTooLong — callImageApi runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: promptI18n.getStoryboardSystemPrompt backend-node/src/services/promptI18n.js:92 — FunctionTooLong — getStoryboardSystemPrompt runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 22 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking REDACTED:77 — `fs.existsSync` in `app.get("/favicon.ico")` 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 backend-node/src/mastra/index.mjs:210 — `fs.mkdirSync` in `initAgent` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:351 — `fs.existsSync` in `sd2VoiceUpload` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:351 — `fs.mkdirSync` in `sd2VoiceUpload` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:355 — `fs.writeFileSync` in `sd2VoiceUpload` 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 backend-node/src/services/aiClient.js:660 — `fs.existsSync` in `generateTextWithVision` 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 backend-node/src/services/aiClient.js:663 — `fs.readFileSync` in `generateTextWithVision` 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 backend-node/src/services/imageService.js:110 — `fs.readFileSync` in `splitQuadGridToImages` 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 backend-node/src/services/imageService.js:145 — `fs.writeFileSync` in `splitQuadGridToImages` 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 backend-node/src/services/imageService.js:328 — `fs.readFileSync` in `splitNineGridToImages` 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 backend-node/src/services/imageService.js:363 — `fs.writeFileSync` in `splitNineGridToImages` 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 backend-node/src/services/imageService.js:426 — `fs.existsSync` in `normalizeLocalImageToTargetSize` 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 backend-node/src/services/imageService.js:435 — `fs.readFileSync` in `normalizeLocalImageToTargetSize` 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 backend-node/src/services/imageService.js:456 — `fs.writeFileSync` in `normalizeLocalImageToTargetSize` 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 backend-node/src/services/imageService.js:475 — `fs.existsSync` in `normalizeSavedImageToTargetPixels` 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 backend-node/src/services/imageService.js:510 — `fs.unlinkSync` in `normalizeSavedImageToTargetPixels` 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 backend-node/src/services/imageService.js:511 — `fs.renameSync` in `normalizeSavedImageToTargetPixels` 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 backend-node/src/services/imageService.js:516 — `fs.existsSync` in `normalizeSavedImageToTargetPixels` 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 backend-node/src/services/imageService.js:516 — `fs.unlinkSync` in `normalizeSavedImageToTargetPixels` 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 backend-node/src/services/mergedEpisodePostProcess.js:212 — `fs.existsSync` in `runMergedEpisodePostProcess` 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 backend-node/src/services/mergedEpisodePostProcess.js:227 — `fs.mkdirSync` in `runMergedEpisodePostProcess` 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 backend-node/src/services/mergedEpisodePostProcess.js:262 — `fs.existsSync` in `runMergedEpisodePostProcess` 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 backend-node/src/services/mergedEpisodePostProcess.js:290 — `fs.existsSync` in `runMergedEpisodePostProcess` 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 backend-node/src/services/mergedEpisodePostProcess.js:294 — `fs.copyFileSync` in `runMergedEpisodePostProcess` 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 backend-node/src/services/mergedEpisodePostProcess.js:310 — `fs.copyFileSync` in `runMergedEpisodePostProcess` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file frontweb/src/views/FilmCreate.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/AIConfigContent.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/views/DramaDetail.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/views/DramaCanvas.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/composables/filmCreate/useCharacters.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/views/FilmList.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/Sd2AssetManagement.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/stores/generationTaskStore.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/composables/filmCreate/useProps.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/composables/filmCreate/useScenes.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/utils/dramaCanvasAdapter.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file backend-node/src/db/migrate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/UniversalSegmentOmniAtEditor.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/SceneModelMap.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/views/FreeCreate.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/views/MediaLibrary.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/components/EpisodeBatchImportDialog.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/composables/useCanvasEpisodeGenerate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontweb/src/composables/useCanvasCrud.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×32
  • Outbound HTTP without resilience backend-node/src/services/aiConfigService.js:276 — `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 backend-node/src/services/aiConfigService.js:295 — `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 backend-node/src/services/aiConfigService.js:319 — `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 backend-node/src/services/aiConfigService.js:361 — `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 backend-node/src/services/aiConfigService.js:383 — `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 backend-node/src/services/aiConfigService.js:405 — `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 backend-node/src/services/aiConfigService.js:456 — `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 backend-node/src/services/imageClient.js:1278 — `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 backend-node/src/services/jimengMaterialHubService.js:246 — `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 backend-node/src/services/modelArkAssetProxyService.js:157 — `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 backend-node/src/services/modelArkAssetProxyService.js:179 — `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 backend-node/src/services/videoClient.js:790 — `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 backend-node/src/services/videoClient.js:939 — `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 backend-node/src/services/videoClient.js:1587 — `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 backend-node/src/services/videoClient.js:1768 — `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 backend-node/src/services/videoClient.js:1846 — `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 backend-node/src/services/videoClient.js:1883 — `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 backend-node/src/services/videoClient.js:2269 — `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 backend-node/src/services/videoClient.js:2395 — `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 backend-node/src/services/videoClient.js:2455 — `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 backend-node/src/services/videoClient.js:2848 — `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 backend-node/src/services/videoClient.js:2938 — `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 backend-node/src/services/videoClient.js:3034 — `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 backend-node/src/services/videoClient.js:3118 — `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 backend-node/src/services/videoClient.js:3220 — `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.
  • + 7 more in this group — see findings.md.
X2 · Cancellation propagation · Async function without AbortSignal · ×26
  • Async function without AbortSignal: streamAgent frontweb/src/api/agent.js:13 — `streamAgent` 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: testConnection backend-node/src/services/aiConfigService.js:261 — `testConnection` 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: callKlingImageApi backend-node/src/services/imageClient.js:426 — `callKlingImageApi` 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: callNanoBananaImageApi backend-node/src/services/imageClient.js:568 — `callNanoBananaImageApi` 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: callGeminiImageApi backend-node/src/services/imageClient.js:1215 — `callGeminiImageApi` 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: hubJson backend-node/src/services/jimengMaterialHubService.js:206 — `hubJson` 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: fetchSignedOpenApi backend-node/src/services/modelArkAssetProxyService.js:116 — `fetchSignedOpenApi` 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: fetchBearer backend-node/src/services/modelArkAssetProxyService.js:166 — `fetchBearer` 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: callVolcengineOmniVideoApi backend-node/src/services/videoClient.js:634 — `callVolcengineOmniVideoApi` 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: callKlingOmniVideoApi backend-node/src/services/videoClient.js:840 — `callKlingOmniVideoApi` 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: callKlingVideoApi backend-node/src/services/videoClient.js:1481 — `callKlingVideoApi` 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: callDashScopeVideoApi backend-node/src/services/videoClient.js:1641 — `callDashScopeVideoApi` 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: callGeminiVideoApi backend-node/src/services/videoClient.js:1811 — `callGeminiVideoApi` 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: callViduVideoApi backend-node/src/services/videoClient.js:2100 — `callViduVideoApi` 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: resolveVeo3ImageForApi backend-node/src/services/videoClient.js:2322 — `resolveVeo3ImageForApi` 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: callVeo3VideoApi backend-node/src/services/videoClient.js:2420 — `callVeo3VideoApi` 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: callAgnesVideoApi backend-node/src/services/videoClient.js:2711 — `callAgnesVideoApi` 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: resolveSoraImageToDataUrl backend-node/src/services/videoClient.js:2908 — `resolveSoraImageToDataUrl` 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: callSoraVideoApi backend-node/src/services/videoClient.js:2952 — `callSoraVideoApi` 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: resolveJimengApiImageBuffer backend-node/src/services/videoClient.js:3272 — `resolveJimengApiImageBuffer` 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: callXaiVideoApi backend-node/src/services/videoClient.js:3515 — `callXaiVideoApi` 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: callMinimaxH3VideoApi backend-node/src/services/videoClient.js:3942 — `callMinimaxH3VideoApi` 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: callVideoApi backend-node/src/services/videoClient.js:4071 — `callVideoApi` 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: pollVideoTask backend-node/src/services/videoClient.js:4506 — `pollVideoTask` 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: resolveVideoToLocalPath backend-node/src/services/videoMergeService.js:84 — `resolveVideoToLocalPath` 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 })`.
  • + 1 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×25
  • Swallowed exception (empty catch) frontweb/src/views/DramaCanvas.vue:743 — 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) frontweb/src/views/DramaCanvas.vue:755 — 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) frontweb/src/views/DramaCanvas.vue:893 — `.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) frontweb/src/views/FilmCreate.vue:2858 — 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) frontweb/src/views/FilmCreate.vue:3933 — 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) frontweb/src/views/FilmCreate.vue:4698 — `.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) frontweb/src/views/FilmCreate.vue:4741 — `.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) frontweb/src/views/FilmCreate.vue:4844 — 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) frontweb/src/views/FilmCreate.vue:4940 — `.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) frontweb/src/views/FilmCreate.vue:4978 — `.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) frontweb/src/views/FilmCreate.vue:5120 — `.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) frontweb/src/views/FilmCreate.vue:5130 — `.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) frontweb/src/views/FilmCreate.vue:5790 — 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) frontweb/src/views/FilmCreate.vue:5833 — 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) frontweb/src/views/FilmCreate.vue:6238 — 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) frontweb/src/views/FilmCreate.vue:6467 — 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) frontweb/src/views/FilmCreate.vue:6539 — `.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) frontweb/src/views/FilmCreate.vue:6736 — 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) frontweb/src/views/FilmCreate.vue:6774 — `.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) frontweb/src/views/FilmCreate.vue:6976 — `.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) frontweb/src/views/FilmCreate.vue:7000 — 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) frontweb/src/views/FilmCreate.vue:8163 — `.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) frontweb/src/views/FilmList.vue:794 — 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) frontweb/src/views/FreeCreate.vue:175 — 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) frontweb/src/views/FreeCreate.vue:206 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×21
  • Animation without a prefers-reduced-motion guard frontweb/src/views/DramaDetail.vue:1348 — `.episode-card` moves (`transition: border-color 0.25s, transform 0.2s, box-shadow 0.25s, background 0.2s`) 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 frontweb/src/views/DramaDetail.vue:1390 — `.episode-enter-icon` moves (`transition: transform 0.2s`) 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 frontweb/src/views/FilmCreate.vue:8318 — `.header` moves (`transition: margin-left 0.25s cubic-bezier(.4,0,.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 frontweb/src/views/FilmCreate.vue:8442 — `.quick-nav` moves (`transition: width 0.25s cubic-bezier(.4,0,.2,1), padding 0.25s cubic-bezier(.4,0,.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 frontweb/src/views/FilmCreate.vue:8504 — `.atp-spin-dot` moves (`animation: atp-pulse 1.2s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard frontweb/src/views/FilmCreate.vue:8538 — `.atp-item-dot` moves (`animation: atp-pulse 1.6s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard frontweb/src/views/FilmCreate.vue:8779 — `.spin` moves (`animation: navSpin 1s 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 frontweb/src/views/FilmCreate.vue:8823 — `.main` moves (`transition: margin-left 0.25s cubic-bezier(.4,0,.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 frontweb/src/views/FilmCreate.vue:8837 — `.card` moves (`transition: border-color 0.3s ease, box-shadow 0.3s ease, transform 0.3s 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 frontweb/src/views/FilmCreate.vue:8931 — `.pipeline-task-dot` moves (`animation: pipeline-dot-pulse 1.2s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard frontweb/src/views/FilmCreate.vue:9524 — `html.light .asset-item:hover` moves (`transition: box-shadow 0.25s, transform 0.2s, border-color 0.25s`) 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 frontweb/src/views/FilmCreate.vue:9629 — `.storyboard-row` moves (`transition: border-color 0.25s ease, box-shadow 0.25s ease, transform 0.25s 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 frontweb/src/views/FilmCreate.vue:9630 — `.storyboard-row` moves (`animation: sb-fade-in 0.35s 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.
  • Animation without a prefers-reduced-motion guard frontweb/src/views/FilmCreate.vue:10477 — `.sb-gen-dot` moves (`animation: sb-dot-bounce 1.2s infinite ease-in-out 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 frontweb/src/views/FilmList.vue:994 — `.project-card` moves (`transition: border-color 0.25s, background 0.25s, transform 0.25s, box-shadow 0.25s`) 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 frontweb/src/styles/theme.css:288 — `html.light .project-card` moves (`transition: transform 0.2s ease, box-shadow 0.2s ease, border-color 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard frontweb/src/styles/theme.css:408 — `html.light .episode-card` moves (`transition: transform 0.15s, box-shadow 0.15s`) 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 frontweb/src/components/StylePickerButton.vue:306 — `.spd-item` moves (`transition: border-color 0.15s, transform 0.1s`) 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 frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:372 — `.spinner` moves (`animation: spin 0.75s 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 frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue:220 — `.spinner` moves (`animation: spin 0.75s 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 frontweb/src/components/dramaCanvas/CanvasNodeStatusOverlay.vue:45 — `.spinner` moves (`animation: spin 0.75s 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×15
  • Swallowed exception (caught, then discarded) frontweb/src/views/DramaCanvas.vue:770 — `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) frontweb/src/views/DramaDetail.vue:957 — `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) frontweb/src/views/DramaDetail.vue:1033 — `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) frontweb/src/views/DramaDetail.vue:1062 — `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) frontweb/src/views/DramaDetail.vue:1090 — `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) frontweb/src/views/FilmCreate.vue:4805 — `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) frontweb/src/views/FilmCreate.vue:5083 — `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) frontweb/src/views/FilmCreate.vue:6404 — `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) frontweb/src/views/FilmCreate.vue:6491 — `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) frontweb/src/views/FilmCreate.vue:6525 — `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) frontweb/src/views/FilmCreate.vue:6654 — `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) frontweb/src/views/FilmList.vue:495 — `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) frontweb/src/views/FilmList.vue:543 — `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) frontweb/src/views/FilmList.vue:590 — `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) frontweb/src/views/FilmList.vue:776 — `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.
D30 · Dependency Vulnerabilities · Medium CVE · ×13
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×11
  • FileTooLong: services/videoClient.js backend-node/src/services/videoClient.js — FileTooLong — 3639 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 3139 over it, 7.28× 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: services/imageClient.js backend-node/src/services/imageClient.js — FileTooLong — 1426 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 926 over it, 2.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: services/episodeStoryboardService.js backend-node/src/services/episodeStoryboardService.js — FileTooLong — 1260 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 760 over it, 2.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: services/imageService.js backend-node/src/services/imageService.js — FileTooLong — 1245 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 745 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: services/promptI18n.js backend-node/src/services/promptI18n.js — FileTooLong — 1213 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 713 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 79% of them inside a single declaration: routes (240-1114). The bar is 500 significant lines; this is 382 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: services/characterLibraryService.js backend-node/src/services/characterLibraryService.js — FileTooLong — 779 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 279 over it, 1.56× 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: services/dramaService.js backend-node/src/services/dramaService.js — FileTooLong — 684 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 184 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: filmCreate/useCharacters.js frontweb/src/composables/filmCreate/useCharacters.js — FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: useCharacters (23-877). The bar is 500 significant lines; this is 165 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: services/aiClient.js backend-node/src/services/aiClient.js — FileTooLong — 573 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 73 over it, 1.15× 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: services/framePromptService.js backend-node/src/services/framePromptService.js — FileTooLong — 515 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 15 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×6
  • Hotspot: backend-node/src/services/videoClient.js backend-node/src/services/videoClient.js:4506 — backend-node/src/services/videoClient.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 191 in videoClient.pollVideoTask at line 4506. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- backend-node/src/services/videoClient.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: backend-node/src/services/imageClient.js backend-node/src/services/imageClient.js:910 — backend-node/src/services/imageClient.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in imageClient.callDashScopeImageApi at line 910. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- backend-node/src/services/imageClient.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: backend-node/src/services/videoService.js backend-node/src/services/videoService.js:472 — backend-node/src/services/videoService.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in videoService.processVideoGeneration at line 472. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- backend-node/src/services/videoService.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: frontweb/src/components/AIConfigContent.vue frontweb/src/components/AIConfigContent.vue:1732 — frontweb/src/components/AIConfigContent.vue changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in onProviderChange at line 1732. 2 of those changes were fix/bug commits, 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- frontweb/src/components/AIConfigContent.vue`: 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: backend-node/src/services/aiClient.js backend-node/src/services/aiClient.js:493 — backend-node/src/services/aiClient.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in aiClient.streamGenerateText at line 493. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- backend-node/src/services/aiClient.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: backend-node/src/services/aiConfigService.js backend-node/src/services/aiConfigService.js:75 — backend-node/src/services/aiConfigService.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in aiConfigService.createConfig at line 75. 1 of those changes was a fix/bug commit, and the other 1 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-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 08:46:42 +08:00' --until='2026-11-17 08:46:42 +08:00' --full-history --no-merges -- backend-node/src/services/aiConfigService.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.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: DramaDetail.vue ↔ FilmCreate.vue frontweb/src/views/DramaDetail.vue:1 — `frontweb/src/views/DramaDetail.vue` and `frontweb/src/views/FilmCreate.vue` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `3efaa18b` feat: add the drama assistant drawer; `9a1a4c63` feat(剧集管理): 添加批量导入剧集功能; `7230f00e` 角色风格进一步强化,提示词bug修复 — run `git show` on any of them.
  • Change coupling: AIConfigContent.vue ↔ FilmCreate.vue frontweb/src/components/AIConfigContent.vue:1 — `frontweb/src/components/AIConfigContent.vue` and `frontweb/src/views/FilmCreate.vue` change together 54% of the time (19 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `755192a7` feat: 接入低价 Seedance2 视频厂商与全能多图; `7b6c1a74` 支持h3,错误后能继续之前的查询; `baa692e4` 增加agnes厂商 — run `git show` on any of them.
  • Change coupling: DramaDetail.vue ↔ FilmList.vue frontweb/src/views/DramaDetail.vue:1 — `frontweb/src/views/DramaDetail.vue` and `frontweb/src/views/FilmList.vue` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `49b782d8` 当前选中的格子显示绿色边框 + ✓ 图标 悬停未选中的格子显示蓝色边框 + 方位名称(左上/右上/左下/右下) 四宫格未选主图时,上方显示…; `19eef568` v1.2.0 - Gemini图片/视频支持 + 参考图图床方案 + API协议字段 + 多项修复; `6aa0537a` v1.1.9 — run `git show` on any of them.
  • Change coupling: characterLibraryService.js ↔ framePromptService.js backend-node/src/services/characterLibraryService.js:1 — `backend-node/src/services/characterLibraryService.js` and `backend-node/src/services/framePromptService.js` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4c30fec8` feat(业务场景模型映射): 实现业务场景与AI模型的映射配置功能; `6a6b943b` 风格提示词优化,场景提示词优化,分镜提示词优化。优化长度和风格放到前面强调。; `7230f00e` 角色风格进一步强化,提示词bug修复 — run `git show` on any of them.
  • Change coupling: episodeStoryboardService.js ↔ framePromptService.js backend-node/src/services/episodeStoryboardService.js:1 — `backend-node/src/services/episodeStoryboardService.js` and `backend-node/src/services/framePromptService.js` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4c30fec8` feat(业务场景模型映射): 实现业务场景与AI模型的映射配置功能; `7230f00e` 角色风格进一步强化,提示词bug修复; `84aa550a` feat: UI优化、流水线状态同步、分镜截断检测与任务悬浮面板 — run `git show` on any of them.
D12 · Dependency Hygiene · Deprecated · ×4
  • Deprecated: multer backend-node/package.json:27 — multer 1.4.5-lts.2, declared in backend-node/package.json, is marked deprecated by its publisher: "Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: uuid backend-node/package.json:29 — uuid 10.0.0, declared in backend-node/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: multer desktop/package.json:33 — multer 1.4.5-lts.2, declared in desktop/package.json, is marked deprecated by its publisher: "Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: uuid desktop/package.json:35 — uuid 10.0.0, declared in desktop/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×4
  • Guard cannot change the result — returns what the code already falls through to backend-node/src/services/imageService.js:77 — The guard above `return 1;` also returns `1`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
  • Guard cannot change the result — returns what the code already falls through to backend-node/src/services/modelArkAssetProxyService.js:63 — The guard above `return 'cn-beijing';` also returns `'cn-beijing'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
  • Guard cannot change the result — returns what the code already falls through to backend-node/src/services/videoClient.js:3477 — The guard above `return '720p';` also returns `'720p'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
  • Guard cannot change the result — returns what the code already falls through to backend-node/src/services/videoClient.js:3884 — The guard above `return '768P';` also returns `'768P'`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
X25 · Inert configuration knob · Option is kept and never read · ×4
  • Option is kept and never read backend-node/src/services/imageClient.js:1462 — `callImageApi` accepts `opts.drama_id` from the caller and keeps it in `drama_id` on line 1462, where only it can read the value — but nothing ever reads `drama_id`. Setting `opts.drama_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `drama_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.drama_id` from the accepted options so callers stop setting a knob that does nothing.
  • Option is kept and never read backend-node/src/services/imageClient.js:1464 — `callImageApi` accepts `opts.character_id` from the caller and keeps it in `character_id` on line 1464, where only it can read the value — but nothing ever reads `character_id`. Setting `opts.character_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `character_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.character_id` from the accepted options so callers stop setting a knob that does nothing.
  • Option is kept and never read backend-node/src/services/imageClient.js:1465 — `callImageApi` accepts `opts.image_type` from the caller and keeps it in `image_type` on line 1465, where only it can read the value — but nothing ever reads `image_type`. Setting `opts.image_type` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `image_type` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.image_type` from the accepted options so callers stop setting a knob that does nothing.
  • Option is kept and never read backend-node/src/services/videoClient.js:3524 — `callXaiVideoApi` accepts `opts.files_base_url` from the caller and keeps it in `files_base_url` on line 3524, where only it can read the value — but nothing ever reads `files_base_url`. Setting `opts.files_base_url` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `files_base_url` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `opts.files_base_url` from the accepted options so callers stop setting a knob that does nothing.
AC1 · Text alternatives · <video> without a captions track · ×3
  • <video> without a captions track frontweb/src/views/FilmCreate.vue:1654 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track frontweb/src/views/FreeCreate.vue:107 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track frontweb/src/views/MediaLibrary.vue:111 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: useCharacters frontweb/src/composables/filmCreate/useCharacters.js:1 — ClassTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 256 over it, 1.64× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: useProps frontweb/src/composables/filmCreate/useProps.js:1 — ClassTooLong — 485 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 85 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: useScenes frontweb/src/composables/filmCreate/useScenes.js:1 — ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×2
  • Both branches are identical — the condition decides nothing backend-node/src/services/aiConfigService.js:314 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing backend-node/src/services/videoClient.js:4606 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×2
  • Duplicated block (28 lines × 2 locations) backend-node/src/services/sceneService.js:323 — backend-node/src/services/sceneService.js:323 · backend-node/src/services/sceneService.js:399 — 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 (28 lines × 2 locations) frontweb/src/views/FilmCreate.vue:5923 — frontweb/src/views/FilmCreate.vue:5923 · frontweb/src/views/FilmCreate.vue:5968 — 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.
R7 · Dead Code · Dead file (~210 LoC) · ×2
  • Dead file (~210 LoC) frontweb/src/components/StylePickerButton.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~210 LoC) frontweb/src/utils/exportStoryboardSheet.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~131 LoC) · ×2
  • Dead file (~131 LoC) frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasMediaNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~131 LoC) frontweb/src/stores/film.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~86 LoC) · ×2
  • Dead file (~86 LoC) frontweb/src/components/dramaCanvas/CanvasAssetNode.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~86 LoC) frontweb/src/utils/canvasLayout.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontweb/src/utils/canvasWorkflow.js, frontweb/src/utils/dramaCanvasAdapter.js, frontweb/src/utils/storyboardMedia.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 frontweb/src/views/FilmList.vue:57 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark index.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×1
  • Heading level jumps from h2 to h4 index.html:666 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast colour pair (4.4 · ×1
  • Low contrast colour pair (4.4:1) frontweb/src/views/FilmCreate.vue:2466 — The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.3 · ×1
  • Low contrast colour pair in CSS (2.3:1) frontweb/src/views/FilmCreate.vue:9537 — `html.light .cover-placeholder` sets color: #9ca3af on background-color: #f3f4f6 — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1
  • Low contrast colour pair in CSS (4.4:1) frontweb/src/views/FilmCreate.vue:9541 — `html.light .cover-placeholder.error` sets color: #dc2626 on background-color: #fef2f2 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.3 · ×1
  • Low contrast colour pair in CSS (3.3:1) frontweb/src/views/FilmCreate.vue:10024 — `html.light .sb-ctrl-mode-btn.el-button:hover` sets color: #fff on background-color: #16a34a — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×1
  • Low contrast colour pair in CSS (2.8:1) frontweb/src/views/MediaLibrary.vue:373 — `.check-icon` sets color: #409eff on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.0 · ×1
  • Low contrast colour pair in CSS (2.0:1) frontweb/src/components/AIConfigContent.vue:2540 — `.one-key-not-recommended` sets color: #e6a23c on background-color: #fdf6ec — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.4 · ×1
  • Low contrast colour pair in CSS (2.4:1) frontweb/src/components/AIConfigContent.vue:2740 — `.ep-auto-badge` sets color: #409eff on background-color: #e6f1ff — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.0 · ×1
  • Low contrast colour pair in CSS (3.0:1) frontweb/src/components/AIConfigContent.vue:2791 — `.ep-badge-gemini` sets color: #b8860b on background-color: #fef6e0 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement frontweb/src/views/DramaDetail.vue:1462 — `.res-tab` 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.
C2 · Access Controls · No authorization · ×1
  • No authorization REDACTED:28 — This repository serves requests — express() (REDACTED:28) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
D1 · Cyclomatic Complexity · processImageGeneration (cyclomatic 345) · ×1
  • processImageGeneration (cyclomatic 345) backend-node/src/services/imageService.js:586 — processImageGeneration has cyclomatic complexity 345 (threshold 15). Of this number, 338 points are the body's own statements and 7 belong to 13 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · videoClient.pollVideoTask (cyclomatic 191) · ×1
  • videoClient.pollVideoTask (cyclomatic 191) backend-node/src/services/videoClient.js:4506 — videoClient.pollVideoTask has cyclomatic complexity 191 (threshold 15). Of this number, 186 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · buildUniversalSegmentUserPromptBundle (cyclomatic 146) · ×1
  • buildUniversalSegmentUserPromptBundle (cyclomatic 146) backend-node/src/services/universalSegmentPromptBundle.js:9 — buildUniversalSegmentUserPromptBundle has cyclomatic complexity 146 (threshold 15). Of this number, 131 points are the body's own statements and 15 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.
D1 · Cyclomatic Complexity · _doImport (cyclomatic 142) · ×1
  • _doImport (cyclomatic 142) backend-node/src/services/dramaImportService.js:154 — _doImport has cyclomatic complexity 142 (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.
D1 · Cyclomatic Complexity · testConnection (cyclomatic 115) · ×1
  • testConnection (cyclomatic 115) backend-node/src/services/aiConfigService.js:261 — testConnection has cyclomatic complexity 115 (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.
D1 · Cyclomatic Complexity · videoClient.callVideoApi (cyclomatic 101) · ×1
  • videoClient.callVideoApi (cyclomatic 101) backend-node/src/services/videoClient.js:4071 — videoClient.callVideoApi has cyclomatic complexity 101 (threshold 15). Of this number, 100 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.
D1 · Cyclomatic Complexity · exportDrama (cyclomatic 100) · ×1
  • exportDrama (cyclomatic 100) backend-node/src/services/dramaExportService.js:80 — exportDrama has cyclomatic complexity 100 (threshold 15). Of this number, 49 points are the body's own statements and 51 belong to 23 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.
D1 · Cyclomatic Complexity · videoClient.callSoraVideoApi (cyclomatic 95) · ×1
  • videoClient.callSoraVideoApi (cyclomatic 95) backend-node/src/services/videoClient.js:2952 — videoClient.callSoraVideoApi has cyclomatic complexity 95 (threshold 15). To reduce it, separate the cases: extract each independent 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 · safeJson.safeParseAIJSON (cyclomatic 92) · ×1
  • safeJson.safeParseAIJSON (cyclomatic 92) backend-node/src/utils/safeJson.js:180 — safeJson.safeParseAIJSON has cyclomatic complexity 92 (threshold 15). Of this number, 89 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.
D1 · Cyclomatic Complexity · imageClient.callNanoBananaImageApi (cyclomatic 90) · ×1
  • imageClient.callNanoBananaImageApi (cyclomatic 90) backend-node/src/services/imageClient.js:568 — imageClient.callNanoBananaImageApi has cyclomatic complexity 90 (threshold 15). Of this number, 88 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.
D1 · Cyclomatic Complexity · callImageApi (cyclomatic 80) · ×1
  • callImageApi (cyclomatic 80) backend-node/src/services/imageClient.js:1456 — callImageApi has cyclomatic complexity 80 (threshold 15). Of this number, 79 points are the body's own statements and 1 belongs 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.
D1 · Cyclomatic Complexity · saveStoryboards (cyclomatic 77) · ×1
  • saveStoryboards (cyclomatic 77) backend-node/src/services/episodeStoryboardService.js:638 — saveStoryboards has cyclomatic complexity 77 (threshold 15). Of this number, 75 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · imageClient.callDashScopeImageApi (cyclomatic 76) · ×1
  • imageClient.callDashScopeImageApi (cyclomatic 76) backend-node/src/services/imageClient.js:910 — imageClient.callDashScopeImageApi has cyclomatic complexity 76 (threshold 15). Of this number, 73 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · imageClient.createAndGenerateImage (cyclomatic 75) · ×1
  • imageClient.createAndGenerateImage (cyclomatic 75) backend-node/src/services/imageClient.js:1686 — imageClient.createAndGenerateImage has cyclomatic complexity 75 (threshold 15). Of this number, 24 points are the body's own statements and 51 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.
D1 · Cyclomatic Complexity · videoClient.callDashScopeVideoApi (cyclomatic 68) · ×1
  • videoClient.callDashScopeVideoApi (cyclomatic 68) backend-node/src/services/videoClient.js:1641 — videoClient.callDashScopeVideoApi has cyclomatic complexity 68 (threshold 15). Of this number, 48 points are the body's own statements and 20 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.
D1 · Cyclomatic Complexity · episodeStoryboardService.generateStoryboard (cyclomatic 66) · ×1
  • episodeStoryboardService.generateStoryboard (cyclomatic 66) backend-node/src/services/episodeStoryboardService.js:1126 — episodeStoryboardService.generateStoryboard has cyclomatic complexity 66 (threshold 15). Of this number, 61 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.
D1 · Cyclomatic Complexity · mergedEpisodePostProcess.runMergedEpisodePostProcess (cyclomatic 66) · ×1
  • mergedEpisodePostProcess.runMergedEpisodePostProcess (cyclomatic 66) backend-node/src/services/mergedEpisodePostProcess.js:204 — mergedEpisodePostProcess.runMergedEpisodePostProcess has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · routes.polishClassicVideoPromptStream (cyclomatic 65) · ×1
  • routes.polishClassicVideoPromptStream (cyclomatic 65) REDACTED:777 — routes.polishClassicVideoPromptStream has cyclomatic complexity 65 (threshold 15). Of this number, 61 points are the body's own statements and 4 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoClient.callViduVideoApi (cyclomatic 64) · ×1
  • videoClient.callViduVideoApi (cyclomatic 64) backend-node/src/services/videoClient.js:2100 — videoClient.callViduVideoApi has cyclomatic complexity 64 (threshold 15). To reduce it, separate the cases: extract each independent 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 · storyboards.routes.polishClassicVideoPromptStream (cyclomatic 63) · ×1
  • storyboards.routes.polishClassicVideoPromptStream (cyclomatic 63) REDACTED:777 — storyboards.routes.polishClassicVideoPromptStream has cyclomatic complexity 63 (threshold 15). Of this number, 59 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.
D1 · Cyclomatic Complexity · videoClient.callVolcengineOmniVideoApi (cyclomatic 63) · ×1
  • videoClient.callVolcengineOmniVideoApi (cyclomatic 63) backend-node/src/services/videoClient.js:634 — videoClient.callVolcengineOmniVideoApi has cyclomatic complexity 63 (threshold 15). Of this number, 56 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · processStoryboardGeneration (cyclomatic 57) · ×1
  • processStoryboardGeneration (cyclomatic 57) backend-node/src/services/episodeStoryboardService.js:862 — processStoryboardGeneration has cyclomatic complexity 57 (threshold 15). Of this number, 48 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · videoClient.callJimengAiApiVideo (cyclomatic 56) · ×1
  • videoClient.callJimengAiApiVideo (cyclomatic 56) backend-node/src/services/videoClient.js:3330 — videoClient.callJimengAiApiVideo has cyclomatic complexity 56 (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 · generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode (cyclomatic 56) · ×1
  • generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode (cyclomatic 56) frontweb/src/stores/generationTaskStore.js:397 — generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode has cyclomatic complexity 56 (threshold 15). Of this number, 32 points are the body's own statements and 24 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.
D1 · Cyclomatic Complexity · routes.polishPrompt (cyclomatic 56) · ×1
  • routes.polishPrompt (cyclomatic 56) REDACTED:410 — routes.polishPrompt has cyclomatic complexity 56 (threshold 15). Of this number, 54 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.
D1 · Cyclomatic Complexity · videoClient.callAgnesVideoApi (cyclomatic 55) · ×1
  • videoClient.callAgnesVideoApi (cyclomatic 55) backend-node/src/services/videoClient.js:2711 — videoClient.callAgnesVideoApi has cyclomatic complexity 55 (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.
D1 · Cyclomatic Complexity · storyboards.routes.polishPrompt (cyclomatic 54) · ×1
  • storyboards.routes.polishPrompt (cyclomatic 54) REDACTED:410 — storyboards.routes.polishPrompt has cyclomatic complexity 54 (threshold 15). Of this number, 52 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.
D1 · Cyclomatic Complexity · propImageGenerationService.processPropImageGeneration (cyclomatic 52) · ×1
  • propImageGenerationService.processPropImageGeneration (cyclomatic 52) backend-node/src/services/propImageGenerationService.js:21 — propImageGenerationService.processPropImageGeneration has cyclomatic complexity 52 (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.
D1 · Cyclomatic Complexity · videoClient.pickProxyVideoUrl (cyclomatic 52) · ×1
  • videoClient.pickProxyVideoUrl (cyclomatic 52) backend-node/src/services/videoClient.js:1359 — videoClient.pickProxyVideoUrl has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · videoService.processVideoGeneration (cyclomatic 50) · ×1
  • videoService.processVideoGeneration (cyclomatic 50) backend-node/src/services/videoService.js:472 — videoService.processVideoGeneration has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent 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 · saveCharacters (cyclomatic 49) · ×1
  • saveCharacters (cyclomatic 49) backend-node/src/services/dramaService.js:558 — saveCharacters 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.
D1 · Cyclomatic Complexity · videoClient.callXaiVideoApi (cyclomatic 48) · ×1
  • videoClient.callXaiVideoApi (cyclomatic 48) backend-node/src/services/videoClient.js:3515 — videoClient.callXaiVideoApi has cyclomatic complexity 48 (threshold 15). Of this number, 47 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.
D1 · Cyclomatic Complexity · imageClient.callGeminiImageApi (cyclomatic 45) · ×1
  • imageClient.callGeminiImageApi (cyclomatic 45) backend-node/src/services/imageClient.js:1215 — imageClient.callGeminiImageApi has cyclomatic complexity 45 (threshold 15). Of this number, 43 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.
D1 · Cyclomatic Complexity · createConfig (cyclomatic 45) · ×1
  • createConfig (cyclomatic 45) backend-node/src/services/aiConfigService.js:75 — createConfig 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.
D1 · Cyclomatic Complexity · runGenerateStoryFromPremise (cyclomatic 45) · ×1
  • runGenerateStoryFromPremise (cyclomatic 45) frontweb/src/composables/useStoryGeneration.js:12 — runGenerateStoryFromPremise has cyclomatic complexity 45 (threshold 15). Of this number, 44 points are the body's own statements and 1 belongs 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.
D1 · Cyclomatic Complexity · videoMergeService.processVideoMerge (cyclomatic 44) · ×1
  • videoMergeService.processVideoMerge (cyclomatic 44) backend-node/src/services/videoMergeService.js:190 — videoMergeService.processVideoMerge has cyclomatic complexity 44 (threshold 15). Of this number, 43 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.
D1 · Cyclomatic Complexity · videoClient.callMinimaxH3VideoApi (cyclomatic 43) · ×1
  • videoClient.callMinimaxH3VideoApi (cyclomatic 43) backend-node/src/services/videoClient.js:3942 — videoClient.callMinimaxH3VideoApi 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.
D1 · Cyclomatic Complexity · processCharacterGeneration (cyclomatic 43) · ×1
  • processCharacterGeneration (cyclomatic 43) backend-node/src/services/characterGenerationService.js:35 — processCharacterGeneration has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · videoClient.callKlingVideoApi (cyclomatic 42) · ×1
  • videoClient.callKlingVideoApi (cyclomatic 42) backend-node/src/services/videoClient.js:1481 — videoClient.callKlingVideoApi has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent 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 · routes.create (cyclomatic 39) · ×1
  • routes.create (cyclomatic 39) backend-node/src/routes/videos.js:18 — routes.create 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.
D1 · Cyclomatic Complexity · deriveStoryboardFieldsFromAi (cyclomatic 39) · ×1
  • deriveStoryboardFieldsFromAi (cyclomatic 39) backend-node/src/services/episodeStoryboardService.js:393 — deriveStoryboardFieldsFromAi has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · generateStory (cyclomatic 39) · ×1
  • generateStory (cyclomatic 39) backend-node/src/services/storyGenerationService.js:9 — generateStory has cyclomatic complexity 39 (threshold 15). Of this number, 32 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · (anonymous).recoverPendingForEpisode (cyclomatic 39) · ×1
  • (anonymous).recoverPendingForEpisode (cyclomatic 39) frontweb/src/stores/generationTaskStore.js:397 — (anonymous).recoverPendingForEpisode 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.
D1 · Cyclomatic Complexity · imageClient.callKlingImageApi (cyclomatic 38) · ×1
  • imageClient.callKlingImageApi (cyclomatic 38) backend-node/src/services/imageClient.js:426 — imageClient.callKlingImageApi has cyclomatic complexity 38 (threshold 15). Of this number, 36 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.
D1 · Cyclomatic Complexity · buildHubContext (cyclomatic 38) · ×1
  • buildHubContext (cyclomatic 38) backend-node/src/services/jimengMaterialHubService.js:58 — buildHubContext has cyclomatic complexity 38 (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.
D1 · Cyclomatic Complexity · processPropExtraction (cyclomatic 38) · ×1
  • processPropExtraction (cyclomatic 38) backend-node/src/services/propExtractionService.js:9 — processPropExtraction has cyclomatic complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs 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.
D1 · Cyclomatic Complexity · streamGenerateText (cyclomatic 37) · ×1
  • streamGenerateText (cyclomatic 37) backend-node/src/services/aiClient.js:493 — streamGenerateText has cyclomatic complexity 37 (threshold 15). Of this number, 31 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.
D1 · Cyclomatic Complexity · videoClient.resolveVeo3ImageForApi (cyclomatic 36) · ×1
  • videoClient.resolveVeo3ImageForApi (cyclomatic 36) backend-node/src/services/videoClient.js:2322 — videoClient.resolveVeo3ImageForApi 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.
D1 · Cyclomatic Complexity · generateText (cyclomatic 36) · ×1
  • generateText (cyclomatic 36) backend-node/src/services/aiClient.js:376 — generateText has cyclomatic complexity 36 (threshold 15). Of this number, 30 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.
D1 · Cyclomatic Complexity · jimengMaterialHubService.hubJson (cyclomatic 35) · ×1
  • jimengMaterialHubService.hubJson (cyclomatic 35) backend-node/src/services/jimengMaterialHubService.js:206 — jimengMaterialHubService.hubJson 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 · videoClient.callKlingOmniVideoApi (cyclomatic 35) · ×1
  • videoClient.callKlingOmniVideoApi (cyclomatic 35) backend-node/src/services/videoClient.js:840 — videoClient.callKlingOmniVideoApi 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 · angleService.inferPhotographyParams (cyclomatic 34) · ×1
  • angleService.inferPhotographyParams (cyclomatic 34) backend-node/src/services/angleService.js:378 — angleService.inferPhotographyParams has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useGenerationTaskSync.syncGeneratingSetsFromStore (cyclomatic 34) · ×1
  • useGenerationTaskSync.syncGeneratingSetsFromStore (cyclomatic 34) frontweb/src/composables/useGenerationTaskSync.js:33 — useGenerationTaskSync.syncGeneratingSetsFromStore 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.
D1 · Cyclomatic Complexity · framePromptService.buildStoryboardContext (cyclomatic 33) · ×1
  • framePromptService.buildStoryboardContext (cyclomatic 33) backend-node/src/services/framePromptService.js:265 — framePromptService.buildStoryboardContext has cyclomatic complexity 33 (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 · videoClient.callGeminiVideoApi (cyclomatic 32) · ×1
  • videoClient.callGeminiVideoApi (cyclomatic 32) backend-node/src/services/videoClient.js:1811 — videoClient.callGeminiVideoApi 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.
D1 · Cyclomatic Complexity · storyboards.postUniversalSegmentNdjsonStream (cyclomatic 32) · ×1
  • storyboards.postUniversalSegmentNdjsonStream (cyclomatic 32) frontweb/src/api/storyboards.js:9 — storyboards.postUniversalSegmentNdjsonStream has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 14). 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.
D1 · Cyclomatic Complexity · toAgentSseEvent (cyclomatic 32) · ×1
  • toAgentSseEvent (cyclomatic 32) backend-node/src/mastra/sse.mjs:11 — toAgentSseEvent has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videos.routes.create (cyclomatic 31) · ×1
  • videos.routes.create (cyclomatic 31) backend-node/src/routes/videos.js:18 — videos.routes.create has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · narrationVideoPostProcess.runNarrationSubtitlePostProcess (cyclomatic 31) · ×1
  • narrationVideoPostProcess.runNarrationSubtitlePostProcess (cyclomatic 31) backend-node/src/services/narrationVideoPostProcess.js:205 — narrationVideoPostProcess.runNarrationSubtitlePostProcess has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · processBackgroundExtraction (cyclomatic 31) · ×1
  • processBackgroundExtraction (cyclomatic 31) backend-node/src/services/backgroundExtractionService.js:60 — processBackgroundExtraction has cyclomatic complexity 31 (threshold 15). Of this number, 25 points are the body's own statements and 6 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.
D1 · Cyclomatic Complexity · routes.linkTailFrame (cyclomatic 31) · ×1
  • routes.linkTailFrame (cyclomatic 31) REDACTED:11 — routes.linkTailFrame has cyclomatic complexity 31 (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 · ttsService.synthesize (cyclomatic 30) · ×1
  • ttsService.synthesize (cyclomatic 30) REDACTED:119 — ttsService.synthesize has cyclomatic complexity 30 (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.
D1 · Cyclomatic Complexity · tailFrameLinkService.routes.linkTailFrame (cyclomatic 30) · ×1
  • tailFrameLinkService.routes.linkTailFrame (cyclomatic 30) REDACTED:11 — tailFrameLinkService.routes.linkTailFrame has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useCharacters.submitEditCharacter (cyclomatic 30) · ×1
  • useCharacters.submitEditCharacter (cyclomatic 30) frontweb/src/composables/filmCreate/useCharacters.js:211 — useCharacters.submitEditCharacter has cyclomatic complexity 30 (threshold 15). Of this number, 23 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · useCharacters.addCharToEpisode (cyclomatic 30) · ×1
  • useCharacters.addCharToEpisode (cyclomatic 30) frontweb/src/composables/filmCreate/useCharacters.js:535 — useCharacters.addCharToEpisode has cyclomatic complexity 30 (threshold 15). Of this number, 22 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · characterLibraryService.generateCharacterImage (cyclomatic 29) · ×1
  • characterLibraryService.generateCharacterImage (cyclomatic 29) backend-node/src/services/characterLibraryService.js:46 — characterLibraryService.generateCharacterImage has cyclomatic complexity 29 (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 · videoClient.resolveJimengApiImageBuffer (cyclomatic 29) · ×1
  • videoClient.resolveJimengApiImageBuffer (cyclomatic 29) backend-node/src/services/videoClient.js:3272 — videoClient.resolveJimengApiImageBuffer has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useCharacters.useCharacters.submitEditCharacter (cyclomatic 29) · ×1
  • useCharacters.useCharacters.submitEditCharacter (cyclomatic 29) frontweb/src/composables/filmCreate/useCharacters.js:211 — useCharacters.useCharacters.submitEditCharacter has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · useCharacters.useCharacters.addCharToEpisode (cyclomatic 29) · ×1
  • useCharacters.useCharacters.addCharToEpisode (cyclomatic 29) frontweb/src/composables/filmCreate/useCharacters.js:535 — useCharacters.useCharacters.addCharToEpisode has cyclomatic complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · applyVendorLock (cyclomatic 29) · ×1
  • applyVendorLock (cyclomatic 29) backend-node/src/services/aiConfigService.js:497 — applyVendorLock has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · generateVideoPrompt (cyclomatic 29) · ×1
  • generateVideoPrompt (cyclomatic 29) backend-node/src/services/episodeStoryboardService.js:294 — generateVideoPrompt has cyclomatic complexity 29 (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 · getStoryboardById (cyclomatic 29) · ×1
  • getStoryboardById (cyclomatic 29) backend-node/src/services/storyboardService.js:143 — getStoryboardById has cyclomatic complexity 29 (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 · episodeStoryboardService.buildFallbackUniversalSeedanceLine (cyclomatic 28) · ×1
  • episodeStoryboardService.buildFallbackUniversalSeedanceLine (cyclomatic 28) backend-node/src/services/episodeStoryboardService.js:159 — episodeStoryboardService.buildFallbackUniversalSeedanceLine has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.setupRouter (cyclomatic 28) · ×1
  • index.setupRouter (cyclomatic 28) REDACTED:25 — index.setupRouter has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 60, 122, 194, …). 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.
D1 · Cyclomatic Complexity · framePromptService.loadStoryboardCharacterNames (cyclomatic 27) · ×1
  • framePromptService.loadStoryboardCharacterNames (cyclomatic 27) backend-node/src/services/framePromptService.js:162 — framePromptService.loadStoryboardCharacterNames has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · videoClient.callVeo3VideoApi (cyclomatic 27) · ×1
  • videoClient.callVeo3VideoApi (cyclomatic 27) backend-node/src/services/videoClient.js:2420 — videoClient.callVeo3VideoApi has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · framePromptService.processFramePromptGeneration (cyclomatic 26) · ×1
  • framePromptService.processFramePromptGeneration (cyclomatic 26) backend-node/src/services/framePromptService.js:480 — framePromptService.processFramePromptGeneration has cyclomatic complexity 26 (threshold 15). Of this number, 25 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.
D1 · Cyclomatic Complexity · modelArkAssetProxyService.callModelArkAsset (cyclomatic 26) · ×1
  • modelArkAssetProxyService.callModelArkAsset (cyclomatic 26) backend-node/src/services/modelArkAssetProxyService.js:182 — modelArkAssetProxyService.callModelArkAsset has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useProps.useProps.addPropToEpisode (cyclomatic 26) · ×1
  • useProps.useProps.addPropToEpisode (cyclomatic 26) frontweb/src/composables/filmCreate/useProps.js:498 — useProps.useProps.addPropToEpisode 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.
D1 · Cyclomatic Complexity · rowToStoryboard (cyclomatic 26) · ×1
  • rowToStoryboard (cyclomatic 26) backend-node/src/services/dramaService.js:348 — rowToStoryboard has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useProps.addPropToEpisode (cyclomatic 26) · ×1
  • useProps.addPropToEpisode (cyclomatic 26) frontweb/src/composables/filmCreate/useProps.js:498 — useProps.addPropToEpisode 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.
D1 · Cyclomatic Complexity · universalSegmentDurationNormalize.normalizeUniversalSegmentShotDurations (cyclomatic 25) · ×1
  • universalSegmentDurationNormalize.normalizeUniversalSegmentShotDurations (cyclomatic 25) backend-node/src/services/universalSegmentDurationNormalize.js:7 — universalSegmentDurationNormalize.normalizeUniversalSegmentShotDurations has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · generationTaskStore.useGenerationTaskStore.reconcileRunningTasks (cyclomatic 25) · ×1
  • generationTaskStore.useGenerationTaskStore.reconcileRunningTasks (cyclomatic 25) frontweb/src/stores/generationTaskStore.js:201 — generationTaskStore.useGenerationTaskStore.reconcileRunningTasks has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous).reconcileRunningTasks (cyclomatic 25) · ×1
  • (anonymous).reconcileRunningTasks (cyclomatic 25) frontweb/src/stores/generationTaskStore.js:201 — (anonymous).reconcileRunningTasks has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · seedance2AssetGuards.markStaleOnCharacterMainImageDrift (cyclomatic 24) · ×1
  • seedance2AssetGuards.markStaleOnCharacterMainImageDrift (cyclomatic 24) backend-node/src/utils/seedance2AssetGuards.js:24 — seedance2AssetGuards.markStaleOnCharacterMainImageDrift has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · aiConfigService.updateConfig (cyclomatic 24) · ×1
  • aiConfigService.updateConfig (cyclomatic 24) backend-node/src/services/aiConfigService.js:149 — aiConfigService.updateConfig 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.
D1 · Cyclomatic Complexity · aiClient.generateTextWithVision (cyclomatic 24) · ×1
  • aiClient.generateTextWithVision (cyclomatic 24) backend-node/src/services/aiClient.js:641 — aiClient.generateTextWithVision 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.
D1 · Cyclomatic Complexity · imageClient.resolveImageRef (cyclomatic 24) · ×1
  • imageClient.resolveImageRef (cyclomatic 24) backend-node/src/services/imageClient.js:866 — imageClient.resolveImageRef has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · audio.routes.extract (cyclomatic 24) · ×1
  • audio.routes.extract (cyclomatic 24) backend-node/src/routes/audio.js:15 — audio.routes.extract 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.
D1 · Cyclomatic Complexity · tools.executeGenerateImage (cyclomatic 24) · ×1
  • tools.executeGenerateImage (cyclomatic 24) backend-node/src/mastra/tools.mjs:269 — tools.executeGenerateImage has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · routes.extract (cyclomatic 24) · ×1
  • routes.extract (cyclomatic 24) backend-node/src/routes/audio.js:15 — routes.extract 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.
D1 · Cyclomatic Complexity · buildEpisodePipeline (cyclomatic 24) · ×1
  • buildEpisodePipeline (cyclomatic 24) frontweb/src/utils/dramaCanvasAdapter.js:165 — buildEpisodePipeline has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 201). 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.
D1 · Cyclomatic Complexity · episodeStoryboardService.buildSplitPlansFromStoryboard (cyclomatic 23) · ×1
  • episodeStoryboardService.buildSplitPlansFromStoryboard (cyclomatic 23) backend-node/src/services/episodeStoryboardService.js:1501 — episodeStoryboardService.buildSplitPlansFromStoryboard has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · modelArkAssetConfigService.buildModelArkContext (cyclomatic 22) · ×1
  • modelArkAssetConfigService.buildModelArkContext (cyclomatic 22) backend-node/src/services/modelArkAssetConfigService.js:34 — modelArkAssetConfigService.buildModelArkContext has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoClient.probeViduReferenceImageSize (cyclomatic 22) · ×1
  • videoClient.probeViduReferenceImageSize (cyclomatic 22) backend-node/src/services/videoClient.js:2020 — videoClient.probeViduReferenceImageSize 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.
D1 · Cyclomatic Complexity · useScenes.useScenes.addSceneToEpisode (cyclomatic 22) · ×1
  • useScenes.useScenes.addSceneToEpisode (cyclomatic 22) frontweb/src/composables/filmCreate/useScenes.js:521 — useScenes.useScenes.addSceneToEpisode has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · dramaCanvasAdapter.getAssetRelationHighlight (cyclomatic 22) · ×1
  • dramaCanvasAdapter.getAssetRelationHighlight (cyclomatic 22) frontweb/src/utils/dramaCanvasAdapter.js:449 — dramaCanvasAdapter.getAssetRelationHighlight 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.
D1 · Cyclomatic Complexity · saveOutline (cyclomatic 22) · ×1
  • saveOutline (cyclomatic 22) backend-node/src/services/dramaService.js:467 — saveOutline 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.
D1 · Cyclomatic Complexity · persistSplitStoryboardRow (cyclomatic 22) · ×1
  • persistSplitStoryboardRow (cyclomatic 22) backend-node/src/services/episodeStoryboardService.js:1559 — persistSplitStoryboardRow has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useScenes.addSceneToEpisode (cyclomatic 22) · ×1
  • useScenes.addSceneToEpisode (cyclomatic 22) frontweb/src/composables/filmCreate/useScenes.js:521 — useScenes.addSceneToEpisode has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · episodeStoryboardService.tryIncrementalSave (cyclomatic 21) · ×1
  • episodeStoryboardService.tryIncrementalSave (cyclomatic 21) backend-node/src/services/episodeStoryboardService.js:588 — episodeStoryboardService.tryIncrementalSave 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.
D1 · Cyclomatic Complexity · dramaService.getVideoUrlForStoryboard (cyclomatic 21) · ×1
  • dramaService.getVideoUrlForStoryboard (cyclomatic 21) backend-node/src/services/dramaService.js:748 — dramaService.getVideoUrlForStoryboard has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoClient.resolveImageInputForAgnesAsync (cyclomatic 21) · ×1
  • videoClient.resolveImageInputForAgnesAsync (cyclomatic 21) backend-node/src/services/videoClient.js:514 — videoClient.resolveImageInputForAgnesAsync 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 · videoClient.extractPollFailureMessage (cyclomatic 21) · ×1
  • videoClient.extractPollFailureMessage (cyclomatic 21) backend-node/src/services/videoClient.js:1255 — videoClient.extractPollFailureMessage 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 · useCharacters.useCharacters.editCharacter (cyclomatic 21) · ×1
  • useCharacters.useCharacters.editCharacter (cyclomatic 21) frontweb/src/composables/filmCreate/useCharacters.js:155 — useCharacters.useCharacters.editCharacter has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · unwrapModelArkAssetView (cyclomatic 21) · ×1
  • unwrapModelArkAssetView (cyclomatic 21) backend-node/src/services/modelArkAssetConfigService.js:120 — unwrapModelArkAssetView 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 · useCharacters.editCharacter (cyclomatic 21) · ×1
  • useCharacters.editCharacter (cyclomatic 21) frontweb/src/composables/filmCreate/useCharacters.js:155 — useCharacters.editCharacter has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · universalOmniMultiBeatFormat.buildFallbackUniversalMultiBeatText (cyclomatic 20) · ×1
  • universalOmniMultiBeatFormat.buildFallbackUniversalMultiBeatText (cyclomatic 20) backend-node/src/services/universalOmniMultiBeatFormat.js:37 — universalOmniMultiBeatFormat.buildFallbackUniversalMultiBeatText has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · framePromptService.buildCharacterAnchorText (cyclomatic 20) · ×1
  • framePromptService.buildCharacterAnchorText (cyclomatic 20) backend-node/src/services/framePromptService.js:127 — framePromptService.buildCharacterAnchorText has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sceneService.generateSceneFourViewImage (cyclomatic 20) · ×1
  • sceneService.generateSceneFourViewImage (cyclomatic 20) backend-node/src/services/sceneService.js:313 — sceneService.generateSceneFourViewImage has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This shape REPEATS in the file: one other method here (sceneService.generateSceneSingleImage) 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.
D1 · Cyclomatic Complexity · sceneService.generateSceneSingleImage (cyclomatic 20) · ×1
  • sceneService.generateSceneSingleImage (cyclomatic 20) backend-node/src/services/sceneService.js:389 — sceneService.generateSceneSingleImage has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This shape REPEATS in the file: one other method here (sceneService.generateSceneFourViewImage) 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.
D1 · Cyclomatic Complexity · videoClient.resolveVideoProtocol (cyclomatic 20) · ×1
  • videoClient.resolveVideoProtocol (cyclomatic 20) backend-node/src/services/videoClient.js:133 — videoClient.resolveVideoProtocol has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoClient.parseDashScopeVideoUrl (cyclomatic 20) · ×1
  • videoClient.parseDashScopeVideoUrl (cyclomatic 20) backend-node/src/services/videoClient.js:1436 — videoClient.parseDashScopeVideoUrl 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.
D1 · Cyclomatic Complexity · videoClient.formatVideoPostBodyForLog (cyclomatic 20) · ×1
  • videoClient.formatVideoPostBodyForLog (cyclomatic 20) backend-node/src/services/videoClient.js:2598 — videoClient.formatVideoPostBodyForLog has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · videoClient.resolveVolcClassicImage (cyclomatic 20) · ×1
  • videoClient.resolveVolcClassicImage (cyclomatic 20) backend-node/src/services/videoClient.js:3820 — videoClient.resolveVolcClassicImage 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.
D1 · Cyclomatic Complexity · tools.executeGetCurrentProject (cyclomatic 20) · ×1
  • tools.executeGetCurrentProject (cyclomatic 20) backend-node/src/mastra/tools.mjs:27 — tools.executeGetCurrentProject has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, 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 · app.createApp (cyclomatic 20) · ×1
  • app.createApp (cyclomatic 20) REDACTED:11 — app.createApp 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 4 function literals inside it that branch (lines 104, 80, 75, …). 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.
D1 · Cyclomatic Complexity · useScenes.useScenes.submitEditScene (cyclomatic 20) · ×1
  • useScenes.useScenes.submitEditScene (cyclomatic 20) frontweb/src/composables/filmCreate/useScenes.js:248 — useScenes.useScenes.submitEditScene has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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 · registerCharacterViaJimengHub (cyclomatic 20) · ×1
  • registerCharacterViaJimengHub (cyclomatic 20) backend-node/src/services/characterLibraryService.js:848 — registerCharacterViaJimengHub has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · runVideoStep (cyclomatic 20) · ×1
  • runVideoStep (cyclomatic 20) frontweb/src/composables/useCanvasWorkflowRunner.js:49 — runVideoStep has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · useScenes.submitEditScene (cyclomatic 20) · ×1
  • useScenes.submitEditScene (cyclomatic 20) frontweb/src/composables/filmCreate/useScenes.js:248 — useScenes.submitEditScene has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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 · imageClient.inferProtocol (cyclomatic 19) · ×1
  • imageClient.inferProtocol (cyclomatic 19) backend-node/src/services/imageClient.js:92 — imageClient.inferProtocol has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · framePromptService.expandAngleDescriptionLegacy (cyclomatic 19) · ×1
  • framePromptService.expandAngleDescriptionLegacy (cyclomatic 19) backend-node/src/services/framePromptService.js:33 — framePromptService.expandAngleDescriptionLegacy 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.
D1 · Cyclomatic Complexity · episodeStoryboardService.loadStoryboardCharacterIds (cyclomatic 19) · ×1
  • episodeStoryboardService.loadStoryboardCharacterIds (cyclomatic 19) backend-node/src/services/episodeStoryboardService.js:1352 — episodeStoryboardService.loadStoryboardCharacterIds 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 branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · videoMergeService.resolveVideoToLocalPath (cyclomatic 19) · ×1
  • videoMergeService.resolveVideoToLocalPath (cyclomatic 19) backend-node/src/services/videoMergeService.js:84 — videoMergeService.resolveVideoToLocalPath 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.
D1 · Cyclomatic Complexity · characterLibraryService.updateCharacter (cyclomatic 19) · ×1
  • characterLibraryService.updateCharacter (cyclomatic 19) backend-node/src/services/characterLibraryService.js:307 — characterLibraryService.updateCharacter has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · videoClient.resolveSoraImageToDataUrl (cyclomatic 19) · ×1
  • videoClient.resolveSoraImageToDataUrl (cyclomatic 19) backend-node/src/services/videoClient.js:2908 — videoClient.resolveSoraImageToDataUrl 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.
D1 · Cyclomatic Complexity · generationTaskStore.useGenerationTaskStore.pollTask (cyclomatic 19) · ×1
  • generationTaskStore.useGenerationTaskStore.pollTask (cyclomatic 19) frontweb/src/stores/generationTaskStore.js:254 — generationTaskStore.useGenerationTaskStore.pollTask has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 271). 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.
D1 · Cyclomatic Complexity · refreshCharacterJimengMaterialAsset (cyclomatic 19) · ×1
  • refreshCharacterJimengMaterialAsset (cyclomatic 19) backend-node/src/services/characterLibraryService.js:1000 — refreshCharacterJimengMaterialAsset 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.
D1 · Cyclomatic Complexity · create (cyclomatic 19) · ×1
  • create (cyclomatic 19) backend-node/src/services/imageService.js:532 — create has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · buildStoryboardSheetRows (cyclomatic 19) · ×1
  • buildStoryboardSheetRows (cyclomatic 19) frontweb/src/utils/exportStoryboardSheet.js:101 — buildStoryboardSheetRows 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.
D1 · Cyclomatic Complexity · episodeStoryboardService.buildCameraMotionChain (cyclomatic 18) · ×1
  • episodeStoryboardService.buildCameraMotionChain (cyclomatic 18) backend-node/src/services/episodeStoryboardService.js:130 — episodeStoryboardService.buildCameraMotionChain 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.
D1 · Cyclomatic Complexity · dramaService.getDrama (cyclomatic 18) · ×1
  • dramaService.getDrama (cyclomatic 18) backend-node/src/services/dramaService.js:67 — dramaService.getDrama has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · characterLibraryService.generateCharacterFourViewImage (cyclomatic 18) · ×1
  • characterLibraryService.generateCharacterFourViewImage (cyclomatic 18) backend-node/src/services/characterLibraryService.js:532 — characterLibraryService.generateCharacterFourViewImage 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.
D1 · Cyclomatic Complexity · sceneService.generateScenePromptOnly (cyclomatic 18) · ×1
  • sceneService.generateScenePromptOnly (cyclomatic 18) backend-node/src/services/sceneService.js:199 — sceneService.generateScenePromptOnly 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. This shape REPEATS in the file: one other method here (sceneService.generateSceneSinglePromptOnly) 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.
D1 · Cyclomatic Complexity · sceneService.generateSceneSinglePromptOnly (cyclomatic 18) · ×1
  • sceneService.generateSceneSinglePromptOnly (cyclomatic 18) backend-node/src/services/sceneService.js:256 — sceneService.generateSceneSinglePromptOnly 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. This shape REPEATS in the file: one other method here (sceneService.generateScenePromptOnly) 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.
D1 · Cyclomatic Complexity · storyboards.buildClassicRequiredCoverageDigest (cyclomatic 18) · ×1
  • storyboards.buildClassicRequiredCoverageDigest (cyclomatic 18) REDACTED:150 — storyboards.buildClassicRequiredCoverageDigest has cyclomatic complexity 18 (threshold 15). Of this number, 15 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.
D1 · Cyclomatic Complexity · videoClient.inferVideoProtocol (cyclomatic 18) · ×1
  • videoClient.inferVideoProtocol (cyclomatic 18) backend-node/src/services/videoClient.js:26 — videoClient.inferVideoProtocol 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.
D1 · Cyclomatic Complexity · videoClient.logKlingOmniAuthDebug (cyclomatic 18) · ×1
  • videoClient.logKlingOmniAuthDebug (cyclomatic 18) backend-node/src/services/videoClient.js:239 — videoClient.logKlingOmniAuthDebug 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.
D1 · Cyclomatic Complexity · videoClient.buildSd2ActiveAssetUrlLookup (cyclomatic 18) · ×1
  • videoClient.buildSd2ActiveAssetUrlLookup (cyclomatic 18) backend-node/src/services/videoClient.js:3720 — videoClient.buildSd2ActiveAssetUrlLookup 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.
D1 · Cyclomatic Complexity · context.assertOwned (cyclomatic 18) · ×1
  • context.assertOwned (cyclomatic 18) backend-node/src/mastra/context.mjs:25 — context.assertOwned 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.
D1 · Cyclomatic Complexity · tools.executeSaveEpisodeScript (cyclomatic 18) · ×1
  • tools.executeSaveEpisodeScript (cyclomatic 18) backend-node/src/mastra/tools.mjs:117 — tools.executeSaveEpisodeScript 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.
D1 · Cyclomatic Complexity · getStoryboardsForEpisode (cyclomatic 18) · ×1
  • getStoryboardsForEpisode (cyclomatic 18) backend-node/src/services/episodeStoryboardService.js:191 — getStoryboardsForEpisode has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 197, 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.
D1 · Cyclomatic Complexity · insertOneStoryboard (cyclomatic 18) · ×1
  • insertOneStoryboard (cyclomatic 18) backend-node/src/services/episodeStoryboardService.js:553 — insertOneStoryboard 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.
D1 · Cyclomatic Complexity · splitNineGridToImages (cyclomatic 18) · ×1
  • splitNineGridToImages (cyclomatic 18) backend-node/src/services/imageService.js:314 — splitNineGridToImages 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.
D1 · Cyclomatic Complexity · syncStoryboardCharacters (cyclomatic 18) · ×1
  • syncStoryboardCharacters (cyclomatic 18) backend-node/src/services/imageService.js:1628 — syncStoryboardCharacters has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent 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 · updateStoryboard (cyclomatic 18) · ×1
  • updateStoryboard (cyclomatic 18) backend-node/src/services/storyboardService.js:87 — updateStoryboard 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.
D1 · Cyclomatic Complexity · parseScriptIntoEpisodes (cyclomatic 18) · ×1
  • parseScriptIntoEpisodes (cyclomatic 18) frontweb/src/utils/scriptEpisodes.js:6 — parseScriptIntoEpisodes 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, separate the cases: extract each independent 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 · framePromptService.regenerateLayoutDescription (cyclomatic 17) · ×1
  • framePromptService.regenerateLayoutDescription (cyclomatic 17) backend-node/src/services/framePromptService.js:629 — framePromptService.regenerateLayoutDescription 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.
D1 · Cyclomatic Complexity · storyboardFrameBinding.bindStoryboardFrameImage (cyclomatic 17) · ×1
  • storyboardFrameBinding.bindStoryboardFrameImage (cyclomatic 17) backend-node/src/services/storyboardFrameBinding.js:6 — storyboardFrameBinding.bindStoryboardFrameImage 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.
D1 · Cyclomatic Complexity · characterLibraryService.isNonPublicMaterialHubUrl (cyclomatic 17) · ×1
  • characterLibraryService.isNonPublicMaterialHubUrl (cyclomatic 17) backend-node/src/services/characterLibraryService.js:689 — characterLibraryService.isNonPublicMaterialHubUrl 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.
D1 · Cyclomatic Complexity · storyboards.routes.polishUniversalSegmentStream (cyclomatic 17) · ×1
  • storyboards.routes.polishUniversalSegmentStream (cyclomatic 17) REDACTED:655 — storyboards.routes.polishUniversalSegmentStream 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.
D1 · Cyclomatic Complexity · storyboards.routes.batchInferParams (cyclomatic 17) · ×1
  • storyboards.routes.batchInferParams (cyclomatic 17) REDACTED:1067 — storyboards.routes.batchInferParams 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.
D1 · Cyclomatic Complexity · useScenes.useScenes.editScene (cyclomatic 17) · ×1
  • useScenes.useScenes.editScene (cyclomatic 17) frontweb/src/composables/filmCreate/useScenes.js:132 — useScenes.useScenes.editScene has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoOmniSupport.canUseUniversalOmniVideoApi (cyclomatic 17) · ×1
  • videoOmniSupport.canUseUniversalOmniVideoApi (cyclomatic 17) frontweb/src/utils/videoOmniSupport.js:45 — videoOmniSupport.canUseUniversalOmniVideoApi has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · routes.polishUniversalSegmentStream (cyclomatic 17) · ×1
  • routes.polishUniversalSegmentStream (cyclomatic 17) REDACTED:655 — routes.polishUniversalSegmentStream 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.
D1 · Cyclomatic Complexity · routes.batchInferParams (cyclomatic 17) · ×1
  • routes.batchInferParams (cyclomatic 17) REDACTED:1067 — routes.batchInferParams 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.
D1 · Cyclomatic Complexity · updateStoryboardRowFromDerived (cyclomatic 17) · ×1
  • updateStoryboardRowFromDerived (cyclomatic 17) backend-node/src/services/episodeStoryboardService.js:498 — updateStoryboardRowFromDerived has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · useCanvasEpisodeGenerate.aiGenerateStoryboards (cyclomatic 17) · ×1
  • useCanvasEpisodeGenerate.aiGenerateStoryboards (cyclomatic 17) frontweb/src/composables/useCanvasEpisodeGenerate.js:98 — useCanvasEpisodeGenerate.aiGenerateStoryboards 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.
D1 · Cyclomatic Complexity · (anonymous).pollTask · ×1
  • (anonymous).pollTask::(anonymous)::tick (cyclomatic 17) frontweb/src/stores/generationTaskStore.js:271 — (anonymous).pollTask::(anonymous)::tick 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.
D1 · Cyclomatic Complexity · useScenes.editScene (cyclomatic 17) · ×1
  • useScenes.editScene (cyclomatic 17) frontweb/src/composables/filmCreate/useScenes.js:132 — useScenes.editScene has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · seedance2AssetGuards.markStaleOnCharacterVoiceDrift (cyclomatic 16) · ×1
  • seedance2AssetGuards.markStaleOnCharacterVoiceDrift (cyclomatic 16) backend-node/src/utils/seedance2AssetGuards.js:88 — seedance2AssetGuards.markStaleOnCharacterVoiceDrift has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · safeJson.extractJsonCandidate (cyclomatic 16) · ×1
  • safeJson.extractJsonCandidate (cyclomatic 16) backend-node/src/utils/safeJson.js:4 — safeJson.extractJsonCandidate 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.
D1 · Cyclomatic Complexity · imageService.buildQuadGridPrompt (cyclomatic 16) · ×1
  • imageService.buildQuadGridPrompt (cyclomatic 16) backend-node/src/services/imageService.js:182 — imageService.buildQuadGridPrompt has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · imageService.normalizeSavedImageToTargetPixels (cyclomatic 16) · ×1
  • imageService.normalizeSavedImageToTargetPixels (cyclomatic 16) backend-node/src/services/imageService.js:470 — imageService.normalizeSavedImageToTargetPixels 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 · dramaService.listDramas (cyclomatic 16) · ×1
  • dramaService.listDramas (cyclomatic 16) backend-node/src/services/dramaService.js:167 — dramaService.listDramas has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · dramaService.saveCanvasLayout (cyclomatic 16) · ×1
  • dramaService.saveCanvasLayout (cyclomatic 16) backend-node/src/services/dramaService.js:709 — dramaService.saveCanvasLayout 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 · propService.generatePropPromptOnly (cyclomatic 16) · ×1
  • propService.generatePropPromptOnly (cyclomatic 16) backend-node/src/services/propService.js:125 — propService.generatePropPromptOnly has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · characterLibraryService.buildFourViewImagePrompt (cyclomatic 16) · ×1
  • characterLibraryService.buildFourViewImagePrompt (cyclomatic 16) backend-node/src/services/characterLibraryService.js:452 — characterLibraryService.buildFourViewImagePrompt 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 · videoClient.resolveKlingOmniBearerToken (cyclomatic 16) · ×1
  • videoClient.resolveKlingOmniBearerToken (cyclomatic 16) backend-node/src/services/videoClient.js:209 — videoClient.resolveKlingOmniBearerToken has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · videoClient.buildQueryUrl (cyclomatic 16) · ×1
  • videoClient.buildQueryUrl (cyclomatic 16) backend-node/src/services/videoClient.js:1155 — videoClient.buildQueryUrl 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 · videoClient.pickVideoUrlFromResultShape (cyclomatic 16) · ×1
  • videoClient.pickVideoUrlFromResultShape (cyclomatic 16) backend-node/src/services/videoClient.js:1338 — videoClient.pickVideoUrlFromResultShape 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.
D1 · Cyclomatic Complexity · videoClient.loadViduReferenceImageBuffer (cyclomatic 16) · ×1
  • videoClient.loadViduReferenceImageBuffer (cyclomatic 16) backend-node/src/services/videoClient.js:1954 — videoClient.loadViduReferenceImageBuffer 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.
D1 · Cyclomatic Complexity · videoService.finalizeSuccessfulVideo (cyclomatic 16) · ×1
  • videoService.finalizeSuccessfulVideo (cyclomatic 16) backend-node/src/services/videoService.js:231 — videoService.finalizeSuccessfulVideo 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 · useCanvasScript.useCanvasScript.extractAll (cyclomatic 16) · ×1
  • useCanvasScript.useCanvasScript.extractAll (cyclomatic 16) frontweb/src/composables/useCanvasScript.js:158 — useCanvasScript.useCanvasScript.extractAll has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · routes.putImage (cyclomatic 16) · ×1
  • routes.putImage (cyclomatic 16) REDACTED:157 — routes.putImage 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 · saveEpisodes (cyclomatic 16) · ×1
  • saveEpisodes (cyclomatic 16) backend-node/src/services/dramaService.js:650 — saveEpisodes 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.
D1 · Cyclomatic Complexity · unwrapMaterialHubAssetView (cyclomatic 16) · ×1
  • unwrapMaterialHubAssetView (cyclomatic 16) backend-node/src/services/jimengMaterialHubService.js:176 — unwrapMaterialHubAssetView 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.
D1 · Cyclomatic Complexity · useCanvasCrud.createEpisode (cyclomatic 16) · ×1
  • useCanvasCrud.createEpisode (cyclomatic 16) frontweb/src/composables/useCanvasCrud.js:114 — useCanvasCrud.createEpisode has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · useCanvasScript.extractAll (cyclomatic 16) · ×1
  • useCanvasScript.extractAll (cyclomatic 16) frontweb/src/composables/useCanvasScript.js:158 — useCanvasScript.extractAll has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · (anonymous).recoverPendingForEpisode · ×1
  • (anonymous).recoverPendingForEpisode::attachImage (cyclomatic 16) frontweb/src/stores/generationTaskStore.js:435 — (anonymous).recoverPendingForEpisode::attachImage 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 · executeUpdateCharacter (cyclomatic 16) · ×1
  • executeUpdateCharacter (cyclomatic 16) backend-node/src/mastra/tools.mjs:160 — executeUpdateCharacter 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.
D12 · Dependency Hygiene · One package at two majors across the workspace · ×1
  • One package at two majors across the workspace: better-sqlite3 — `better-sqlite3` is maintained at 2 different major versions inside this one repository — major 11 in backend-node/package.json; major 13 in desktop/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
D2 · Cognitive Complexity · processImageGeneration (cognitive 760) · ×1
  • processImageGeneration (cognitive 760) backend-node/src/services/imageService.js:586 — processImageGeneration has cognitive complexity 760 (threshold 15). Drivers by points: if/else 136 (399 pts), boolean chains 121, error handling 36 (112 pts), ternaries 31 (102 pts), loops 7 (26 pts) (nesting depth added 429). Of this number, 730 points are the body's own statements and 30 belong to 13 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.
D2 · Cognitive Complexity · pollVideoTask (cognitive 288) · ×1
  • pollVideoTask (cognitive 288) backend-node/src/services/videoClient.js:4506 — pollVideoTask has cognitive complexity 288 (threshold 15). Drivers by points: if/else 68 (174 pts), boolean chains 67, ternaries 13 (31 pts), error handling 5 (15 pts), loops 1 (nesting depth added 134). Of this number, 283 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.
D2 · Cognitive Complexity · safeJson.safeParseAIJSON (cognitive 263) · ×1
  • safeJson.safeParseAIJSON (cognitive 263) backend-node/src/utils/safeJson.js:180 — safeJson.safeParseAIJSON has cognitive complexity 263 (threshold 15). Drivers by points: if/else 48 (152 pts), ternaries 13 (52 pts), error handling 11 (39 pts), boolean chains 20 (nesting depth added 171). Of this number, 259 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · _doImport (cognitive 207) · ×1
  • _doImport (cognitive 207) backend-node/src/services/dramaImportService.js:154 — _doImport has cognitive complexity 207 (threshold 15). Drivers by points: boolean chains 93, if/else 19 (56 pts), loops 11 (24 pts), ternaries 7 (19 pts), error handling 3 (12 pts), other 3 (nesting depth added 71). 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.
D2 · Cognitive Complexity · universalSegmentPromptBundle.buildUniversalSegmentUserPromptBundle (cognitive 171) · ×1
  • universalSegmentPromptBundle.buildUniversalSegmentUserPromptBundle (cognitive 171) backend-node/src/services/universalSegmentPromptBundle.js:9 — universalSegmentPromptBundle.buildUniversalSegmentUserPromptBundle has cognitive complexity 171 (threshold 15). Drivers by points: boolean chains 61, if/else 32 (50 pts), ternaries 25 (40 pts), error handling 9 (11 pts), loops 6 (9 pts) (nesting depth added 38). Of this number, 155 points are the body's own statements and 16 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.
D2 · Cognitive Complexity · callSoraVideoApi (cognitive 147) · ×1
  • callSoraVideoApi (cognitive 147) backend-node/src/services/videoClient.js:2952 — callSoraVideoApi has cognitive complexity 147 (threshold 15). Drivers by points: if/else 34 (62 pts), boolean chains 30, ternaries 16 (30 pts), error handling 10 (23 pts), loops 1 (2 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.
D2 · Cognitive Complexity · exportDrama (cognitive 132) · ×1
  • exportDrama (cognitive 132) backend-node/src/services/dramaExportService.js:80 — exportDrama has cognitive complexity 132 (threshold 15). Drivers by points: if/else 22 (54 pts), boolean chains 38, loops 17 (20 pts), ternaries 13, other 4, error handling 2 (3 pts) (nesting depth added 36). Of this number, 82 points are the body's own statements and 50 belong to 23 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.
D2 · Cognitive Complexity · callVideoApi (cognitive 132) · ×1
  • callVideoApi (cognitive 132) backend-node/src/services/videoClient.js:4071 — callVideoApi has cognitive complexity 132 (threshold 15). Drivers by points: if/else 44 (67 pts), boolean chains 31, ternaries 11 (22 pts), error handling 3 (7 pts), loops 1 (5 pts) (nesting depth added 42). Of this number, 131 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.
D2 · Cognitive Complexity · mergedEpisodePostProcess.runMergedEpisodePostProcess (cognitive 130) · ×1
  • mergedEpisodePostProcess.runMergedEpisodePostProcess (cognitive 130) backend-node/src/services/mergedEpisodePostProcess.js:204 — mergedEpisodePostProcess.runMergedEpisodePostProcess has cognitive complexity 130 (threshold 15). Drivers by points: if/else 38 (80 pts), error handling 8 (23 pts), boolean chains 16, ternaries 3 (8 pts), loops 2 (3 pts) (nesting depth added 63). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · callViduVideoApi (cognitive 125) · ×1
  • callViduVideoApi (cognitive 125) backend-node/src/services/videoClient.js:2100 — callViduVideoApi has cognitive complexity 125 (threshold 15). Drivers by points: if/else 25 (53 pts), ternaries 15 (43 pts), boolean chains 23, error handling 3 (6 pts) (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.
D2 · Cognitive Complexity · testConnection (cognitive 120) · ×1
  • testConnection (cognitive 120) backend-node/src/services/aiConfigService.js:261 — testConnection has cognitive complexity 120 (threshold 15). Drivers by points: boolean chains 56, if/else 22 (34 pts), error handling 9 (23 pts), ternaries 4 (7 pts) (nesting depth added 29). 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.
D2 · Cognitive Complexity · callDashScopeImageApi (cognitive 109) · ×1
  • callDashScopeImageApi (cognitive 109) backend-node/src/services/imageClient.js:910 — callDashScopeImageApi has cognitive complexity 109 (threshold 15). Drivers by points: if/else 26 (48 pts), boolean chains 25, ternaries 10 (18 pts), error handling 8 (16 pts), loops 2 (nesting depth added 38). Of this number, 105 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · imageClient.createAndGenerateImage (cognitive 107) · ×1
  • imageClient.createAndGenerateImage (cognitive 107) backend-node/src/services/imageClient.js:1686 — imageClient.createAndGenerateImage has cognitive complexity 107 (threshold 15). Drivers by points: if/else 22 (36 pts), boolean chains 30, error handling 14 (28 pts), ternaries 9 (13 pts) (nesting depth added 32). Of this number, 26 points are the body's own statements and 81 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.
D2 · Cognitive Complexity · callNanoBananaImageApi (cognitive 107) · ×1
  • callNanoBananaImageApi (cognitive 107) backend-node/src/services/imageClient.js:568 — callNanoBananaImageApi has cognitive complexity 107 (threshold 15). Drivers by points: ternaries 22 (42 pts), boolean chains 30, if/else 17 (26 pts), error handling 5 (8 pts), loops 1 (nesting depth added 32). Of this number, 103 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · saveCharacters (cognitive 104) · ×1
  • saveCharacters (cognitive 104) backend-node/src/services/dramaService.js:558 — saveCharacters has cognitive complexity 104 (threshold 15). Drivers by points: if/else 17 (49 pts), ternaries 6 (29 pts), other 21, loops 2 (3 pts), boolean chains 2 (nesting depth added 56). 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.
D2 · Cognitive Complexity · saveStoryboards (cognitive 100) · ×1
  • saveStoryboards (cognitive 100) backend-node/src/services/episodeStoryboardService.js:638 — saveStoryboards has cognitive complexity 100 (threshold 15). Drivers by points: boolean chains 27, if/else 12 (26 pts), other 16, ternaries 5 (14 pts), error handling 4 (13 pts), loops 2 (4 pts) (nesting depth added 34). Of this number, 95 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · callVolcengineOmniVideoApi (cognitive 97) · ×1
  • callVolcengineOmniVideoApi (cognitive 97) backend-node/src/services/videoClient.js:634 — callVolcengineOmniVideoApi has cognitive complexity 97 (threshold 15). Drivers by points: if/else 20 (37 pts), boolean chains 24, ternaries 8 (20 pts), error handling 5 (14 pts), loops 1 (2 pts) (nesting depth added 39). Of this number, 90 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · callImageApi (cognitive 89) · ×1
  • callImageApi (cognitive 89) backend-node/src/services/imageClient.js:1456 — callImageApi has cognitive complexity 89 (threshold 15). Drivers by points: boolean chains 31, ternaries 22 (31 pts), if/else 17 (22 pts), error handling 3 (4 pts), other 1 (nesting depth added 15). Of this number, 87 points are the body's own statements and 2 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · imageClient.callGeminiImageApi (cognitive 82) · ×1
  • imageClient.callGeminiImageApi (cognitive 82) backend-node/src/services/imageClient.js:1215 — imageClient.callGeminiImageApi has cognitive complexity 82 (threshold 15). Drivers by points: if/else 24 (50 pts), boolean chains 13, error handling 5 (8 pts), loops 4 (6 pts), ternaries 3 (5 pts) (nesting depth added 33). Of this number, 79 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.
D2 · Cognitive Complexity · videoClient.callDashScopeVideoApi (cognitive 81) · ×1
  • videoClient.callDashScopeVideoApi (cognitive 81) backend-node/src/services/videoClient.js:1641 — videoClient.callDashScopeVideoApi has cognitive complexity 81 (threshold 15). Drivers by points: if/else 27 (36 pts), boolean chains 30, ternaries 7 (11 pts), error handling 3 (4 pts) (nesting depth added 14). Of this number, 59 points are the body's own statements and 22 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.
D2 · Cognitive Complexity · episodeStoryboardService.generateStoryboard (cognitive 80) · ×1
  • episodeStoryboardService.generateStoryboard (cognitive 80) backend-node/src/services/episodeStoryboardService.js:1126 — episodeStoryboardService.generateStoryboard has cognitive complexity 80 (threshold 15). Drivers by points: if/else 31 (44 pts), boolean chains 26, ternaries 6 (9 pts), error handling 1 (nesting depth added 16). Of this number, 76 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.
D2 · Cognitive Complexity · processStoryboardGeneration (cognitive 74) · ×1
  • processStoryboardGeneration (cognitive 74) backend-node/src/services/episodeStoryboardService.js:862 — processStoryboardGeneration has cognitive complexity 74 (threshold 15). Drivers by points: if/else 16 (29 pts), boolean chains 20, ternaries 10 (13 pts), error handling 5 (9 pts), loops 2, other 1 (nesting depth added 20). Of this number, 64 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · pickProxyVideoUrl (cognitive 73) · ×1
  • pickProxyVideoUrl (cognitive 73) backend-node/src/services/videoClient.js:1359 — pickProxyVideoUrl has cognitive complexity 73 (threshold 15). Drivers by points: if/else 28 (53 pts), boolean chains 19, loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routes.polishPrompt (cognitive 69) · ×1
  • routes.polishPrompt (cognitive 69) REDACTED:410 — routes.polishPrompt has cognitive complexity 69 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 17, ternaries 9 (12 pts), error handling 7 (10 pts), loops 2 (4 pts), other 1 (nesting depth added 17). Of this number, 67 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.
D2 · Cognitive Complexity · storyboards.routes.polishPrompt (cognitive 67) · ×1
  • storyboards.routes.polishPrompt (cognitive 67) REDACTED:410 — storyboards.routes.polishPrompt has cognitive complexity 67 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 17, ternaries 9 (12 pts), error handling 6 (9 pts), loops 2 (4 pts) (nesting depth added 17). Of this number, 65 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.
D2 · Cognitive Complexity · generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode (cognitive 67) · ×1
  • generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode (cognitive 67) frontweb/src/stores/generationTaskStore.js:397 — generationTaskStore.useGenerationTaskStore.recoverPendingForEpisode has cognitive complexity 67 (threshold 15). Drivers by points: if/else 23 (36 pts), boolean chains 19, loops 6, ternaries 5, error handling 1 (nesting depth added 13). Of this number, 43 points are the body's own statements and 24 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.
D2 · Cognitive Complexity · routes.polishClassicVideoPromptStream (cognitive 66) · ×1
  • routes.polishClassicVideoPromptStream (cognitive 66) REDACTED:777 — routes.polishClassicVideoPromptStream has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 28, ternaries 12 (17 pts), if/else 10 (11 pts), error handling 8, other 2 (nesting depth added 6). Of this number, 62 points are the body's own statements and 4 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · videoClient.resolveVeo3ImageForApi (cognitive 65) · ×1
  • videoClient.resolveVeo3ImageForApi (cognitive 65) backend-node/src/services/videoClient.js:2322 — videoClient.resolveVeo3ImageForApi has cognitive complexity 65 (threshold 15). Drivers by points: if/else 16 (32 pts), error handling 6 (13 pts), boolean chains 10, ternaries 3 (10 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · videoService.processVideoGeneration (cognitive 63) · ×1
  • videoService.processVideoGeneration (cognitive 63) backend-node/src/services/videoService.js:472 — videoService.processVideoGeneration has cognitive complexity 63 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 17, ternaries 7 (9 pts), error handling 3 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · callJimengAiApiVideo (cognitive 62) · ×1
  • callJimengAiApiVideo (cognitive 62) backend-node/src/services/videoClient.js:3330 — callJimengAiApiVideo has cognitive complexity 62 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 18, ternaries 8 (12 pts), loops 4 (5 pts), error handling 3 (4 pts) (nesting depth added 10). 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 · videoClient.callXaiVideoApi (cognitive 61) · ×1
  • videoClient.callXaiVideoApi (cognitive 61) backend-node/src/services/videoClient.js:3515 — videoClient.callXaiVideoApi has cognitive complexity 61 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 19, ternaries 7 (8 pts), error handling 2 (3 pts), loops 1 (2 pts) (nesting depth added 15). Of this number, 60 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.
D2 · Cognitive Complexity · callKlingVideoApi (cognitive 61) · ×1
  • callKlingVideoApi (cognitive 61) backend-node/src/services/videoClient.js:1481 — callKlingVideoApi has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 16, ternaries 5 (10 pts), error handling 3 (7 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous).recoverPendingForEpisode (cognitive 61) · ×1
  • (anonymous).recoverPendingForEpisode (cognitive 61) frontweb/src/stores/generationTaskStore.js:397 — (anonymous).recoverPendingForEpisode has cognitive complexity 61 (threshold 15). Drivers by points: if/else 23 (40 pts), boolean chains 19, error handling 7 (13 pts), ternaries 7 (9 pts), loops 6 (7 pts), other 4 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · propImageGenerationService.processPropImageGeneration (cognitive 60) · ×1
  • propImageGenerationService.processPropImageGeneration (cognitive 60) backend-node/src/services/propImageGenerationService.js:21 — propImageGenerationService.processPropImageGeneration has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 20, if/else 14 (18 pts), error handling 9 (14 pts), ternaries 6 (8 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.
D2 · Cognitive Complexity · storyboards.routes.polishClassicVideoPromptStream (cognitive 59) · ×1
  • storyboards.routes.polishClassicVideoPromptStream (cognitive 59) REDACTED:777 — storyboards.routes.polishClassicVideoPromptStream has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 30, if/else 10 (11 pts), ternaries 8 (10 pts), error handling 8 (nesting depth added 3). Of this number, 55 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.
D2 · Cognitive Complexity · processCharacterGeneration (cognitive 57) · ×1
  • processCharacterGeneration (cognitive 57) backend-node/src/services/characterGenerationService.js:35 — processCharacterGeneration has cognitive complexity 57 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 6 (12 pts), boolean chains 11, other 10, loops 3 (5 pts), ternaries 2 (3 pts) (nesting depth added 15). Of this number, 51 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.
D2 · Cognitive Complexity · callAgnesVideoApi (cognitive 55) · ×1
  • callAgnesVideoApi (cognitive 55) backend-node/src/services/videoClient.js:2711 — callAgnesVideoApi has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 23, if/else 13 (19 pts), ternaries 5 (9 pts), error handling 2 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processVideoMerge (cognitive 55) · ×1
  • processVideoMerge (cognitive 55) backend-node/src/services/videoMergeService.js:190 — processVideoMerge has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 14, ternaries 3 (6 pts), error handling 3 (4 pts), loops 2 (nesting depth added 15). Of this number, 54 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.
D2 · Cognitive Complexity · createConfig (cognitive 54) · ×1
  • createConfig (cognitive 54) backend-node/src/services/aiConfigService.js:75 — createConfig has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 21, other 1, ternaries 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.
D2 · Cognitive Complexity · storyboards.postUniversalSegmentNdjsonStream (cognitive 52) · ×1
  • storyboards.postUniversalSegmentNdjsonStream (cognitive 52) frontweb/src/api/storyboards.js:9 — storyboards.postUniversalSegmentNdjsonStream has cognitive complexity 52 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 10, error handling 4 (10 pts), loops 2 (3 pts) (nesting depth added 23). Most of this is not in the body itself: 1 of the 52 points is its own statement and the rest belongs to one function literal inside it that branches (line 14). 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.
D2 · Cognitive Complexity · processPropExtraction (cognitive 52) · ×1
  • processPropExtraction (cognitive 52) backend-node/src/services/propExtractionService.js:9 — processPropExtraction has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 20, if/else 10 (20 pts), error handling 4 (7 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 15). Of this number, 48 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.
D2 · Cognitive Complexity · videoClient.callGeminiVideoApi (cognitive 51) · ×1
  • videoClient.callGeminiVideoApi (cognitive 51) backend-node/src/services/videoClient.js:1811 — videoClient.callGeminiVideoApi has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 14, error handling 4 (10 pts), ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · loadStoryboardCharacterNames (cognitive 51) · ×1
  • loadStoryboardCharacterNames (cognitive 51) backend-node/src/services/framePromptService.js:162 — loadStoryboardCharacterNames has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (30 pts), error handling 4 (11 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 25). Of this number, 37 points are the body's own statements and 14 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · syncGeneratingSetsFromStore (cognitive 50) · ×1
  • syncGeneratingSetsFromStore (cognitive 50) frontweb/src/composables/useGenerationTaskSync.js:33 — syncGeneratingSetsFromStore has cognitive complexity 50 (threshold 15). Drivers by points: if/else 16 (31 pts), loops 8 (15 pts), boolean chains 2, match/switch 1 (2 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.
D2 · Cognitive Complexity · callKlingImageApi (cognitive 47) · ×1
  • callKlingImageApi (cognitive 47) backend-node/src/services/imageClient.js:426 — callKlingImageApi has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 13, error handling 4 (6 pts), ternaries 4 (5 pts), loops 1 (nesting depth added 11). Of this number, 43 points are the body's own statements and 4 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveJimengApiImageBuffer (cognitive 46) · ×1
  • resolveJimengApiImageBuffer (cognitive 46) backend-node/src/services/videoClient.js:3272 — resolveJimengApiImageBuffer has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 10, ternaries 4 (10 pts), error handling 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · callMinimaxH3VideoApi (cognitive 46) · ×1
  • callMinimaxH3VideoApi (cognitive 46) backend-node/src/services/videoClient.js:3942 — callMinimaxH3VideoApi has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 12, ternaries 5 (8 pts), error handling 2 (3 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routes.create (cognitive 45) · ×1
  • routes.create (cognitive 45) backend-node/src/routes/videos.js:18 — routes.create has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 13, ternaries 9 (13 pts), if/else 6 (10 pts), other 6, error handling 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · streamGenerateText (cognitive 45) · ×1
  • streamGenerateText (cognitive 45) backend-node/src/services/aiClient.js:493 — streamGenerateText has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 9, ternaries 6 (8 pts), error handling 2, other 1 (nesting depth added 9). Of this number, 39 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useStoryGeneration.runGenerateStoryFromPremise (cognitive 44) · ×1
  • useStoryGeneration.runGenerateStoryFromPremise (cognitive 44) frontweb/src/composables/useStoryGeneration.js:12 — useStoryGeneration.runGenerateStoryFromPremise has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 23, if/else 10 (12 pts), ternaries 3 (5 pts), error handling 3 (4 pts) (nesting depth added 5). Of this number, 42 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · generateText (cognitive 44) · ×1
  • generateText (cognitive 44) backend-node/src/services/aiClient.js:376 — generateText has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 9, ternaries 5 (7 pts), error handling 2, other 1 (nesting depth added 9). Of this number, 38 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · narrationVideoPostProcess.runNarrationSubtitlePostProcess (cognitive 43) · ×1
  • narrationVideoPostProcess.runNarrationSubtitlePostProcess (cognitive 43) backend-node/src/services/narrationVideoPostProcess.js:205 — narrationVideoPostProcess.runNarrationSubtitlePostProcess has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (22 pts), error handling 6 (11 pts), boolean chains 6, loops 2, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generationTaskStore.useGenerationTaskStore.reconcileRunningTasks (cognitive 43) · ×1
  • generationTaskStore.useGenerationTaskStore.reconcileRunningTasks (cognitive 43) frontweb/src/stores/generationTaskStore.js:201 — generationTaskStore.useGenerationTaskStore.reconcileRunningTasks has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 10, error handling 1 (3 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous).reconcileRunningTasks (cognitive 43) · ×1
  • (anonymous).reconcileRunningTasks (cognitive 43) frontweb/src/stores/generationTaskStore.js:201 — (anonymous).reconcileRunningTasks has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 10, error handling 1 (3 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · inferPhotographyParams (cognitive 41) · ×1
  • inferPhotographyParams (cognitive 41) backend-node/src/services/angleService.js:378 — inferPhotographyParams has cognitive complexity 41 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 11, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · dramaCanvasAdapter.getAssetRelationHighlight (cognitive 40) · ×1
  • dramaCanvasAdapter.getAssetRelationHighlight (cognitive 40) frontweb/src/utils/dramaCanvasAdapter.js:449 — dramaCanvasAdapter.getAssetRelationHighlight has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · deriveStoryboardFieldsFromAi (cognitive 40) · ×1
  • deriveStoryboardFieldsFromAi (cognitive 40) backend-node/src/services/episodeStoryboardService.js:393 — deriveStoryboardFieldsFromAi has cognitive complexity 40 (threshold 15). Drivers by points: other 12, if/else 8 (11 pts), ternaries 9, boolean chains 8 (nesting depth added 3). Of this number, 39 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · processBackgroundExtraction (cognitive 39) · ×1
  • processBackgroundExtraction (cognitive 39) backend-node/src/services/backgroundExtractionService.js:60 — processBackgroundExtraction has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 10, error handling 4 (8 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 11). Of this number, 27 points are the body's own statements and 12 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.
D2 · Cognitive Complexity · videos.routes.create (cognitive 38) · ×1
  • videos.routes.create (cognitive 38) backend-node/src/routes/videos.js:18 — videos.routes.create has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 13, ternaries 8 (12 pts), if/else 6 (10 pts), error handling 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processFramePromptGeneration (cognitive 38) · ×1
  • processFramePromptGeneration (cognitive 38) backend-node/src/services/framePromptService.js:480 — processFramePromptGeneration has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 7, ternaries 4 (7 pts), loops 1 (3 pts), error handling 2 (nesting depth added 12). 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, split the body into named stages: move each independent 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 · hubJson (cognitive 38) · ×1
  • hubJson (cognitive 38) backend-node/src/services/jimengMaterialHubService.js:206 — hubJson has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 13, if/else 9 (13 pts), ternaries 5 (11 pts), 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.
D2 · Cognitive Complexity · framePromptService.buildStoryboardContext (cognitive 37) · ×1
  • framePromptService.buildStoryboardContext (cognitive 37) backend-node/src/services/framePromptService.js:265 — framePromptService.buildStoryboardContext has cognitive complexity 37 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 8, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · dramaService.getDrama (cognitive 36) · ×1
  • dramaService.getDrama (cognitive 36) backend-node/src/services/dramaService.js:67 — dramaService.getDrama has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 5 (11 pts), error handling 4 (8 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · videoClient.resolveImageInputForAgnesAsync (cognitive 36) · ×1
  • videoClient.resolveImageInputForAgnesAsync (cognitive 36) backend-node/src/services/videoClient.js:514 — videoClient.resolveImageInputForAgnesAsync has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 6, error handling 1 (3 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · videoClient.callKlingOmniVideoApi (cognitive 36) · ×1
  • videoClient.callKlingOmniVideoApi (cognitive 36) backend-node/src/services/videoClient.js:840 — videoClient.callKlingOmniVideoApi has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 7, ternaries 4 (6 pts), error handling 2 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · buildHubContext (cognitive 35) · ×1
  • buildHubContext (cognitive 35) backend-node/src/services/jimengMaterialHubService.js:58 — buildHubContext has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 16, if/else 11 (15 pts), other 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useCharacters.submitEditCharacter (cognitive 35) · ×1
  • useCharacters.submitEditCharacter (cognitive 35) frontweb/src/composables/filmCreate/useCharacters.js:211 — useCharacters.submitEditCharacter has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 21, if/else 5 (8 pts), ternaries 2 (4 pts), error handling 1, other 1 (nesting depth added 5). Of this number, 28 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · videoClient.parseDashScopeVideoUrl (cognitive 34) · ×1
  • videoClient.parseDashScopeVideoUrl (cognitive 34) backend-node/src/services/videoClient.js:1436 — videoClient.parseDashScopeVideoUrl has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · routes.linkTailFrame (cognitive 34) · ×1
  • routes.linkTailFrame (cognitive 34) REDACTED:11 — routes.linkTailFrame has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10, ternaries 5 (9 pts), error handling 2, other 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.
D2 · Cognitive Complexity · buildEpisodePipeline (cognitive 33) · ×1
  • buildEpisodePipeline (cognitive 33) frontweb/src/utils/dramaCanvasAdapter.js:165 — buildEpisodePipeline has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 7, ternaries 3, loops 2, other 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to one function literal inside it that branches (line 201). 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.
D2 · Cognitive Complexity · useCharacters.useCharacters.submitEditCharacter (cognitive 32) · ×1
  • useCharacters.useCharacters.submitEditCharacter (cognitive 32) frontweb/src/composables/filmCreate/useCharacters.js:211 — useCharacters.useCharacters.submitEditCharacter has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 21, if/else 5 (8 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Of this number, 25 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · episodeStoryboardService.buildFallbackUniversalSeedanceLine (cognitive 31) · ×1
  • episodeStoryboardService.buildFallbackUniversalSeedanceLine (cognitive 31) backend-node/src/services/episodeStoryboardService.js:159 — episodeStoryboardService.buildFallbackUniversalSeedanceLine has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 13, if/else 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · characterLibraryService.generateCharacterImage (cognitive 31) · ×1
  • characterLibraryService.generateCharacterImage (cognitive 31) backend-node/src/services/characterLibraryService.js:46 — characterLibraryService.generateCharacterImage has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (9 pts), if/else 8, error handling 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · audio.routes.extract (cognitive 31) · ×1
  • audio.routes.extract (cognitive 31) backend-node/src/routes/audio.js:15 — audio.routes.extract has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 11, error handling 2 (3 pts), ternaries 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.
D2 · Cognitive Complexity · routes.extract (cognitive 31) · ×1
  • routes.extract (cognitive 31) backend-node/src/routes/audio.js:15 — routes.extract has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 11, error handling 2 (3 pts), ternaries 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.
D2 · Cognitive Complexity · generateTextWithVision (cognitive 31) · ×1
  • generateTextWithVision (cognitive 31) backend-node/src/services/aiClient.js:641 — generateTextWithVision has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 9 (11 pts), boolean chains 7, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getStoryboardById (cognitive 31) · ×1
  • getStoryboardById (cognitive 31) backend-node/src/services/storyboardService.js:143 — getStoryboardById has cognitive complexity 31 (threshold 15). Drivers by points: other 19, if/else 4 (5 pts), error handling 2 (4 pts), ternaries 2, boolean chains 1 (nesting depth added 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.
D2 · Cognitive Complexity · aiConfigService.applyVendorLock (cognitive 30) · ×1
  • aiConfigService.applyVendorLock (cognitive 30) backend-node/src/services/aiConfigService.js:497 — aiConfigService.applyVendorLock has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 12, ternaries 3 (7 pts), if/else 5 (6 pts), loops 4, 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.
D2 · Cognitive Complexity · useCharacters.useCharacters.addCharToEpisode (cognitive 30) · ×1
  • useCharacters.useCharacters.addCharToEpisode (cognitive 30) frontweb/src/composables/filmCreate/useCharacters.js:535 — useCharacters.useCharacters.addCharToEpisode has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 23, if/else 5 (6 pts), error handling 1 (nesting depth added 1). Of this number, 22 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · generateVideoPrompt (cognitive 30) · ×1
  • generateVideoPrompt (cognitive 30) backend-node/src/services/episodeStoryboardService.js:294 — generateVideoPrompt has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 4, ternaries 2 (3 pts), other 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, 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 · callModelArkAsset (cognitive 30) · ×1
  • callModelArkAsset (cognitive 30) backend-node/src/services/modelArkAssetProxyService.js:182 — callModelArkAsset has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 12, ternaries 2, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · generateStory (cognitive 30) · ×1
  • generateStory (cognitive 30) backend-node/src/services/storyGenerationService.js:9 — generateStory has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 18, if/else 7 (9 pts), other 2, error handling 1 (nesting depth added 2). Of this number, 26 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, 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.
D2 · Cognitive Complexity · normalizeUniversalSegmentShotDurations (cognitive 30) · ×1
  • normalizeUniversalSegmentShotDurations (cognitive 30) backend-node/src/services/universalSegmentDurationNormalize.js:7 — normalizeUniversalSegmentShotDurations has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 8, loops 4 (5 pts), ternaries 2 (4 pts) (nesting depth added 6). Of this number, 27 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · storyboards.routes.batchInferParams (cognitive 29) · ×1
  • storyboards.routes.batchInferParams (cognitive 29) REDACTED:1067 — storyboards.routes.batchInferParams has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 5 (10 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · app.createApp (cognitive 29) · ×1
  • app.createApp (cognitive 29) REDACTED:11 — app.createApp has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 6 (10 pts), boolean chains 5, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 104, 80, 75, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · callVeo3VideoApi (cognitive 29) · ×1
  • callVeo3VideoApi (cognitive 29) backend-node/src/services/videoClient.js:2420 — callVeo3VideoApi has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 11, error handling 2 (3 pts), ternaries 1 (3 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.
D2 · Cognitive Complexity · aiConfigService.updateConfig (cognitive 28) · ×1
  • aiConfigService.updateConfig (cognitive 28) backend-node/src/services/aiConfigService.js:149 — aiConfigService.updateConfig has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16, ternaries 5 (10 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · videoClient.probeViduReferenceImageSize (cognitive 28) · ×1
  • videoClient.probeViduReferenceImageSize (cognitive 28) backend-node/src/services/videoClient.js:2020 — videoClient.probeViduReferenceImageSize has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 7, ternaries 1 (3 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parseScriptIntoEpisodes (cognitive 28) · ×1
  • parseScriptIntoEpisodes (cognitive 28) frontweb/src/utils/scriptEpisodes.js:6 — parseScriptIntoEpisodes has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (6 pts), other 3, loops 2, boolean chains 1 (nesting depth added 10). Of this number, 18 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · useCharacters.addCharToEpisode (cognitive 28) · ×1
  • useCharacters.addCharToEpisode (cognitive 28) frontweb/src/composables/filmCreate/useCharacters.js:535 — useCharacters.addCharToEpisode has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 20, if/else 5 (6 pts), error handling 1, other 1 (nesting depth added 1). Of this number, 20 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · safeJson.extractJsonCandidate (cognitive 27) · ×1
  • safeJson.extractJsonCandidate (cognitive 27) backend-node/src/utils/safeJson.js:4 — safeJson.extractJsonCandidate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 3, loops 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.
D2 · Cognitive Complexity · safeJson.repairTruncatedJsonArray (cognitive 27) · ×1
  • safeJson.repairTruncatedJsonArray (cognitive 27) backend-node/src/utils/safeJson.js:48 — safeJson.repairTruncatedJsonArray has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · framePromptService.expandAngleDescriptionLegacy (cognitive 27) · ×1
  • framePromptService.expandAngleDescriptionLegacy (cognitive 27) backend-node/src/services/framePromptService.js:33 — framePromptService.expandAngleDescriptionLegacy has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 8 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · episodeStoryboardService.tryIncrementalSave (cognitive 27) · ×1
  • episodeStoryboardService.tryIncrementalSave (cognitive 27) backend-node/src/services/episodeStoryboardService.js:588 — episodeStoryboardService.tryIncrementalSave has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 4 (8 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · tailFrameLinkService.routes.linkTailFrame (cognitive 27) · ×1
  • tailFrameLinkService.routes.linkTailFrame (cognitive 27) REDACTED:11 — tailFrameLinkService.routes.linkTailFrame has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10, ternaries 3, error handling 2 (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.
D2 · Cognitive Complexity · videoClient.resolveSoraImageToDataUrl (cognitive 27) · ×1
  • videoClient.resolveSoraImageToDataUrl (cognitive 27) backend-node/src/services/videoClient.js:2908 — videoClient.resolveSoraImageToDataUrl has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, error handling 3 (6 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.
D2 · Cognitive Complexity · index.setupRouter (cognitive 27) · ×1
  • index.setupRouter (cognitive 27) REDACTED:25 — index.setupRouter has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 12, if/else 9 (10 pts), error handling 5 (nesting depth added 1). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 60, 122, 194, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · saveOutline (cognitive 27) · ×1
  • saveOutline (cognitive 27) backend-node/src/services/dramaService.js:467 — saveOutline has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (7 pts), boolean chains 6, error handling 2 (4 pts), other 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveImageRef (cognitive 27) · ×1
  • resolveImageRef (cognitive 27) backend-node/src/services/imageClient.js:866 — resolveImageRef has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 11, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). Of this number, 22 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body: 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 · index.getHistory (cognitive 26) · ×1
  • index.getHistory (cognitive 26) backend-node/src/mastra/index.mjs:270 — index.getHistory has cognitive complexity 26 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 3 (6 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routes.batchInferParams (cognitive 26) · ×1
  • routes.batchInferParams (cognitive 26) REDACTED:1067 — routes.batchInferParams has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (10 pts), boolean chains 2, error handling 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.
D2 · Cognitive Complexity · loadStoryboardCharacterIds (cognitive 26) · ×1
  • loadStoryboardCharacterIds (cognitive 26) backend-node/src/services/episodeStoryboardService.js:1352 — loadStoryboardCharacterIds has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 8, loops 2 (5 pts), error handling 2 (3 pts) (nesting depth added 8). Of this number, 25 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.
D2 · Cognitive Complexity · buildSplitPlansFromStoryboard (cognitive 26) · ×1
  • buildSplitPlansFromStoryboard (cognitive 26) backend-node/src/services/episodeStoryboardService.js:1501 — buildSplitPlansFromStoryboard has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 10, if/else 3, loops 1 (nesting depth added 5). Of this number, 25 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · buildCharacterAnchorText (cognitive 26) · ×1
  • buildCharacterAnchorText (cognitive 26) backend-node/src/services/framePromptService.js:127 — buildCharacterAnchorText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 9 (nesting depth added 8). Of this number, 25 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · synthesize (cognitive 26) · ×1
  • synthesize (cognitive 26) REDACTED:119 — synthesize has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, if/else 6, error handling 2, ternaries 1. Of this number, 25 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · downloadImageToLocal (cognitive 26) · ×1
  • downloadImageToLocal (cognitive 26) backend-node/src/services/uploadService.js:91 — downloadImageToLocal has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (7 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · safeJson.escapeNewlinesInStrings (cognitive 25) · ×1
  • safeJson.escapeNewlinesInStrings (cognitive 25) backend-node/src/utils/safeJson.js:138 — safeJson.escapeNewlinesInStrings has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 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.
D2 · Cognitive Complexity · videoClient.resolveVolcClassicImage (cognitive 25) · ×1
  • videoClient.resolveVolcClassicImage (cognitive 25) backend-node/src/services/videoClient.js:3820 — videoClient.resolveVolcClassicImage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 9, error handling 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tools.executeGenerateImage (cognitive 25) · ×1
  • tools.executeGenerateImage (cognitive 25) backend-node/src/mastra/tools.mjs:269 — tools.executeGenerateImage has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, if/else 6 (7 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · generationTaskStore.useGenerationTaskStore.pollTask (cognitive 25) · ×1
  • generationTaskStore.useGenerationTaskStore.pollTask (cognitive 25) frontweb/src/stores/generationTaskStore.js:254 — generationTaskStore.useGenerationTaskStore.pollTask has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 271). 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.
D2 · Cognitive Complexity · postJSONStream (cognitive 25) · ×1
  • postJSONStream (cognitive 25) backend-node/src/services/aiClient.js:120 — postJSONStream has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, error handling 1 (2 pts), ternaries 2, loops 1 (nesting depth added 11). None of this is in the body itself: all 25 points belong to 10 function items inside it that branch (a function literal at line 169, a function literal at line 121, a function literal at line 151, …). 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 · listDramas (cognitive 25) · ×1
  • listDramas (cognitive 25) backend-node/src/services/dramaService.js:167 — listDramas has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (7 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 196, 218, 191, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · rowToStoryboard (cognitive 25) · ×1
  • rowToStoryboard (cognitive 25) backend-node/src/services/dramaService.js:348 — rowToStoryboard has cognitive complexity 25 (threshold 15). Drivers by points: other 22, ternaries 2, boolean chains 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.
D2 · Cognitive Complexity · buildFallbackUniversalMultiBeatText (cognitive 25) · ×1
  • buildFallbackUniversalMultiBeatText (cognitive 25) backend-node/src/services/universalOmniMultiBeatFormat.js:37 — buildFallbackUniversalMultiBeatText has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (10 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · extractPollFailureMessage (cognitive 25) · ×1
  • extractPollFailureMessage (cognitive 25) backend-node/src/services/videoClient.js:1255 — extractPollFailureMessage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7, loops 3 (4 pts), ternaries 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · storyboardService.updateStoryboard (cognitive 24) · ×1
  • storyboardService.updateStoryboard (cognitive 24) backend-node/src/services/storyboardService.js:87 — storyboardService.updateStoryboard has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 4 (8 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · videoMergeService.resolveVideoToLocalPath (cognitive 24) · ×1
  • videoMergeService.resolveVideoToLocalPath (cognitive 24) backend-node/src/services/videoMergeService.js:84 — videoMergeService.resolveVideoToLocalPath has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, ternaries 3 (5 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · modelArkAssetConfigService.buildModelArkContext (cognitive 24) · ×1
  • modelArkAssetConfigService.buildModelArkContext (cognitive 24) backend-node/src/services/modelArkAssetConfigService.js:34 — modelArkAssetConfigService.buildModelArkContext has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (11 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · sceneService.generateSceneFourViewImage (cognitive 24) · ×1
  • sceneService.generateSceneFourViewImage (cognitive 24) backend-node/src/services/sceneService.js:313 — sceneService.generateSceneFourViewImage has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, ternaries 3 (6 pts), error handling 2 (4 pts), if/else 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (sceneService.generateSceneSingleImage) 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.
D2 · Cognitive Complexity · sceneService.generateSceneSingleImage (cognitive 24) · ×1
  • sceneService.generateSceneSingleImage (cognitive 24) backend-node/src/services/sceneService.js:389 — sceneService.generateSceneSingleImage has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, ternaries 3 (6 pts), error handling 2 (4 pts), if/else 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (sceneService.generateSceneFourViewImage) 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.
D2 · Cognitive Complexity · splitNineGridToImages (cognitive 24) · ×1
  • splitNineGridToImages (cognitive 24) backend-node/src/services/imageService.js:314 — splitNineGridToImages has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 3 (8 pts), error handling 3 (4 pts), loops 3 (4 pts), other 4, boolean chains 3, if/else 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.
D2 · Cognitive Complexity · formatVideoPostBodyForLog (cognitive 24) · ×1
  • formatVideoPostBodyForLog (cognitive 24) backend-node/src/services/videoClient.js:2598 — formatVideoPostBodyForLog has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 5 (nesting depth added 5). Of this number, 12 points are the body's own statements and 12 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · seedance2AssetGuards.markStaleOnCharacterMainImageDrift (cognitive 23) · ×1
  • seedance2AssetGuards.markStaleOnCharacterMainImageDrift (cognitive 23) backend-node/src/utils/seedance2AssetGuards.js:24 — seedance2AssetGuards.markStaleOnCharacterMainImageDrift has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (7 pts), error handling 1 (3 pts), ternaries 2 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · imageClient.getDefaultImageConfig (cognitive 23) · ×1
  • imageClient.getDefaultImageConfig (cognitive 23) backend-node/src/services/imageClient.js:113 — imageClient.getDefaultImageConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (7 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · videoClient.buildSd2ActiveAssetUrlLookup (cognitive 23) · ×1
  • videoClient.buildSd2ActiveAssetUrlLookup (cognitive 23) backend-node/src/services/videoClient.js:3720 — videoClient.buildSd2ActiveAssetUrlLookup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 8, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · context.assertOwned (cognitive 23) · ×1
  • context.assertOwned (cognitive 23) backend-node/src/mastra/context.mjs:25 — context.assertOwned has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 7 (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 · (anonymous).pollTask · ×1
  • (anonymous).pollTask::(anonymous)::tick (cognitive 23) frontweb/src/stores/generationTaskStore.js:271 — (anonymous).pollTask::(anonymous)::tick has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, error handling 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.
D2 · Cognitive Complexity · useCharacters.editCharacter (cognitive 23) · ×1
  • useCharacters.editCharacter (cognitive 23) frontweb/src/composables/filmCreate/useCharacters.js:155 — useCharacters.editCharacter has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 4 (7 pts), error handling 1 (2 pts), ternaries 2 (nesting depth added 4). Of this number, 15 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · useScenes.submitEditScene (cognitive 23) · ×1
  • useScenes.submitEditScene (cognitive 23) frontweb/src/composables/filmCreate/useScenes.js:248 — useScenes.submitEditScene has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (8 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
D2 · Cognitive Complexity · storyboards.extractRetentionClausesFromVideoPrompts (cognitive 22) · ×1
  • storyboards.extractRetentionClausesFromVideoPrompts (cognitive 22) REDACTED:44 — storyboards.extractRetentionClausesFromVideoPrompts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · videoClient.pickVideoUrlFromResultShape (cognitive 22) · ×1
  • videoClient.pickVideoUrlFromResultShape (cognitive 22) backend-node/src/services/videoClient.js:1338 — videoClient.pickVideoUrlFromResultShape has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, ternaries 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · videoClient.loadViduReferenceImageBuffer (cognitive 22) · ×1
  • videoClient.loadViduReferenceImageBuffer (cognitive 22) backend-node/src/services/videoClient.js:1954 — videoClient.loadViduReferenceImageBuffer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useScenes.useScenes.submitEditScene (cognitive 22) · ×1
  • useScenes.useScenes.submitEditScene (cognitive 22) frontweb/src/composables/filmCreate/useScenes.js:248 — useScenes.useScenes.submitEditScene has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, if/else 5 (8 pts), error handling 1 (nesting depth added 3). Of this number, 19 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.
D2 · Cognitive Complexity · syncStoryboardCharacters (cognitive 22) · ×1
  • syncStoryboardCharacters (cognitive 22) backend-node/src/services/imageService.js:1628 — syncStoryboardCharacters has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 3, boolean chains 2, loops 1, other 1, ternaries 1 (nesting depth added 5). Of this number, 20 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.
D2 · Cognitive Complexity · resolveImageInputForOmniLocalBase64 (cognitive 22) · ×1
  • resolveImageInputForOmniLocalBase64 (cognitive 22) backend-node/src/services/videoClient.js:393 — resolveImageInputForOmniLocalBase64 has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, ternaries 2 (4 pts), error handling 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · toAgentSseEvent (cognitive 22) · ×1
  • toAgentSseEvent (cognitive 22) backend-node/src/mastra/sse.mjs:11 — toAgentSseEvent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, if/else 6, ternaries 1 (2 pts), other 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · uploadService.uploadToImageProxy (cognitive 21) · ×1
  • uploadService.uploadToImageProxy (cognitive 21) backend-node/src/services/uploadService.js:165 — uploadService.uploadToImageProxy has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · episodeStoryboardService.buildCameraMotionChain (cognitive 21) · ×1
  • episodeStoryboardService.buildCameraMotionChain (cognitive 21) backend-node/src/services/episodeStoryboardService.js:130 — episodeStoryboardService.buildCameraMotionChain has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (9 pts), ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · characterLibraryService.updateCharacter (cognitive 21) · ×1
  • characterLibraryService.updateCharacter (cognitive 21) backend-node/src/services/characterLibraryService.js:307 — characterLibraryService.updateCharacter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14, ternaries 3 (6 pts), 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.
D2 · Cognitive Complexity · characterLibraryService.generateCharacterFourViewImage (cognitive 21) · ×1
  • characterLibraryService.generateCharacterFourViewImage (cognitive 21) backend-node/src/services/characterLibraryService.js:532 — characterLibraryService.generateCharacterFourViewImage has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), error handling 2 (4 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tools.executeSaveEpisodeScript (cognitive 21) · ×1
  • tools.executeSaveEpisodeScript (cognitive 21) backend-node/src/mastra/tools.mjs:117 — tools.executeSaveEpisodeScript has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, ternaries 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · useProps.useProps.addPropToEpisode (cognitive 21) · ×1
  • useProps.useProps.addPropToEpisode (cognitive 21) frontweb/src/composables/filmCreate/useProps.js:498 — useProps.useProps.addPropToEpisode has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, if/else 3, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · exportStoryboardSheet.buildStoryboardSheetRows (cognitive 21) · ×1
  • exportStoryboardSheet.buildStoryboardSheetRows (cognitive 21) frontweb/src/utils/exportStoryboardSheet.js:101 — exportStoryboardSheet.buildStoryboardSheetRows has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (12 pts), boolean chains 8, 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.
D2 · Cognitive Complexity · unwrapModelArkAssetView (cognitive 21) · ×1
  • unwrapModelArkAssetView (cognitive 21) backend-node/src/services/modelArkAssetConfigService.js:120 — unwrapModelArkAssetView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), other 3, 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.
D2 · Cognitive Complexity · useProps.addPropToEpisode (cognitive 21) · ×1
  • useProps.addPropToEpisode (cognitive 21) frontweb/src/composables/filmCreate/useProps.js:498 — useProps.addPropToEpisode has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, if/else 3, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · buildClassicRequiredCoverageDigest (cognitive 20) · ×1
  • buildClassicRequiredCoverageDigest (cognitive 20) REDACTED:150 — buildClassicRequiredCoverageDigest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 3 (4 pts) (nesting depth added 2). Of this number, 17 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, 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 · extractBackgroundsForEpisode (cognitive 20) · ×1
  • extractBackgroundsForEpisode (cognitive 20) backend-node/src/services/backgroundExtractionService.js:168 — extractBackgroundsForEpisode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, error handling 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent 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 · unwrapMaterialHubAssetView (cognitive 20) · ×1
  • unwrapMaterialHubAssetView (cognitive 20) backend-node/src/services/jimengMaterialHubService.js:176 — unwrapMaterialHubAssetView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 2 (3 pts), other 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.
D2 · Cognitive Complexity · finalizeSuccessfulVideo (cognitive 20) · ×1
  • finalizeSuccessfulVideo (cognitive 20) backend-node/src/services/videoService.js:231 — finalizeSuccessfulVideo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 3 (4 pts), ternaries 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · executeUpdateCharacter (cognitive 20) · ×1
  • executeUpdateCharacter (cognitive 20) backend-node/src/mastra/tools.mjs:160 — executeUpdateCharacter has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, other 4, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · framePromptService.generateSingleFrame (cognitive 19) · ×1
  • framePromptService.generateSingleFrame (cognitive 19) backend-node/src/services/framePromptService.js:421 — framePromptService.generateSingleFrame has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (14 pts), boolean chains 3, error handling 1, if/else 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tools.executeGetCurrentProject (cognitive 19) · ×1
  • tools.executeGetCurrentProject (cognitive 19) backend-node/src/mastra/tools.mjs:27 — tools.executeGetCurrentProject has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (6 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · useScenes.useScenes.addSceneToEpisode (cognitive 19) · ×1
  • useScenes.useScenes.addSceneToEpisode (cognitive 19) frontweb/src/composables/filmCreate/useScenes.js:521 — useScenes.useScenes.addSceneToEpisode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 3, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · refreshCharacterJimengMaterialAsset (cognitive 19) · ×1
  • refreshCharacterJimengMaterialAsset (cognitive 19) backend-node/src/services/characterLibraryService.js:1000 — refreshCharacterJimengMaterialAsset has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, other 2, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getStoryboardsForEpisode (cognitive 19) · ×1
  • getStoryboardsForEpisode (cognitive 19) backend-node/src/services/episodeStoryboardService.js:191 — getStoryboardsForEpisode has cognitive complexity 19 (threshold 15). Drivers by points: other 9, if/else 4 (5 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 197, 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.
D2 · Cognitive Complexity · insertOneStoryboard (cognitive 19) · ×1
  • insertOneStoryboard (cognitive 19) backend-node/src/services/episodeStoryboardService.js:553 — insertOneStoryboard has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, other 4, error handling 2 (3 pts), loops 1 (2 pts), if/else 1, ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · persistSplitStoryboardRow (cognitive 19) · ×1
  • persistSplitStoryboardRow (cognitive 19) backend-node/src/services/episodeStoryboardService.js:1559 — persistSplitStoryboardRow has cognitive complexity 19 (threshold 15). Drivers by points: other 18, 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.
D2 · Cognitive Complexity · resolveVideoProtocol (cognitive 19) · ×1
  • resolveVideoProtocol (cognitive 19) backend-node/src/services/videoClient.js:133 — resolveVideoProtocol has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (6 pts), ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · resumeFailedVideoPoll (cognitive 19) · ×1
  • resumeFailedVideoPoll (cognitive 19) backend-node/src/services/videoService.js:376 — resumeFailedVideoPoll has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 4 (6 pts), boolean chains 3 (nesting depth added 4). Of this number, 15 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · useCanvasEpisodeGenerate.aiGenerateStoryboards (cognitive 19) · ×1
  • useCanvasEpisodeGenerate.aiGenerateStoryboards (cognitive 19) frontweb/src/composables/useCanvasEpisodeGenerate.js:98 — useCanvasEpisodeGenerate.aiGenerateStoryboards has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 3 (4 pts), loops 1, other 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · useScenes.editScene (cognitive 19) · ×1
  • useScenes.editScene (cognitive 19) frontweb/src/composables/filmCreate/useScenes.js:132 — useScenes.editScene has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (7 pts), error handling 1 (2 pts) (nesting depth added 4). Of this number, 11 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, 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.
D2 · Cognitive Complexity · useScenes.addSceneToEpisode (cognitive 19) · ×1
  • useScenes.addSceneToEpisode (cognitive 19) frontweb/src/composables/filmCreate/useScenes.js:521 — useScenes.addSceneToEpisode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 3, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · imageService.normalizeSavedImageToTargetPixels (cognitive 18) · ×1
  • imageService.normalizeSavedImageToTargetPixels (cognitive 18) backend-node/src/services/imageService.js:470 — imageService.normalizeSavedImageToTargetPixels has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, error handling 3 (4 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 · dramaService.getVideoUrlForStoryboard (cognitive 18) · ×1
  • dramaService.getVideoUrlForStoryboard (cognitive 18) backend-node/src/services/dramaService.js:748 — dramaService.getVideoUrlForStoryboard has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 11 points are the body's own statements and 7 belong to one function item 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.
D2 · Cognitive Complexity · videoClient.logKlingOmniAuthDebug (cognitive 18) · ×1
  • videoClient.logKlingOmniAuthDebug (cognitive 18) backend-node/src/services/videoClient.js:239 — videoClient.logKlingOmniAuthDebug has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 6, if/else 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.
D2 · Cognitive Complexity · tools.executeUpdateScene (cognitive 18) · ×1
  • tools.executeUpdateScene (cognitive 18) backend-node/src/mastra/tools.mjs:186 — tools.executeUpdateScene has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tools.executeDeleteItem (cognitive 18) · ×1
  • tools.executeDeleteItem (cognitive 18) backend-node/src/mastra/tools.mjs:327 — tools.executeDeleteItem has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useCanvasWorkflowRunner.runStoryboardPipeline (cognitive 18) · ×1
  • useCanvasWorkflowRunner.runStoryboardPipeline (cognitive 18) frontweb/src/composables/useCanvasWorkflowRunner.js:93 — useCanvasWorkflowRunner.runStoryboardPipeline has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, error handling 1 (2 pts), loops 1, 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.
D2 · Cognitive Complexity · routes.putImage (cognitive 18) · ×1
  • routes.putImage (cognitive 18) REDACTED:157 — routes.putImage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), other 3, ternaries 2, boolean chains 1, error handling 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.
D2 · Cognitive Complexity · saveEpisodes (cognitive 18) · ×1
  • saveEpisodes (cognitive 18) backend-node/src/services/dramaService.js:650 — saveEpisodes has cognitive complexity 18 (threshold 15). Drivers by points: other 7, if/else 4 (6 pts), boolean chains 3, loops 2 (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.
D2 · Cognitive Complexity · buildCharacterAppearancesFromAiCharacters (cognitive 18) · ×1
  • buildCharacterAppearancesFromAiCharacters (cognitive 18) backend-node/src/services/episodeStoryboardService.js:351 — buildCharacterAppearancesFromAiCharacters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (6 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create (cognitive 18) · ×1
  • create (cognitive 18) backend-node/src/services/imageService.js:532 — create has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, other 4, if/else 3, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · (anonymous).recoverPendingForEpisode · ×1
  • (anonymous).recoverPendingForEpisode::attachImage (cognitive 18) frontweb/src/stores/generationTaskStore.js:435 — (anonymous).recoverPendingForEpisode::attachImage has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 3 (5 pts), other 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.
D2 · Cognitive Complexity · imageClient.inferProtocol (cognitive 17) · ×1
  • imageClient.inferProtocol (cognitive 17) backend-node/src/services/imageClient.js:92 — imageClient.inferProtocol has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 8. 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.
D2 · Cognitive Complexity · safeJson.extractWrappedArrayStr (cognitive 17) · ×1
  • safeJson.extractWrappedArrayStr (cognitive 17) backend-node/src/utils/safeJson.js:103 — safeJson.extractWrappedArrayStr has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · storyboards.routes.polishUniversalSegmentStream (cognitive 17) · ×1
  • storyboards.routes.polishUniversalSegmentStream (cognitive 17) REDACTED:655 — storyboards.routes.polishUniversalSegmentStream has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), error handling 3, ternaries 1 (nesting depth added 1). To reduce it, split the body into named stages: move each independent 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 · routes.polishUniversalSegmentStream (cognitive 17) · ×1
  • routes.polishUniversalSegmentStream (cognitive 17) REDACTED:655 — routes.polishUniversalSegmentStream has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), error handling 3, ternaries 1 (nesting depth added 1). To reduce it, split the body into named stages: move each independent 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 · registerCharacterViaJimengHub (cognitive 17) · ×1
  • registerCharacterViaJimengHub (cognitive 17) backend-node/src/services/characterLibraryService.js:848 — registerCharacterViaJimengHub has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 2, other 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.
D2 · Cognitive Complexity · updateStoryboardRowFromDerived (cognitive 17) · ×1
  • updateStoryboardRowFromDerived (cognitive 17) backend-node/src/services/episodeStoryboardService.js:498 — updateStoryboardRowFromDerived has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, other 4, loops 1 (2 pts), error handling 1, if/else 1, ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · callDashScopeVideoApi · ×1
  • callDashScopeVideoApi::toImageInput (cognitive 17) backend-node/src/services/videoClient.js:1669 — callDashScopeVideoApi::toImageInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useProps.editProp (cognitive 17) · ×1
  • useProps.editProp (cognitive 17) frontweb/src/composables/filmCreate/useProps.js:133 — useProps.editProp has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (7 pts), error handling 1 (2 pts) (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · seedance2AssetGuards.markStaleOnCharacterVoiceDrift (cognitive 16) · ×1
  • seedance2AssetGuards.markStaleOnCharacterVoiceDrift (cognitive 16) backend-node/src/utils/seedance2AssetGuards.js:88 — seedance2AssetGuards.markStaleOnCharacterVoiceDrift has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, error handling 1 (3 pts), ternaries 1 (nesting depth added 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.
D2 · Cognitive Complexity · aiClient.resolveEntityImageSource (cognitive 16) · ×1
  • aiClient.resolveEntityImageSource (cognitive 16) backend-node/src/services/aiClient.js:604 — aiClient.resolveEntityImageSource has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (nesting depth added 3). Of this number, 14 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.
D2 · Cognitive Complexity · promptI18n.buildStoryExpansionUserPrompt (cognitive 16) · ×1
  • promptI18n.buildStoryExpansionUserPrompt (cognitive 16) backend-node/src/services/promptI18n.js:931 — promptI18n.buildStoryExpansionUserPrompt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dramaStyleMerge.mergeCfgStyleWithDrama (cognitive 16) · ×1
  • dramaStyleMerge.mergeCfgStyleWithDrama (cognitive 16) backend-node/src/utils/dramaStyleMerge.js:52 — dramaStyleMerge.mergeCfgStyleWithDrama has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 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.
D2 · Cognitive Complexity · framePromptService.regenerateLayoutDescription (cognitive 16) · ×1
  • framePromptService.regenerateLayoutDescription (cognitive 16) backend-node/src/services/framePromptService.js:629 — framePromptService.regenerateLayoutDescription has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7, boolean chains 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.
D2 · Cognitive Complexity · storyboardFrameBinding.bindStoryboardFrameImage (cognitive 16) · ×1
  • storyboardFrameBinding.bindStoryboardFrameImage (cognitive 16) backend-node/src/services/storyboardFrameBinding.js:6 — storyboardFrameBinding.bindStoryboardFrameImage has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4, ternaries 4, error handling 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · characterLibraryService.buildFourViewImagePrompt (cognitive 16) · ×1
  • characterLibraryService.buildFourViewImagePrompt (cognitive 16) backend-node/src/services/characterLibraryService.js:452 — characterLibraryService.buildFourViewImagePrompt has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 4 (5 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · videoClient.inferVideoProtocol (cognitive 16) · ×1
  • videoClient.inferVideoProtocol (cognitive 16) backend-node/src/services/videoClient.js:26 — videoClient.inferVideoProtocol has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 5. 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 · videoClient.buildAgnesVideo25Body (cognitive 16) · ×1
  • videoClient.buildAgnesVideo25Body (cognitive 16) backend-node/src/services/videoClient.js:2550 — videoClient.buildAgnesVideo25Body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), boolean chains 5, ternaries 3 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useCanvasAssetGenerate.generateAssetReferenceImage (cognitive 16) · ×1
  • useCanvasAssetGenerate.generateAssetReferenceImage (cognitive 16) frontweb/src/composables/useCanvasAssetGenerate.js:38 — useCanvasAssetGenerate.generateAssetReferenceImage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 5). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useCanvasEpisodeGenerate.useCanvasEpisodeGenerate.aiGenerateStoryboards (cognitive 16) · ×1
  • useCanvasEpisodeGenerate.useCanvasEpisodeGenerate.aiGenerateStoryboards (cognitive 16) frontweb/src/composables/useCanvasEpisodeGenerate.js:98 — useCanvasEpisodeGenerate.useCanvasEpisodeGenerate.aiGenerateStoryboards has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 2 (3 pts), loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useCanvasScript.useCanvasScript.extractAll (cognitive 16) · ×1
  • useCanvasScript.useCanvasScript.extractAll (cognitive 16) frontweb/src/composables/useCanvasScript.js:158 — useCanvasScript.useCanvasScript.extractAll has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7, error handling 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · routes.uploadImage (cognitive 16) · ×1
  • routes.uploadImage (cognitive 16) backend-node/src/routes/upload.js:52 — routes.uploadImage has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (4 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · splitQuadGridToImages (cognitive 16) · ×1
  • splitQuadGridToImages (cognitive 16) backend-node/src/services/imageService.js:96 — splitQuadGridToImages has cognitive complexity 16 (threshold 15). Drivers by points: other 5, error handling 3 (4 pts), boolean chains 3, ternaries 1 (2 pts), if/else 1, loops 1 (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.
D2 · Cognitive Complexity · ipv4Request (cognitive 16) · ×1
  • ipv4Request (cognitive 16) backend-node/src/utils/ipv4Http.js:16 — ipv4Request has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 4 (5 pts), if/else 3 (4 pts), error handling 1 (nesting depth added 2). Of this number, 9 points are the body's own statements and 7 belong to 9 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 · runVideoStep (cognitive 16) · ×1
  • runVideoStep (cognitive 16) frontweb/src/composables/useCanvasWorkflowRunner.js:49 — runVideoStep has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (4 pts), other 1, ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 215 plain JS — the untyped files are REDACTED, backend-node/src/config/index.js, backend-node/src/config/videoGeneration.js, backend-node/src/constants/generationStylePresets.js, backend-node/src/db/index.js, backend-node/src/db/migrate.js (+209 more).
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (9 clone groups) REDACTED:456 — 9 duplicated blocks under backend-node/src/ have copies in at least two of the sibling directories routes, services, utils — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (9 clone groups) frontweb/src/composables/filmCreate/useProps.js:570 — 9 duplicated blocks under frontweb/src/ have copies in at least two of the sibling directories components, composables, utils, views — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (392 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (392 matched lines × 2 locations) frontweb/src/composables/filmCreate/useProps.js:70 — frontweb/src/composables/filmCreate/useProps.js:70 · frontweb/src/composables/filmCreate/useScenes.js:63 — the two spans are one implementation copied and then locally edited — 2424 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 (250 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (250 matched lines × 2 locations) backend-node/src/services/mergedEpisodePostProcess.js:9 — backend-node/src/services/mergedEpisodePostProcess.js:9 · backend-node/src/services/narrationVideoPostProcess.js:9 — the two spans are one implementation copied and then locally edited — 1978 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 (186 lines × 2 locations) · ×1
  • Duplicated block (186 lines × 2 locations) frontweb/src/composables/filmCreate/useCharacters.js:343 — frontweb/src/composables/filmCreate/useCharacters.js:343 · frontweb/src/composables/filmCreate/useProps.js:305 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (138 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (138 matched lines × 2 locations) backend-node/src/services/propLibraryService.js:12 — backend-node/src/services/propLibraryService.js:12 · backend-node/src/services/sceneLibraryService.js:14 — the two spans are one implementation copied and then locally edited — 1372 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 (105 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (105 matched lines × 2 locations) frontweb/src/composables/filmCreate/useCharacters.js:24 — frontweb/src/composables/filmCreate/useCharacters.js:24 · frontweb/src/composables/filmCreate/useScenes.js:24 — the two spans are one implementation copied and then locally edited — 720 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 (82 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (82 matched lines × 2 locations) backend-node/src/services/aiClient.js:377 — backend-node/src/services/aiClient.js:377 · backend-node/src/services/aiClient.js:494 — the two spans are one implementation copied and then locally edited — 618 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (71 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (71 matched lines × 2 locations) backend-node/src/services/jimengMaterialHubService.js:158 — backend-node/src/services/jimengMaterialHubService.js:158 · backend-node/src/services/modelArkAssetConfigService.js:110 — the two spans are one implementation copied and then locally edited — 531 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 (68 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (68 matched lines × 2 locations) backend-node/src/services/backgroundExtractionService.js:60 — backend-node/src/services/backgroundExtractionService.js:60 · backend-node/src/services/propExtractionService.js:9 — the two spans are one implementation copied and then locally edited — 503 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 (63 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (63 matched lines × 2 locations) backend-node/src/services/imageService.js:86 — backend-node/src/services/imageService.js:86 · backend-node/src/services/imageService.js:307 — the two spans are one implementation copied and then locally edited — 530 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (60 lines × 2 locations) · ×1
  • Duplicated block (60 lines × 2 locations) frontweb/src/views/FilmCreate.vue:7690 — frontweb/src/views/FilmCreate.vue:7690 · frontweb/src/views/FilmCreate.vue:8031 — 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.
R10 · Code Duplication · Duplicated block (53 lines × 3 locations) · ×1
  • Duplicated block (53 lines × 3 locations) backend-node/src/routes/characterLibrary.js:4 — backend-node/src/routes/characterLibrary.js:4 · backend-node/src/routes/propLibrary.js:4 · backend-node/src/routes/sceneLibrary.js:4 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 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 (52 lines × 2 locations) · ×1
  • Duplicated block (52 lines × 2 locations) frontweb/src/components/Sd2AssetManagement.vue:626 — frontweb/src/components/Sd2AssetManagement.vue:626 · frontweb/src/components/Sd2AssetManagement.vue:722 — 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.
R10 · Code Duplication · Duplicated block with local edits (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) REDACTED:456 — REDACTED:456 · backend-node/src/services/imageService.js:1213 — the two spans are one implementation copied and then locally edited — 447 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 (49 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (49 matched lines × 2 locations) backend-node/src/utils/seedance2AssetGuards.js:21 — backend-node/src/utils/seedance2AssetGuards.js:21 · backend-node/src/utils/seedance2AssetGuards.js:85 — the two spans are one implementation copied and then locally edited — 266 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (46 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (46 matched lines × 2 locations) frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:195 — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:195 · frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue:240 — the two spans are one implementation copied and then locally edited — 307 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 (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) frontweb/src/composables/useCanvasEpisodeGenerate.js:148 — frontweb/src/composables/useCanvasEpisodeGenerate.js:148 · frontweb/src/composables/useCanvasEpisodeGenerate.js:199 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (45 lines × 4 locations) · ×1
  • Duplicated block (45 lines × 4 locations) backend-node/src/routes/assets.js:8 — backend-node/src/routes/assets.js:8 · backend-node/src/routes/characterLibrary.js:8 · backend-node/src/routes/propLibrary.js:8 · backend-node/src/routes/sceneLibrary.js:8 — the 4 copies are spread across 4 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 (40 lines × 3 locations) · ×1
  • Duplicated block (40 lines × 3 locations) backend-node/src/services/characterLibraryService.js:125 — backend-node/src/services/characterLibraryService.js:125 · backend-node/src/services/propLibraryService.js:49 · backend-node/src/services/sceneLibraryService.js:50 — the 3 copies are spread across 3 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 (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) backend-node/src/routes/aiConfig.js:4 — backend-node/src/routes/aiConfig.js:4 · backend-node/src/routes/prop.js:5 — the two spans are one implementation copied and then locally edited — 335 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 (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) backend-node/src/services/sceneService.js:203 — backend-node/src/services/sceneService.js:203 · backend-node/src/services/sceneService.js:260 — 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.
R10 · Code Duplication · Duplicated block (34 lines × 3 locations) · ×1
  • Duplicated block (34 lines × 3 locations) REDACTED:599 — REDACTED:599 · REDACTED:721 · REDACTED:978 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) backend-node/src/services/dramaService.js:349 — backend-node/src/services/dramaService.js:349 · backend-node/src/services/storyboardService.js:157 — the two spans are one implementation copied and then locally edited — 216 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 (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) backend-node/src/services/propService.js:182 — backend-node/src/services/propService.js:182 · backend-node/src/services/sceneService.js:464 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) backend-node/src/services/aiConfigService.js:146 — backend-node/src/services/aiConfigService.js:146 · backend-node/src/services/propService.js:66 — the two spans are one implementation copied and then locally edited — 409 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 (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) backend-node/src/services/dramaService.js:570 — backend-node/src/services/dramaService.js:570 · backend-node/src/services/dramaService.js:602 — 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.
R10 · Code Duplication · Duplicated block (29 lines × 3 locations) · ×1
  • Duplicated block (29 lines × 3 locations) frontweb/src/views/FilmList.vue:450 — frontweb/src/views/FilmList.vue:450 · frontweb/src/views/FilmList.vue:497 · frontweb/src/views/FilmList.vue:545 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) frontweb/src/views/FilmCreate.vue:5579 — frontweb/src/views/FilmCreate.vue:5579 · frontweb/src/views/FilmCreate.vue:5611 — 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.
R10 · Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (26 matched lines × 2 locations) backend-node/src/services/characterLibraryService.js:859 — backend-node/src/services/characterLibraryService.js:859 · backend-node/src/services/characterLibraryService.js:925 — the two spans are one implementation copied and then locally edited — 217 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) backend-node/src/utils/safeJson.js:226 — backend-node/src/utils/safeJson.js:226 · backend-node/src/utils/safeJson.js:254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) frontweb/src/views/FilmCreate.vue:7634 — frontweb/src/views/FilmCreate.vue:7634 · frontweb/src/views/FilmCreate.vue:7990 — 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.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) backend-node/src/services/assetService.js:1 — backend-node/src/services/assetService.js:1 · backend-node/src/services/imageService.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) backend-node/src/services/imageClient.js:468 — backend-node/src/services/imageClient.js:468 · backend-node/src/services/imageClient.js:654 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (23 lines × 3 locations) · ×1
  • Duplicated block (23 lines × 3 locations) frontweb/src/composables/filmCreate/useCharacters.js:72 — frontweb/src/composables/filmCreate/useCharacters.js:72 · frontweb/src/composables/filmCreate/useProps.js:73 · frontweb/src/composables/filmCreate/useScenes.js:66 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 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 (22 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (22 matched lines × 2 locations) backend-node/src/services/aiClient.js:225 — backend-node/src/services/aiClient.js:225 · backend-node/src/services/imageClient.js:135 — the two spans are one implementation copied and then locally edited — 156 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 (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) backend-node/src/services/characterLibraryService.js:494 — backend-node/src/services/characterLibraryService.js:494 · backend-node/src/services/characterLibraryService.js:551 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (21 lines × 3 locations) · ×1
  • Duplicated block (21 lines × 3 locations) frontweb/src/views/DramaDetail.vue:649 — frontweb/src/views/DramaDetail.vue:649 · frontweb/src/views/DramaDetail.vue:719 · frontweb/src/views/DramaDetail.vue:791 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:third-party-deep-import] frontweb/src/main.js:9 — frontweb/src/main.js:9 imports element-plus/dist/locale/zh-cn.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
R2 · Cyclomatic Complexity · Complex function processImageGeneration (cyclomatic 338, cognitive 730) · ×1
  • Complex function processImageGeneration (cyclomatic 338, cognitive 730) backend-node/src/services/imageService.js:586 — processImageGeneration has cyclomatic complexity 338 and cognitive complexity 730; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 pollVideoTask (cyclomatic 186, cognitive 283) · ×1
  • Complex function pollVideoTask (cyclomatic 186, cognitive 283) backend-node/src/services/videoClient.js:4506 — pollVideoTask has cyclomatic complexity 186 and cognitive complexity 283; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 _doImport (cyclomatic 142, cognitive 207) · ×1
  • Complex function _doImport (cyclomatic 142, cognitive 207) backend-node/src/services/dramaImportService.js:154 — _doImport has cyclomatic complexity 142 and cognitive complexity 207; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 buildUniversalSegmentUserPromptBundle (cyclomatic 131, cognitive 157) · ×1
  • Complex function buildUniversalSegmentUserPromptBundle (cyclomatic 131, cognitive 157) backend-node/src/services/universalSegmentPromptBundle.js:9 — buildUniversalSegmentUserPromptBundle has cyclomatic complexity 131 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.
R2 · Cyclomatic Complexity · Complex function testConnection (cyclomatic 115, cognitive 120) · ×1
  • Complex function testConnection (cyclomatic 115, cognitive 120) backend-node/src/services/aiConfigService.js:261 — testConnection has cyclomatic complexity 115 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 (anonymous) (cyclomatic 103, cognitive 108) · ×1
  • Complex function (anonymous) (cyclomatic 103, cognitive 108) frontweb/src/components/AIConfigContent.vue:1586 — (anonymous) has cyclomatic complexity 103 and cognitive complexity 108; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callVideoApi (cyclomatic 100, cognitive 131) · ×1
  • Complex function callVideoApi (cyclomatic 100, cognitive 131) backend-node/src/services/videoClient.js:4071 — callVideoApi has cyclomatic complexity 100 and cognitive complexity 131; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 callSoraVideoApi (cyclomatic 95, cognitive 147) · ×1
  • Complex function callSoraVideoApi (cyclomatic 95, cognitive 147) backend-node/src/services/videoClient.js:2952 — callSoraVideoApi has cyclomatic complexity 95 and cognitive complexity 147; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 safeParseAIJSON (cyclomatic 89, cognitive 259) · ×1
  • Complex function safeParseAIJSON (cyclomatic 89, cognitive 259) backend-node/src/utils/safeJson.js:180 — safeParseAIJSON has cyclomatic complexity 89 and cognitive complexity 259; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 callNanoBananaImageApi (cyclomatic 87, cognitive 103) · ×1
  • Complex function callNanoBananaImageApi (cyclomatic 87, cognitive 103) backend-node/src/services/imageClient.js:568 — callNanoBananaImageApi has cyclomatic complexity 87 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.
R2 · Cyclomatic Complexity · Complex function callImageApi (cyclomatic 79, cognitive 87) · ×1
  • Complex function callImageApi (cyclomatic 79, cognitive 87) backend-node/src/services/imageClient.js:1456 — callImageApi has cyclomatic complexity 79 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.
R2 · Cyclomatic Complexity · Complex function saveStoryboards (cyclomatic 75, cognitive 95) · ×1
  • Complex function saveStoryboards (cyclomatic 75, cognitive 95) backend-node/src/services/episodeStoryboardService.js:638 — saveStoryboards has cyclomatic complexity 75 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.
R2 · Cyclomatic Complexity · Complex function callDashScopeImageApi (cyclomatic 72, cognitive 105) · ×1
  • Complex function callDashScopeImageApi (cyclomatic 72, cognitive 105) backend-node/src/services/imageClient.js:910 — callDashScopeImageApi 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.
R2 · Cyclomatic Complexity · Complex function runMergedEpisodePostProcess (cyclomatic 66, cognitive 130) · ×1
  • Complex function runMergedEpisodePostProcess (cyclomatic 66, cognitive 130) backend-node/src/services/mergedEpisodePostProcess.js:204 — runMergedEpisodePostProcess has cyclomatic complexity 66 and cognitive complexity 130; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 callViduVideoApi (cyclomatic 64, cognitive 125) · ×1
  • Complex function callViduVideoApi (cyclomatic 64, cognitive 125) backend-node/src/services/videoClient.js:2100 — callViduVideoApi has cyclomatic complexity 64 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 runOneClickPipeline (cyclomatic 64, cognitive 98) · ×1
  • Complex function runOneClickPipeline (cyclomatic 64, cognitive 98) frontweb/src/views/FilmCreate.vue:7340 — runOneClickPipeline has cyclomatic complexity 64 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.
R2 · Cyclomatic Complexity · Complex function polishClassicVideoPromptStream (cyclomatic 61, cognitive 62) · ×1
  • Complex function polishClassicVideoPromptStream (cyclomatic 61, cognitive 62) REDACTED:777 — polishClassicVideoPromptStream has cyclomatic complexity 61 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runRepairPipeline (cyclomatic 60, cognitive 88) · ×1
  • Complex function runRepairPipeline (cyclomatic 60, cognitive 88) frontweb/src/views/FilmCreate.vue:7781 — runRepairPipeline has cyclomatic complexity 60 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.
R2 · Cyclomatic Complexity · Complex function generateStoryboard (cyclomatic 57, cognitive 70) · ×1
  • Complex function generateStoryboard (cyclomatic 57, cognitive 70) backend-node/src/services/episodeStoryboardService.js:1126 — generateStoryboard 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.
R2 · Cyclomatic Complexity · Complex function callVolcengineOmniVideoApi (cyclomatic 56, cognitive 90) · ×1
  • Complex function callVolcengineOmniVideoApi (cyclomatic 56, cognitive 90) backend-node/src/services/videoClient.js:634 — callVolcengineOmniVideoApi has cyclomatic complexity 56 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.
R2 · Cyclomatic Complexity · Complex function callJimengAiApiVideo (cyclomatic 56, cognitive 62) · ×1
  • Complex function callJimengAiApiVideo (cyclomatic 56, cognitive 62) backend-node/src/services/videoClient.js:3330 — callJimengAiApiVideo has cyclomatic complexity 56 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callAgnesVideoApi (cyclomatic 55, cognitive 55) · ×1
  • Complex function callAgnesVideoApi (cyclomatic 55, cognitive 55) backend-node/src/services/videoClient.js:2711 — callAgnesVideoApi has cyclomatic complexity 55 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 polishPrompt (cyclomatic 54, cognitive 67) · ×1
  • Complex function polishPrompt (cyclomatic 54, cognitive 67) REDACTED:410 — polishPrompt has cyclomatic complexity 54 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 52, cognitive 80) · ×1
  • Complex function (anonymous) (cyclomatic 52, cognitive 80) backend-node/src/services/imageClient.js:1744 — (anonymous) has cyclomatic complexity 52 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 pickProxyVideoUrl (cyclomatic 52, cognitive 73) · ×1
  • Complex function pickProxyVideoUrl (cyclomatic 52, cognitive 73) backend-node/src/services/videoClient.js:1359 — pickProxyVideoUrl has cyclomatic complexity 52 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function processPropImageGeneration (cyclomatic 52, cognitive 60) · ×1
  • Complex function processPropImageGeneration (cyclomatic 52, cognitive 60) backend-node/src/services/propImageGenerationService.js:21 — processPropImageGeneration has cyclomatic complexity 52 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onGenerateSbVideo (cyclomatic 50, cognitive 74) · ×1
  • Complex function onGenerateSbVideo (cyclomatic 50, cognitive 74) frontweb/src/views/FilmCreate.vue:6482 — onGenerateSbVideo has cyclomatic complexity 50 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 processVideoGeneration (cyclomatic 50, cognitive 63) · ×1
  • Complex function processVideoGeneration (cyclomatic 50, cognitive 63) backend-node/src/services/videoService.js:472 — processVideoGeneration has cyclomatic complexity 50 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 saveCharacters (cyclomatic 49, cognitive 104) · ×1
  • Complex function saveCharacters (cyclomatic 49, cognitive 104) backend-node/src/services/dramaService.js:558 — saveCharacters has cyclomatic complexity 49 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 exportDrama (cyclomatic 49, cognitive 82) · ×1
  • Complex function exportDrama (cyclomatic 49, cognitive 82) backend-node/src/services/dramaExportService.js:80 — exportDrama has cyclomatic complexity 49 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.
R2 · Cyclomatic Complexity · Complex function processStoryboardGeneration (cyclomatic 48, cognitive 64) · ×1
  • Complex function processStoryboardGeneration (cyclomatic 48, cognitive 64) backend-node/src/services/episodeStoryboardService.js:862 — processStoryboardGeneration has cyclomatic complexity 48 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callDashScopeVideoApi (cyclomatic 48, cognitive 57) · ×1
  • Complex function callDashScopeVideoApi (cyclomatic 48, cognitive 57) backend-node/src/services/videoClient.js:1641 — callDashScopeVideoApi has cyclomatic complexity 48 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callXaiVideoApi (cyclomatic 47, cognitive 59) · ×1
  • Complex function callXaiVideoApi (cyclomatic 47, cognitive 59) backend-node/src/services/videoClient.js:3515 — callXaiVideoApi has cyclomatic complexity 47 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.
R2 · Cyclomatic Complexity · Complex function videoWorker (cyclomatic 46, cognitive 76) · ×1
  • Complex function videoWorker (cyclomatic 46, cognitive 76) frontweb/src/views/FilmCreate.vue:6957 — videoWorker has cyclomatic complexity 46 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function createConfig (cyclomatic 45, cognitive 54) · ×1
  • Complex function createConfig (cyclomatic 45, cognitive 54) backend-node/src/services/aiConfigService.js:75 — createConfig has cyclomatic complexity 45 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runGenerateStoryFromPremise (cyclomatic 44, cognitive 43) · ×1
  • Complex function runGenerateStoryFromPremise (cyclomatic 44, cognitive 43) frontweb/src/composables/useStoryGeneration.js:12 — runGenerateStoryFromPremise has cyclomatic complexity 44 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callGeminiImageApi (cyclomatic 43, cognitive 79) · ×1
  • Complex function callGeminiImageApi (cyclomatic 43, cognitive 79) backend-node/src/services/imageClient.js:1215 — callGeminiImageApi has cyclomatic complexity 43 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function processVideoMerge (cyclomatic 43, cognitive 54) · ×1
  • Complex function processVideoMerge (cyclomatic 43, cognitive 54) backend-node/src/services/videoMergeService.js:190 — processVideoMerge has cyclomatic complexity 43 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callMinimaxH3VideoApi (cyclomatic 43, cognitive 46) · ×1
  • Complex function callMinimaxH3VideoApi (cyclomatic 43, cognitive 46) backend-node/src/services/videoClient.js:3942 — callMinimaxH3VideoApi has cyclomatic complexity 43 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callKlingVideoApi (cyclomatic 42, cognitive 61) · ×1
  • Complex function callKlingVideoApi (cyclomatic 42, cognitive 61) backend-node/src/services/videoClient.js:1481 — callKlingVideoApi has cyclomatic complexity 42 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 · frontweb/src/views/FilmCreate.vue · ×1
  • frontweb/src/views/FilmCreate.vue: 10394 lines of code frontweb/src/views/FilmCreate.vue:1 — frontweb/src/views/FilmCreate.vue has 10394 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 · backend-node/src/services/videoClient.js · ×1
  • backend-node/src/services/videoClient.js: 4637 lines of code backend-node/src/services/videoClient.js:1 — backend-node/src/services/videoClient.js has 4637 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 · frontweb/src/components/AIConfigContent.vue · ×1
  • frontweb/src/components/AIConfigContent.vue: 2759 lines of code frontweb/src/components/AIConfigContent.vue:1 — frontweb/src/components/AIConfigContent.vue has 2759 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 · backend-node/src/services/imageClient.js · ×1
  • backend-node/src/services/imageClient.js: 1872 lines of code backend-node/src/services/imageClient.js:1 — backend-node/src/services/imageClient.js has 1872 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 · backend-node/src/services/imageService.js · ×1
  • backend-node/src/services/imageService.js: 1593 lines of code backend-node/src/services/imageService.js:1 — backend-node/src/services/imageService.js has 1593 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 · backend-node/src/services/episodeStoryboardService.js · ×1
  • backend-node/src/services/episodeStoryboardService.js: 1575 lines of code backend-node/src/services/episodeStoryboardService.js:1 — backend-node/src/services/episodeStoryboardService.js has 1575 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 · frontweb/src/views/DramaDetail.vue · ×1
  • frontweb/src/views/DramaDetail.vue: 1470 lines of code frontweb/src/views/DramaDetail.vue:1 — frontweb/src/views/DramaDetail.vue has 1470 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 · backend-node/src/services/promptI18n.js · ×1
  • backend-node/src/services/promptI18n.js: 1375 lines of code backend-node/src/services/promptI18n.js:1 — backend-node/src/services/promptI18n.js has 1375 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 · frontweb/src/views/FilmList.vue · ×1
  • frontweb/src/views/FilmList.vue: 1279 lines of code frontweb/src/views/FilmList.vue:1 — frontweb/src/views/FilmList.vue has 1279 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 · frontweb/src/views/DramaCanvas.vue · ×1
  • frontweb/src/views/DramaCanvas.vue: 1053 lines of code frontweb/src/views/DramaCanvas.vue:1 — frontweb/src/views/DramaCanvas.vue has 1053 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 · REDACTED · ×1
  • REDACTED: 1052 lines of code REDACTED:1 — REDACTED has 1052 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 · backend-node/src/services/characterLibraryService.js · ×1
  • backend-node/src/services/characterLibraryService.js: 978 lines of code backend-node/src/services/characterLibraryService.js:1 — backend-node/src/services/characterLibraryService.js has 978 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 · backend-node/src/services/dramaService.js · ×1
  • backend-node/src/services/dramaService.js: 832 lines of code backend-node/src/services/dramaService.js:1 — backend-node/src/services/dramaService.js has 832 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 · frontweb/src/composables/filmCreate/useCharacters.js · ×1
  • frontweb/src/composables/filmCreate/useCharacters.js: 814 lines of code frontweb/src/composables/filmCreate/useCharacters.js:1 — frontweb/src/composables/filmCreate/useCharacters.js has 814 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 · frontweb/src/components/Sd2AssetManagement.vue · ×1
  • frontweb/src/components/Sd2AssetManagement.vue: 798 lines of code frontweb/src/components/Sd2AssetManagement.vue:1 — frontweb/src/components/Sd2AssetManagement.vue has 798 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 · backend-node/src/services/aiClient.js · ×1
  • backend-node/src/services/aiClient.js: 796 lines of code backend-node/src/services/aiClient.js:1 — backend-node/src/services/aiClient.js has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · frontweb/src/components/UniversalSegmentOmniAtEditor.vue · ×1
  • frontweb/src/components/UniversalSegmentOmniAtEditor.vue: 679 lines of code frontweb/src/components/UniversalSegmentOmniAtEditor.vue:1 — frontweb/src/components/UniversalSegmentOmniAtEditor.vue has 679 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 · backend-node/src/services/framePromptService.js · ×1
  • backend-node/src/services/framePromptService.js: 643 lines of code backend-node/src/services/framePromptService.js:1 — backend-node/src/services/framePromptService.js has 643 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · frontweb/src/composables/filmCreate/useProps.js · ×1
  • frontweb/src/composables/filmCreate/useProps.js: 596 lines of code frontweb/src/composables/filmCreate/useProps.js:1 — frontweb/src/composables/filmCreate/useProps.js has 596 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 · frontweb/src/composables/filmCreate/useScenes.js · ×1
  • frontweb/src/composables/filmCreate/useScenes.js: 594 lines of code frontweb/src/composables/filmCreate/useScenes.js:1 — frontweb/src/composables/filmCreate/useScenes.js has 594 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 · backend-node/src/services/videoService.js · ×1
  • backend-node/src/services/videoService.js: 593 lines of code backend-node/src/services/videoService.js:1 — backend-node/src/services/videoService.js has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · frontweb/src/stores/generationTaskStore.js · ×1
  • frontweb/src/stores/generationTaskStore.js: 593 lines of code frontweb/src/stores/generationTaskStore.js:1 — frontweb/src/stores/generationTaskStore.js has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · backend-node/src/services/aiConfigService.js · ×1
  • backend-node/src/services/aiConfigService.js: 561 lines of code backend-node/src/services/aiConfigService.js:1 — backend-node/src/services/aiConfigService.js has 561 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 · frontweb/src/views/FreeCreate.vue · ×1
  • frontweb/src/views/FreeCreate.vue: 523 lines of code frontweb/src/views/FreeCreate.vue:1 — frontweb/src/views/FreeCreate.vue has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · backend-node/src/db/migrate.js · ×1
  • backend-node/src/db/migrate.js: 514 lines of code backend-node/src/db/migrate.js:1 — backend-node/src/db/migrate.js has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · frontweb/src/utils/dramaCanvasAdapter.js · ×1
  • frontweb/src/utils/dramaCanvasAdapter.js: 497 lines of code frontweb/src/utils/dramaCanvasAdapter.js:1 — frontweb/src/utils/dramaCanvasAdapter.js has 497 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 · frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue · ×1
  • frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue: 484 lines of code frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue:1 — frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue has 484 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 · backend-node/src/services/universalSegmentPromptBundle.js · ×1
  • backend-node/src/services/universalSegmentPromptBundle.js: 453 lines of code backend-node/src/services/universalSegmentPromptBundle.js:1 — backend-node/src/services/universalSegmentPromptBundle.js has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · backend-node/src/services/sceneService.js · ×1
  • backend-node/src/services/sceneService.js: 443 lines of code backend-node/src/services/sceneService.js:1 — backend-node/src/services/sceneService.js has 443 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 · frontweb/src/views/MediaLibrary.vue · ×1
  • frontweb/src/views/MediaLibrary.vue: 426 lines of code frontweb/src/views/MediaLibrary.vue:1 — frontweb/src/views/MediaLibrary.vue has 426 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 · backend-node/src/services/dramaImportService.js · ×1
  • backend-node/src/services/dramaImportService.js: 421 lines of code backend-node/src/services/dramaImportService.js:1 — backend-node/src/services/dramaImportService.js has 421 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 · frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue · ×1
  • frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue: 419 lines of code frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:1 — frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue has 419 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 · backend-node/src/utils/safeJson.js · ×1
  • backend-node/src/utils/safeJson.js: 418 lines of code backend-node/src/utils/safeJson.js:1 — backend-node/src/utils/safeJson.js has 418 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 · backend-node/src/services/dramaExportService.js · ×1
  • backend-node/src/services/dramaExportService.js: 410 lines of code backend-node/src/services/dramaExportService.js:1 — backend-node/src/services/dramaExportService.js has 410 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 · backend-node/src/services/angleService.js · ×1
  • backend-node/src/services/angleService.js: 408 lines of code backend-node/src/services/angleService.js:1 — backend-node/src/services/angleService.js has 408 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 · backend-node/src/services/mergedEpisodePostProcess.js · ×1
  • backend-node/src/services/mergedEpisodePostProcess.js: 408 lines of code backend-node/src/services/mergedEpisodePostProcess.js:1 — backend-node/src/services/mergedEpisodePostProcess.js has 408 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 · frontweb/src/components/SceneModelMap.vue · ×1
  • frontweb/src/components/SceneModelMap.vue: 405 lines of code frontweb/src/components/SceneModelMap.vue:1 — frontweb/src/components/SceneModelMap.vue has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No test, lint or typecheck script · ×1
  • No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~8179 LoC) · ×1
  • Dead file (~8179 LoC) frontweb/src/views/FilmCreate.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~2407 LoC) · ×1
  • Dead file (~2407 LoC) frontweb/src/components/AIConfigContent.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~1208 LoC) · ×1
  • Dead file (~1208 LoC) frontweb/src/views/DramaDetail.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~926 LoC) · ×1
  • Dead file (~926 LoC) frontweb/src/views/DramaCanvas.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~877 LoC) · ×1
  • Dead file (~877 LoC) frontweb/src/composables/filmCreate/useCharacters.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~795 LoC) · ×1
  • Dead file (~795 LoC) frontweb/src/views/FilmList.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~790 LoC) · ×1
  • Dead file (~790 LoC) frontweb/src/components/Sd2AssetManagement.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~657 LoC) · ×1
  • Dead file (~657 LoC) frontweb/src/stores/generationTaskStore.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~651 LoC) · ×1
  • Dead file (~651 LoC) frontweb/src/composables/filmCreate/useProps.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~646 LoC) · ×1
  • Dead file (~646 LoC) frontweb/src/composables/filmCreate/useScenes.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~546 LoC) · ×1
  • Dead file (~546 LoC) frontweb/src/utils/dramaCanvasAdapter.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~474 LoC) · ×1
  • Dead file (~474 LoC) frontweb/src/components/UniversalSegmentOmniAtEditor.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~410 LoC) · ×1
  • Dead file (~410 LoC) frontweb/src/components/dramaCanvas/CanvasStoryboardPanel.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasStoryboardNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~383 LoC) · ×1
  • Dead file (~383 LoC) frontweb/src/components/SceneModelMap.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~327 LoC) · ×1
  • Dead file (~327 LoC) frontweb/src/views/FreeCreate.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~298 LoC) · ×1
  • Dead file (~298 LoC) frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasAssetNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~264 LoC) · ×1
  • Dead file (~264 LoC) frontweb/src/views/MediaLibrary.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~263 LoC) · ×1
  • Dead file (~263 LoC) frontweb/src/components/EpisodeBatchImportDialog.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~260 LoC) · ×1
  • Dead file (~260 LoC) frontweb/src/composables/useCanvasEpisodeGenerate.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~243 LoC) · ×1
  • Dead file (~243 LoC) frontweb/src/composables/useCanvasCrud.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~223 LoC) · ×1
  • Dead file (~223 LoC) frontweb/src/components/AgentDrawer.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~206 LoC) · ×1
  • Dead file (~206 LoC) frontweb/src/composables/useCanvasScript.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~186 LoC) · ×1
  • Dead file (~186 LoC) frontweb/src/components/PromptEditor.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~154 LoC) · ×1
  • Dead file (~154 LoC) frontweb/src/utils/storyboardMedia.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/utils/dramaCanvasAdapter.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~152 LoC) · ×1
  • Dead file (~152 LoC) frontweb/src/components/dramaCanvas/CanvasCreateDialog.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~151 LoC) · ×1
  • Dead file (~151 LoC) frontweb/src/composables/useGenerationTaskSync.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~149 LoC) · ×1
  • Dead file (~149 LoC) frontweb/src/composables/useCanvasWorkflowRunner.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~145 LoC) · ×1
  • Dead file (~145 LoC) frontweb/src/components/dramaCanvas/CanvasScriptPanel.vue — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/components/dramaCanvas/CanvasScriptNode.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~142 LoC) · ×1
  • Dead file (~142 LoC) frontweb/src/composables/useStoryGeneration.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~94 LoC) · ×1
  • Dead file (~94 LoC) frontweb/src/utils/scriptEpisodes.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~80 LoC) · ×1
  • Dead file (~80 LoC) frontweb/src/utils/canvasWorkflow.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontweb/src/utils/dramaCanvasAdapter.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~76 LoC) · ×1
  • Dead file (~76 LoC) frontweb/src/composables/filmCreate/libraryMembership.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~75 LoC) · ×1
  • Dead file (~75 LoC) frontweb/src/api/drama.js — no import path from any entry point (41 application, 1 tooling, 38 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity index.html:28 — `https://cdn.tailwindcss.com` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup.
Minor — 113 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×39
  • Duplicated predicate backend-node/src/services/backgroundExtractionService.js:171 — `!episode.script_content || !String(episode.script_content).trim()` appears character-identically in 2 files — backend-node/src/services/backgroundExtractionService.js, backend-node/src/services/propExtractionService.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 backend-node/src/services/mergedEpisodePostProcess.js:212 — `!mergedAbsPath || !fs.existsSync(mergedAbsPath) || !Array.isArray(scenes) || scenes.length === 0` appears character-identically in 2 files — backend-node/src/services/mergedEpisodePostProcess.js, backend-node/src/services/narrationVideoPostProcess.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 backend-node/src/services/jimengMaterialHubService.js:163 — `!obj || typeof obj !== 'object' || Array.isArray(obj)` appears character-identically in 2 files — backend-node/src/services/jimengMaterialHubService.js, backend-node/src/services/modelArkAssetConfigService.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 backend-node/src/services/backgroundExtractionService.js:68 — `!scriptContent || !String(scriptContent).trim()` appears character-identically in 2 files — backend-node/src/services/backgroundExtractionService.js, backend-node/src/services/propExtractionService.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 frontweb/src/composables/filmCreate/useProps.js:499 — `!store.dramaId || !currentEpisodeId.value` appears character-identically in 2 files — frontweb/src/composables/filmCreate/useProps.js, frontweb/src/composables/filmCreate/useScenes.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 backend-node/src/services/videoMergeService.js:85 — `!videoUrl || typeof videoUrl !== 'string'` appears character-identically in 2 files — backend-node/src/services/videoMergeService.js, backend-node/src/services/videoService.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 frontweb/src/composables/filmCreate/useCharacters.js:44 — `(arr[0].match(/:(.*?);/) || [])[1] || 'image/png'` appears character-identically in 3 files — frontweb/src/composables/filmCreate/useCharacters.js, frontweb/src/composables/filmCreate/useProps.js, frontweb/src/composables/filmCreate/useScenes.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:469 — `(nextShot.action || [nextShot.location, nextShot.time].filter(Boolean).join(' ')).slice(0, 120).trim() || '(last shot)'` appears character-identically in 2 files — REDACTED, backend-node/src/services/imageService.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:464 — `(prevShot.action || [prevShot.location, prevShot.time].filter(Boolean).join(' ')).slice(0, 120).trim() || '(first shot)'` appears character-identically in 2 files — REDACTED, backend-node/src/services/imageService.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 backend-node/src/services/imageService.js:733 — `Array.isArray(parsed) && parsed.length > 0` appears character-identically in 2 files — backend-node/src/services/imageService.js, backend-node/src/utils/safeJson.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 backend-node/src/services/imageClient.js:872 — `baseUrl && /localhost|127\.0\.0\.1/i.test(baseUrl)` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:255 — `body.model_name || body.model || undefined` appears character-identically in 2 files — REDACTED, backend-node/src/routes/scenes.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:1039 — `cfg.storage?.local_path || './data/storage'` appears character-identically in 6 files — REDACTED, backend-node/src/services/imageClient.js, backend-node/src/services/imageService.js, backend-node/src/services/propImageGenerationService.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:127 — `cfg?.storage?.local_path || './data/storage'` appears character-identically in 7 files — REDACTED, backend-node/src/routes/upload.js, backend-node/src/services/aiClient.js, backend-node/src/services/characterLibraryService.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:439 — `cfg?.style?.default_style_en || cfg?.style?.default_style || ''` appears character-identically in 4 files — REDACTED, backend-node/src/services/framePromptService.js, backend-node/src/services/imageService.js, backend-node/src/services/universalSegmentPromptBundle.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 backend-node/src/services/imageClient.js:428 — `config.base_url || 'https://api.klingai.com'` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.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 backend-node/src/services/imageClient.js:1218 — `config.base_url || 'https://generativelanguage.googleapis.com'` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.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 backend-node/src/services/imageClient.js:1415 — `errJson.error?.message || errJson.message` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.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 backend-node/src/services/imageClient.js:1641 — `errJson.error?.message || errJson.message || errJson.error` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.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 backend-node/src/services/mergedEpisodePostProcess.js:409 — `fs.existsSync(mergedAbsPath) && outAbs !== mergedAbsPath` appears character-identically in 2 files — backend-node/src/services/mergedEpisodePostProcess.js, backend-node/src/services/narrationVideoPostProcess.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 backend-node/src/services/characterLibraryService.js:231 — `image_url && !image_url.startsWith('data:')` appears character-identically in 3 files — backend-node/src/services/characterLibraryService.js, backend-node/src/services/propLibraryService.js, backend-node/src/services/sceneLibraryService.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 backend-node/src/services/imageClient.js:1284 — `imgRes.headers.get('content-type') || 'image/jpeg'` appears character-identically in 2 files — backend-node/src/services/imageClient.js, backend-node/src/services/videoClient.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 backend-node/src/services/characterLibraryService.js:519 — `mergedCfg.style.default_style_en || mergedCfg.style.default_style || ''` appears character-identically in 2 files — backend-node/src/services/characterLibraryService.js, backend-node/src/services/sceneService.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 backend-node/src/services/mergedEpisodePostProcess.js:132 — `n == null || !Number.isFinite(videoDur) || videoDur <= 0.1` appears character-identically in 2 files — backend-node/src/services/mergedEpisodePostProcess.js, backend-node/src/services/narrationVideoPostProcess.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 backend-node/src/services/characterLibraryService.js:148 — `normalizeSourceId(req.source_id) || null` appears character-identically in 3 files — backend-node/src/services/characterLibraryService.js, backend-node/src/services/propLibraryService.js, backend-node/src/services/sceneLibraryService.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.
  • + 14 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×26
  • Console output used as the logging channel REDACTED:55 — `REDACTED` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel REDACTED:70 — `REDACTED` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/server.js:12 — `backend-node/src/server.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/utils/safeJson.js:185 — `backend-node/src/utils/safeJson.js` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:360 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 360 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:382 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 382 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:404 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 404 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:455 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 455 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:516 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 516 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:525 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 525 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:568 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 568 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/aiConfigService.js:570 — `backend-node/src/services/aiConfigService.js` reports through `console.*` at line 570 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/backgroundExtractionService.js:42 — `backend-node/src/services/backgroundExtractionService.js` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/backgroundExtractionService.js:43 — `backend-node/src/services/backgroundExtractionService.js` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/characterGenerationService.js:88 — `backend-node/src/services/characterGenerationService.js` reports through `console.*` at line 88 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/services/characterGenerationService.js:96 — `backend-node/src/services/characterGenerationService.js` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel REDACTED:148 — `REDACTED` reports through `console.*` at line 148 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/routes/agent.js:18 — `backend-node/src/routes/agent.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:22 — `backend-node/src/db/migrate.js` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:26 — `backend-node/src/db/migrate.js` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:29 — `backend-node/src/db/migrate.js` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:39 — `backend-node/src/db/migrate.js` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:70 — `backend-node/src/db/migrate.js` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:80 — `backend-node/src/db/migrate.js` reports through `console.*` at line 80 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel backend-node/src/db/migrate.js:85 — `backend-node/src/db/migrate.js` reports through `console.*` at line 85 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 1 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×15
  • Silent fallback default in catch backend-node/src/services/storageLayout.js:22 — `parseMetadata` 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 backend-node/src/services/deepseekConfig.js:14 — `parseSettings` 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 backend-node/src/services/storyboardService.js:21 — `parseDramaCharacterIds` 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 backend-node/src/utils/dramaStyleMerge.js:14 — `parseDramaMetadata` 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 backend-node/src/services/framePromptService.js:254 — `loadDramaCharacterNamesForStoryboard` 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 backend-node/src/services/episodeStoryboardService.js:233 — `getStoryboardsForEpisode` 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 backend-node/src/services/dramaService.js:343 — `parseStoryboardCharacters` 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 backend-node/src/services/dramaExportService.js:36 — `parseExtraImages` 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 backend-node/src/services/dramaExportService.js:73 — `parseSbChars` 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 backend-node/src/services/modelArkAssetConfigService.js:26 — `parseSettingsJson` 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 backend-node/src/services/videoClient.js:191 — `parseConfigSettingsJson` 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 backend-node/src/services/videoClient.js:3715 — `storageRelativeFromPublicUrl` 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 frontweb/src/api/agent.js:8 — `readError` 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 frontweb/src/utils/canvasLayout.js:81 — `parseDramaMetadata` 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 frontweb/src/utils/videoOmniSupport.js:36 — `parseAiConfigSettings` 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.
D12 · Dependency Hygiene · Deprecated · ×6
  • Deprecated: lodash.get REDACTED:2784 — lodash.get 4.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: boolean REDACTED:2311 — boolean 3.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:3929 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:4371 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: lodash.get REDACTED:4744 — lodash.get 4.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:6683 — rimraf 2.6.3 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D34 · Knowledge Freshness · Orphaned file · ×5
  • Orphaned file frontweb/src/components/SceneModelMap.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file frontweb/src/components/EpisodeBatchImportDialog.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file backend-node/src/services/libraryDedup.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file backend-node/src/routes/sceneModelMap.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file backend-node/src/services/deepseekConfig.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X7 · Silent fallback defaults · Pending state with no failure state · ×5
  • Pending state with no failure state frontweb/src/views/MediaLibrary.vue:39 — The view draws `正在上传 {{ uploadProgress.current }}/{{ uploadProgress.total }}...` under `uploading`, but `uploading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontweb/src/components/SceneModelMap.vue:17 — The view draws `<div v-if="loading" v-loading="true" class="loading-wrap" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontweb/src/components/dramaCanvas/CanvasAssetPanel.vue:21 — The view draws `{{ nodeBusy?.message || '生成参考图…' }}` under `generating || nodeBusy`, but `generating` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue:37 — The view draws `生图中…` under `busy`, but `busy` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontweb/src/components/dramaCanvas/CanvasMediaPanel.vue:46 — The view draws `生视频中…` under `busy`, but `busy` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
D21 · Naming Consistency · `taskID` spells `ID` where 253 names in the project spell it `Id` · ×2
  • `taskID` spells `ID` where 253 names in the project spell it `Id` backend-node/src/services/backgroundExtractionService.js:60 — 253 of 255 names in project repository spell the token `Id` (253 of 255; unit: names in project repository containing `Id`). Peers: context.dramaThreadId (backend-node/src/mastra/context.mjs:1); context.dramaThreadId(dramaId) (backend-node/src/mastra/context.mjs:1); context.resolveEpisode(dramaId) (backend-node/src/mastra/context.mjs:5); context.resolveEpisode(episodeId) (backend-node/src/mastra/context.mjs:5); context.assertOwned(dramaId) (backend-node/src/mastra/context.mjs:25). Rename to `taskId`. [rule N6]
  • `taskID` spells `ID` where 253 names in the project spell it `Id` backend-node/src/services/characterGenerationService.js:35 — 253 of 255 names in project repository spell the token `Id` (253 of 255; unit: names in project repository containing `Id`). Peers: context.dramaThreadId (backend-node/src/mastra/context.mjs:1); context.dramaThreadId(dramaId) (backend-node/src/mastra/context.mjs:1); context.resolveEpisode(dramaId) (backend-node/src/mastra/context.mjs:5); context.resolveEpisode(episodeId) (backend-node/src/mastra/context.mjs:5); context.assertOwned(dramaId) (backend-node/src/mastra/context.mjs:25). Rename to `taskId`. [rule N6]
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): uuid backend-node/package.json:29 — uuid is pinned at 10.0.0; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found frontweb/package.json:7 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `frontweb/package.json` makes this repository a deployable product (line 7).
D21 · Naming Consistency · `dramaAPI` spells `API` where 32 names in the project spell it `Api` · ×1
  • `dramaAPI` spells `API` where 32 names in the project spell it `Api` frontweb/src/constants/styleOptions.js:275 — 32 of 33 names in project repository spell the token `Api` (32 of 33; unit: names in project repository containing `Api`). Peers: aiConfigService.normalizeApiKeyForService (backend-node/src/services/aiConfigService.js:6); aiConfigService.bulkUpdateApiKey (backend-node/src/services/aiConfigService.js:576); imageClient.resolveAssetUserNegativeForApi (backend-node/src/services/imageClient.js:28); imageClient.callKlingImageApi (backend-node/src/services/imageClient.js:426); imageClient.callNanoBananaImageApi (backend-node/src/services/imageClient.js:568). Rename to `dramaApi`. [rule N6]
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 5 of 120 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 120 of the 179 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: frontweb/src/components/SceneModelMap.vue, frontweb/src/components/EpisodeBatchImportDialog.vue, backend-node/src/services/libraryDedup.js, backend-node/src/routes/sceneModelMap.js, backend-node/src/services/deepseekConfig.js. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D37 · Vulnerability-disclosure Policy · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation backend-node/package.json:15 — `backend-node/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected backend-node/src/server.js:33 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
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 4/30 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.
Minor — 15 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×15
  • Outdated (npm): @mastra/core — @mastra/core is pinned at 1.78.0; registry.npmjs.org publishes 1.83.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mastra/libsql — @mastra/libsql is pinned at 1.26.2; registry.npmjs.org publishes 1.30.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mastra/memory — @mastra/memory is pinned at 1.38.0; registry.npmjs.org publishes 1.41.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): adm-zip — adm-zip is pinned at 0.5.16; registry.npmjs.org publishes 0.6.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): axios — axios is pinned at 1.13.5; registry.npmjs.org publishes 1.21.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): better-sqlite3 — better-sqlite3 is pinned at 13.0.3; registry.npmjs.org publishes 13.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): element-plus — element-plus is pinned at 2.13.2; registry.npmjs.org publishes 2.14.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): express — express is pinned at 4.22.1; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): js-yaml — js-yaml is pinned at 4.1.1; registry.npmjs.org publishes 5.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): jsonrepair — jsonrepair is pinned at 3.13.3; registry.npmjs.org publishes 3.15.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): multer — multer is pinned at 1.4.5-lts.2; registry.npmjs.org publishes 2.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): pinia — pinia is pinned at 2.3.1; registry.npmjs.org publishes 4.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): sharp — sharp is pinned at 0.34.5; registry.npmjs.org publishes 0.35.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): vue — vue is pinned at 3.5.27; registry.npmjs.org publishes 3.5.45 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): vue-router — vue-router is pinned at 4.6.4; registry.npmjs.org publishes 5.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-9a8732020ec74138925d6d32cd8eb199/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=69" --report-format json --report-path /tmp/watchdog-gitleaks-9a8732020ec74138925d6d32cd8eb199/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9a8732020ec74138925d6d32cd8eb199/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude desktop .179artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .48artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e9e2-c8a6-76e0-82ec-7a1152436f3a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md